How Work Moves

How work moves

1. Read the current task, authority, instructions and relevant source. Check the revision and destination.
2. Find existing work before creating a new packet. Claim shared work using the team's established mechanism.
3. Prepare a bounded plan and acceptance test. Set the total budget and stop rule before dispatching workers.
4. Do the work in the system that owns it. Save a checkpoint before a session ends or context is lost.
5. Give a reviewer the artifact, request, source and standard. Preserve disagreements and repair real defects.
6. Deliver only through the authorized route. Read the result back at the destination and record what was observed.
7. Update the same task record. Save the lesson and next action; close only when the required checks are complete.

A handoff is accepted when the next owner can open the same canonical artifact and revision, understands the current state and acceptance test, and has the authority and tools to continue. Include queued work, remaining budget, blockers and disagreements. Until acceptance, the current coordinator retains responsibility.

A judgment brief should contain the exact ask, decision needed, permitted actions, constraints, evidence links, alternatives, uncertainties and required output. It saves attention without replacing the evidence. A reviewer may request the source passage that could change the answer.