← Deterministic Core
Interactive architecture · 29 May 2026

Deterministic Core Architecture

Click a node to see what owns it, why it exists, and where the source of truth lives. The point is simple: software owns the gate; RL reasons inside it.

A
System map

Click through the control flow

4
Applied cores

Where this pattern is already being used

Family Core

Family

Partial

Private-by-default household logistics. Abby onboarding and shared-action consent are intentionally blocked until opt-in.

Stock Alert Core

Stocks

Live scaffold

Freshness, trigger, position context and no-noise gates. Typed claim files now hold deterministic monitor state.

Report Core

Reports

Live scaffold

Client/report jobs move through package → validation → approval → generation → audit.

KB Capture Core

KB

Live

Durable knowledge gets routed to the right wiki/project/person/ticker file with privacy classification.

!
Known gap

What still needs to become hard middleware

Current truth: the cores guide and test RL, but they do not yet intercept every OpenClaw tool call.

Today

  • Classifiers, checklists, schemas and tests exist.
  • Risky work is guided by protocol and visible audit.
  • Some state is now typed and inspectable.

Target

  • Safe wrappers for messages, crons, stock alerts and family actions.
  • Restricted direct access once wrappers exist.
  • No high-risk action without classify → policy → validate → approve.