Sort sessions and projects into decisions.
The system gets lighter when every open loop has a status. You do not need to finish everything. You need to decide what each thing is.
Simple layer. Every session or project becomes one card. The card must answer: continue, extract task, validate proof, archive, or wait.
This mirrors the loop-engineering bucket pattern: Do-now, Needs-user, Blocked, Out-of-scope. The cockpit uses friendlier lanes so you can operate quickly.
Try the board
Click a destination. The sample loop moves to the lane you choose.
Session triage prompt
Use this when a Codex, Claude Code, Kimi, or Grok thread feels important but vague.
Read this session and extract: 1. final useful result 2. unfinished blocker 3. exact next action 4. proof gate 5. archive / continue / validate / convert-to-task verdict