Team systems
Multi-agent handoff playbook
Switching from Grok to Claude to a local model should not reset truth. This playbook is how we move work across agents on LYGO projects without relying on “read the whole chat.”
The packet
Every handoff packet contains:
- Goal and non-goals
- Current status (green / yellow / red) with reasons
- File map (paths that matter)
- Continuum capsule or hash list
- Open questions for humans
- Next three actions only
If a packet lacks done checks, it is a diary entry, not a handoff.
Advertisement
Roles
| Role | Job | Champion lens |
|---|---|---|
| Builder | Change files | ARKOS / OMNIΣIREN |
| Verifier | Re-check claims | Δ9RA / ÆTHERIS |
| Integrator | Merge and release notes | SANCORA / Lightfather |
| Human owner | Consent and publish | always human |
Failure modes
- Story without files — reject the handoff.
- Files without claims — seal before switching agents.
- Claims without re-verify — verify is the first act of the new agent.
- Secret leakage — redaction pass before packet paste.
30-minute drill
- Pick a tiny task.
- Complete it with Agent A.
- Seal Continuum claims.
- Open Agent B with only the packet (no prior chat).
- Agent B must re-verify and extend work.
If B cannot proceed, the packet was incomplete — improve the template, not the mythic language.
