ProductiveBot Architecture direction · Internal guide

The platform we’re working toward.

Every eligible durable business record uses the same Brain contracts on a machine the customer owns — coordinated by one control plane, so new tools reuse context without creating a second knowledge store.

This is the target architecture, not a claim that the full integrated stack is complete. Hover or tap any component to see its role.

OWNERSHIP BOUNDARY — TAP THE PRODUCTIVEBOT WORKSTATION · CUSTOMER-OWNED THE ONLY DOOR Apps & branded Machines Extensions: Content · Workflow · Meta Ads · next Scout guides · never executes ProductiveBot Core jobs · events · handoffs pb-record M1 · the one writer pb-recall M2 · scoped reads only Broker approval + audit Company Brain durable · portable · plain files · yours Total Recall memory · instant recall Runner adapter one doorway: start · stream · cancel · resume Agent runners Hermes default · OpenClaw supported — the body AI models Claude · GPT · Gemini · local via Ollama — the brain Providers Meta · Google · email · more

What exists now, and what comes next

The map is the durable direction. We are assembling it in small, verifiable slices instead of treating every box as already integrated.

Foundations in use

Customer-owned local software, a Company Brain scaffold, Total Recall Brain registration, Broker foundations, and Hermes/OpenClaw execution inform the system today. The shared writer and scoped reader remain M1–M2 work.

Next integrated proof

Publish Core’s `pb.handoff/v1` and Runner Adapter contracts; then prove one Content Machine path through `pb-record`, `pb-recall`, Broker rules, and later-session retrieval.