Part 1 · Operator’s Guide

Job Packets

A task record another worker can continue.

Public teaching edition · 1 October 2026

The job packet

A packet carries the conversation across sessions: the ask verbatim, owner and function, decisions, checkpoints, QA, artifacts, next click and verification. Start with one file; add tooling when the number or consequence of tasks calls for it.

The packet states are OPEN, CLAIMED, QA, DONE and PARKED. PARKED is a dated wait, with a reason and recheck. It is not a place for forgotten work. A required review still outstanding belongs in QA.

Three checks matter especially: existing competing work, the required review, and the intended delivery lane. The documented packet tool can reject an external-delivery record when recorded checks fail. It does not itself send mail or publish a page. Preventing an action requires the actual sending or publishing route to invoke a pre-action gate and honor the result.

The detailed reference provides a copyable packet template and the documented command names. Do not substitute invented validate or release commands for that implementation's lint, handoff, park and close lifecycle.

Seven useful requests

Say this The worker should do
Do this task Search for existing work, identify authority, create or use the packet
Pick up this task Read the packet, source revision, last checkpoint and next click
Hand this to another worker Transfer the same record and obtain acceptance
Check this work Open the artifact and standard; report evidence and disagreements
Compare these drafts Keep a bake-off within the agreed audience; recommend one winner
What is happening with this task? Read the canonical record and distinguish current observation from old status
Close this task Verify destination evidence and required QA before marking DONE

A vague title may match several jobs. Resolve the task before changing state. Handoff does not require the human to carry messages or files between agents when an authorized supported route exists.