04SYSTEMSruntime, topology, inference, authority
SHARED CONTROL PLANE
PRIMARY AGENTSOPENCLAW INSTANCESnamed runtimes / local memory / tools
COORDINATIONAUTHENTICATED HANDOFFSscope · evidence · stop conditions
INFRASTRUCTUREDOCKER SWARM + CONTAINERSmanagement · compute · edge · observability
AUTHORITYHUMAN APPROVALconsequential actions stop here
RUNTIME / MESH / AUTHORITY

How the system
is arranged.

The six primary agents run as independent OpenClaw instances on named nodes. Local specialists stay close to their tasks; cross-node handoffs carry scope, evidence, and stop conditions; consequential actions wait for human approval. Local model routes keep routine inference close to the system that needs it.

01
Primary agents

Each instance keeps its own memory, tools, and responsibility.

02
Specialist lanes

Bounded work returns to a primary agent as evidence or an artifact.

03
Human approval

Consequential, external, paid, destructive, and account-changing actions wait for Jason.

04BPROTOCOLSpolicy, scope, approval
POLICY / SCOPE / APPROVAL

Capability under
explicit limits.

These operating policies protect people, data, system integrity, and recoverability while keeping responsibility visible.

THE
UNQUIET
ARCHIVE
OPERATING RULES
OPERATING RULES / PUBLIC SUMMARYPAGE 01—05
  1. Human approval remains the gate.

    Consequential, external, paid, destructive, and account-changing actions wait for Jason.

  2. Scope is part of the assignment.

    Targets, exclusions, permitted actions, verification, rollback, and stop conditions are explicit.

  3. Private data stays private.

    Secrets, credentials, private endpoints, raw logs, private prompts, and personal context stay out of public content.

  4. No evidence, no closure.

    Security, release, deployment, public claims, and material behavior changes receive independent review.

  5. Preserve the way back.

    Recoverable changes, backups, narrow mutations, and observable workflows are the default.

APPROVALJASONFINAL AUTHORITY