Put it in the right place
SparkWorth remembering, but no committed venture home or timing yet.
WorkProjects, milestones, wishes, and scheduled outcomes that are not executable now.
KanbanExecutable now, with one next action and a definition of done.
Open → run → receipt
1 · OpenCreate or promote a task only when it can start. P0 gets 4 hours, P1 one day, P2 three days, and P3 seven days before Timing review.
2 · Start / ResumeUse the card action, choose Codex, Claude Code, Cursor, or Antigravity, then paste Cairn's copied prompt into that tool.
3 · Divide safelyEach coding workstream uses its own branch and worktree/environment. Declare owned files and production-write domains; overlap may warn or block.
4 · Keep continuity honestWhen focus changes, record progress, blocked, abandoned, or handoff with current commit, PR, tests, and exact next action.
5 · Finish onceWorker completion is not a release. The Release Captain integrates, deploys, verifies live, then posts the one versioned release finish and bundled receipt evidence.
Do not let Ready become storage
A Timing review badge means the best start window passed. Start it, rewrite the next action, return future work to Work, or close/park it. Do not keep refreshing something that is not truly ready.
Receipt shorthand
Starting from a card is recorded automatically. Use non-versioned workstream updates for progress, blocks, and handoffs. Review-ready is progress, not finished. Only the Release Captain posts release.finished through the release-finish endpoint after merge, deploy, and live verification.
Full contracts: _command-center/TASK-OPERATIONS.md and _command-center/RELEASE-COORDINATION.md.