Handoffs

Persist information when it provides auditability, resumability, debugging, cross-agent consumption, or later synthesis—not merely because a runtime can store it.

Three classes

Ephemeral coordination

Use native status, short clarification, and bounded parent/peer messages when the result is only needed during the current run.

Durable coordination record

Use a task assignment, decision request, block, acceptance state, or recovery record when orchestration may resume later. A native task/message broker is optional; _workspace/ is the portable fallback.

Durable artifact

Use deterministic files for plans, review evidence, experiment ledgers, integration reports, and outputs consumed across sessions. Follow the repository’s _workspace/ naming contract.

Failure semantics

Every delegated workflow must account for spawn failure, unavailable tools or models, permission denial, workspace setup failure, communication failure, resource conflicts, partial worker failure, and missing synthesis branches.

A missing runtime feature is a visible compatibility result, not a silent weakening of correctness. Serialize conflicting work or stop with an actionable explanation.