Integration branch: <main>
Landing lock: <default: cr-land.lock in the git common directory | a path in CR_LAND_LOCK>
Heavy-job lock: </tmp/cr-heavy.lock>
Journal:
Desk:
Tracker: <how to read it, e.g. bd ready>
Last reminder to the owner:
How to brief
Brief files: . One file per brief, named `.md`, written
before it is sent.
Runner
Command
Claude Code cloud
runners/claude-code-cloud/cr-cloud brief <session> <file> (queues it and returns; 3: not delivered, tell the owner first)
Local worktree
nohup runners/local/cr-worker brief <profile> <file> >/dev/null 2>&1 & (75: in a turn, try next run)
A status question uses the same command with the question in the file.
The brief states the model and the effort (docs/protocol.md, Model and
effort): the strongest model at high effort for long-horizon, architecture,
security-sensitive or hard-merge work; a fast model at medium effort (high
when harder) for well-specified epics.
How to create a worker
Only when “Workers created by the coordinator” above says authorised.
Submit the routine file with the routine tool of the coordinator’s session
(runners/claude-code-cloud/README.md). Record the routine at once. On the run
after it fires, read its run for the session id, and fill the worker’s row.
How to land
Under the landing lock, after checking the sha is not already landed
(docs/coordinator-loop.md § Two coordinators):