CK-1 <short title> Decide
- Decision level
- Work
- What it is
- <one or two sentences; assume no prior context>
- Options
- A. <option>
- B. <option>
- C. <option>
- Lean
- A — <one-line reason>
- Needed by
- Thu 2026-01-08 17:00 <PT> — <what waits until then>
<Project> Check-in Desk
Last updated: Thu 2026-01-01 09:00 <PT> · operator <operator name> · maintained by <role that keeps this page current>
1Decisions waiting
1Actions only you can take
0Deadlines this week
Decide
Decisions only you can make. Each stays open until you answer it.
CK-6 <an ask another desk owns> Decide
Owned by <other project> CK-9. Answer it there; this entry closes with it.
Do
Actions only you can take. Nothing here can be delegated back to a delivery role.
CK-2 <short title> Do
- What it is
- <what the operator specifically must do, and why it cannot be done for them>
- Needed by
- no date — <what stays blocked until it is done>
Decided by the team
Decisions made within the team's own authority. Made, owned, and recorded here so you can see them; reply by ID if you want one revisited.
- CK-3 (2026-01-01, <role>) — <what was decided> — Why: <one-line reason> — Status: done: <optional detail>
Already answered
Closed asks, newest first. Dated, kept forever, IDs never reused.
- CK-4 (2025-12-31) — <one-line summary of the ask> — Ruling: <what was decided>
- CK-5 (2025-12-30) — <one-line summary of the ask> — Ruling: withdrawn — <why it no longer needs an answer>
How to reply
Reply by ID, in chat.
Reply by ID, in chat. Examples:
CK-1 fine·CK-1 no, use <alternative>CK-2 doneCK-3 revisitto reopen a team decision