<Project> Work Board

Last updated: Mon 2026-01-05 09:00 <PT> · maintained by <role that keeps this board current> · desk: <Project> Check-in Desk

2In motion
2Waiting
1Backlog
2Due this week
0Controls never run

Open work by initiative: no initiative 4 · <optional initiative> 1 · 1 from peers · 1 run by software · 0 agent-scheduled · 0 person-triggered

In motion (2)

Doing now, then committed to a date or a week. Ordered by needed-by.

WI-1 <what is being done><optional initiative> doing

Owner
<role>
Belongs to
<tranche or issue record, e.g. issues/0042.md>
Needed by
Fri 2026-01-09 17:00 <PT>
Unblocks
WI-2 (<what is next>)

WI-2 <what is next> committed

Owner
<role>
Belongs to
<tranche>
Depends on
WI-1 (<what is being done>)
Needed by
Fri 2026-01-16

Waiting (2)

Blocked on a desk ask or another item, or held for an event with a date. Nothing here is forgotten; each names what it waits on.

WI-3 <what cannot move until the Operator answers> blocked

Owner
<role>
Belongs to
<tranche>
Waits on
the Operator's answer to <project> CK-7

WI-4 <what waits for an outside event> held

Owner
<role>
Waits on
<peer read-back or statement date> — by Mon 2026-01-12

Backlog (1)

Wanted, not yet committed, by initiative.

WI-5 <wanted, not scheduled>size Mbenefit M: risk retired backlog

Owner
<role>
Origin
asked by <peer project>, their item 3

Controls (2)

Recurring assurance work. A control never leaves the board; its next due date is computed from its cadence. Daily controls are always due and are not counted in the week.

Done (1)

Closed with proof, newest first, by initiative. The proof is cited, not judged here; a close without an artifact is shown lighter.

Dropped (1)

Closed without doing, newest first, with the reason. IDs never reused.