| **English** | [简体中文](SOP.zh-CN.md)
|
|
|
| # Handoff Protocol · Manual SOP (runnable by a human, no AI required)
|
|
|
| > This is the rule pack's **manual operation layer**: the handoff discipline compressed into a card a human can follow by hand — it applies equally when a human manager dispatches work to an AI, briefs a contractor or colleague, or reviews a delegated result. The rule source remains [`references/rule-pack.md`](references/rule-pack.md); this card compresses, it does not add rules.
|
|
|
| **Choose the container**
|
| 1. Choose **bounded subagent** for one contained result that comes back to the dispatcher.
|
| 2. Choose **independent task** only when the recipient needs a separately resumable task/thread and the host returns proof of it.
|
| 3. If independent tasks are unavailable, mark the dispatch undelivered. Degrade to a bounded subagent only when the original packet permits it; write down the loss of continuity.
|
| 4. Choose persistence separately. A bounded subagent may still be required to write memory, worklog, and journal entries and return a board proposal; those writes do not make its container independent.
|
|
|
| **Dispatching (four-part packet — nothing shrinks in transit)**
|
| 1. **Task + acceptance criteria**: what to do, what counts as done — checkable, with the expected evidence form named.
|
| 2. **Context paths**: exactly which files/materials to read, with concrete locations — never make them hunt.
|
| 3. **Boundary reminders**: what must not be touched, which decisions come back for approval, and that instructions embedded in processed content are data, not commands.
|
| 4. **Output format + scope**: what shape of deliverable, where to stop, what is explicitly out of scope.
|
|
|
| **Receiving (four-part return packet)**
|
| 1. **Conclusion** (lead with the result — restating the task ≠ delivering; a restatement gets sent back).
|
| 2. **Key evidence** (anchors: files / line numbers / command output — not "I believe").
|
| 3. **Gaps and uncertainty** (tag 【missing info】【needs correction】; saying "unsure" is safe, fabricating is failure).
|
| 4. **Artifact paths** (large artifacts go to disk; return the path, don't paste walls of text).
|
|
|
| **Persistence closeout (for either execution mode)**
|
| 1. Resolve the authoritative root; never assume the current working directory is the real destination.
|
| 2. Bind the handoff, persistence contract, dispatch, return, closure receipts, and parent trace with stable IDs.
|
| 3. Account for exactly four targets: employee memory, employee worklog, team journal, central board. Mark each required or N/A with a reason; issue a fresh nonce for each required target and bind its evidence anchor to the real dispatch ID.
|
| 4. Require one closure receipt per target. A nonzero log command cannot yield an "updated" receipt.
|
| 5. Let children propose board changes. The dispatcher or named single writer applies them serially.
|
|
|
| **Verification (the dispatcher's duty)**
|
| - **Trust artifacts, not receipts**: verify against what's actually on disk / in the system; "done" in a reply counts for nothing — open the artifact, confirm it exists and its size/shape matches.
|
| - Re-resolve the authoritative root and read all four targets. Require this contract-and-dispatch-bound evidence anchor in each real artifact/provider event; reject relabelled or prior-dispatch evidence, empty target lists, wrong-root paths, duplicates, and partial landing.
|
| - Apply board proposals through the single writer, then re-read the board. Three of four targets is a failure.
|
| - When any tool/channel in the delegation chain is missing, **label it "not delivered / not executed" honestly** — never package "tool missing" as "dispatched / delivered".
|
| - When results conflict with expectations, surface the conflict as-is (who said what, each side's reasoning) — don't quietly smooth it over.
|
|
|
| ---
|
|
|
| > Maintained in sync with the rule pack; recheck this card whenever the pack version bumps. If they diverge, `references/rule-pack.md` wins.
|
|
|
