Architecture

Architecture

The method has three layers. Standards define the rules and evidence requirements. Skills turn those rules into repeatable recipes. The runtime supplies the tools, access, task records, schedules and checkpoints needed to execute them.

The loop crosses all three: execute within authority; record the result; review the evidence; propose a supported lesson; update the canonical source after review; regenerate derived copies; test the next activation. No step is proven by the mere existence of the previous one.

The minimum implementation is an accessible request, a bounded task, an acceptance test and a saved result. A team implementation adds concurrent ownership, independent checks and enforced audience boundaries. Avoid presenting the larger implementation as a prerequisite for learning the smaller loop.

Routing across surfaces

The durable record owns task state. The decision channel holds human choices with links back to the record. The client channel holds only the agreed client-visible result. The live channel carries immediate handoff signals. The scheduled runtime owns the clock and its run receipts.

A single app can fill several functions, provided the boundaries are explicit. Conversely, a task can span several tools without creating several competing masters. Put the canonical task ID on each supporting artifact.

Before a backup acts, verify the outage or accepted handoff, inspect the source thread and reconcile prior side effects. Keep primary and backup responsibilities current in an owned routing record rather than hard-coding a model name into a permanent handbook.

The complete handoff contract

The sending coordinator checkpoints before compaction, shutdown or reassignment. The checkpoint names:

• Canonical task ID, exact ask and acceptance test
• Source and artifact revisions, with accessible locations
• Current packet state, owner and accountable function
• Work completed and evidence observed at the destination
• In-flight workers or queued external actions
• Allowed next actions, data boundary, approval gaps and stop rules
• Total budget, spent or unknown costs, remaining allowance and reserve
• Open findings, dissent, blockers and next click

The receiving worker reads the record, confirms access to the required source and destination, reconciles live actions and explicitly accepts the handoff. If those checks fail, report the missing step; do not imply ownership transferred.

A live message can announce the handoff. The lasting record must still contain enough context for a later worker. Secrets and unnecessary client data stay outside the handoff artifact. The receiver uses its own authorized route, not copied credentials.