[JacobStephens2]

Summary

The domain decisions from grilling #212, ahead of its Spec. No code changes, and thirdshift pickup does not exist yet.

 CONTEXT.md
+  Claim          # ready-for-agent swapped for in-progress when a Run or Spec run takes an issue
+  Pickup run     # one pass, no Issue URL: takes the lowest-numbered Ready issue
+  Ready issue    # what a Pickup run may take
+  Claim limit    # open Claims at which a Pickup run takes no more
   Run, Architect run, Architect plan, Run notification   # now mention the Pickup run
 docs/adr/
+  0009-the-operating-system-schedules-thirdshift.md      # no daemon: cron starts each pass

thirdshift pickup            (one pass, started by cron)
  lock held, no Ready issue, or at the Claim limit  -> skipped: exit 0, no Run notification
  else take the lowest-numbered Ready issue
    Claim it
    dispatch as `thirdshift <Issue URL>` would   -> one Run notification

Part of #212, which stays open for the Spec.

Evidence

• Before: grep -c "Pickup run" CONTEXT.md is 0; docs/adr/ ends at 0008.
  After: the four terms are defined, and ADR 0009 exists. Documentation only, so no test run applies.

Merge Danger

Door: two-way

The glossary describes behaviour that is not built yet, as it did for the Architect plan before #237 landed. Reverting is one commit.

Blast Radius: docs

Agents read CONTEXT.md in every session, so until the Spec lands a session may read Claim and Pickup run as existing behaviour.

🤖 Generated with Claude Code