Delivery board for each project: what is in progress, and what has landed. The work is assessment, automation, and AI enablement. The sheet is the system of record. Redis coordination is in progress and is not a trusted live read.
Current path and destination Comparison not green
Counts load from the published delivery snapshot. Not yet refreshed. The same file feeds Ops. This is not a live bus, and it is not a Redis dashboard. Landed means production and verified. A merge is not landed.
Path
Role today
What is measured
Sheet / communication board
System of record
Not yet refreshed.
Redis coordination
Destination. In progress. Not trusted live.
The comparison gate is not green. No Redis count is published. Dual-run is not a product surface.
Ops keeps the per-agent scorecard, Gantt, CI status, and lane rates visible. Those figures are the measured operations picture. They are not Redis.
Project delivery Snapshot
Milestones by project. Counts load from the published delivery snapshot. In progress is anything not yet production and verified.
Conference Not yet refreshed.
In progress
Hear all conference contributors — Staging · pending · Claude
Shared OKF context and direct agent addressing — Staging · pending · Claude
Agents understand the shared screen — Backlog · pending · Claude
Independent native-duplex acceptance — Test · pending · Aya
Conference join, feedback, and opt-in record — Test · recorded · Cody
Conference create gate and duplex join page — Test · recorded · Cody
M7 Agents QA (planned) — Test · pending · Aya
Landed
Conference line: the owner’s browser telemetry reaches the gateway log
Conference line: STT timing, sealed transcript and agenda read-back
Conference line: the five fixes from the owner’s 07:25Z call
SFDC24 Not yet refreshed.
In progress
Ops refresh, roles and mobile repair — Test · blocked · Greg
Drop client names from the public board — Test · recorded · Cody
Conference mandate without personal names — Test · recorded · Cody
M6 Site land (planned) — Development · pending · Cody
M8 HITL release gate (planned) — Production · pending · Greg. External invites stay closed until owner GO.
Landed
Delivery Gantt at the top of Ops
Guided entry and host-nudge source release
Cody and current agent roles
Release clock morning checkpoint
Ops delivery refresh
Ops: the delivery snapshot only moves forward
Ops: the per-agent scorecard shows measured figures
Ops: the last conference’s action items, first on the page
Platform Not yet refreshed.
In progress
Nothing in progress on this snapshot.
Landed
Python-managed delivery feed for all projects
WhatsApp standby reply says a message is queued, not that it was seen
Open milestones Snapshot
Four open milestones from the published delivery snapshot. Each names a title, a milestone, who is working now, who worked before, what changed, and the quality of that work. A number alone is not a label. Not a live roster. The full board is above.
Hear all conference contributors
Milestone
Conference · staging
Working now
Claude
Worked before
Aya and Cody, on review
Changes
Source is merged. Staging and production are not verified on the snapshot.
Quality
Pending. Not landed. A merge is not production verified.
Ops refresh, roles and mobile repair
Milestone
SFDC24 · test
Working now
Greg. The row is blocked.
Worked before
Claude, on release
Changes
The lane waits on an owner replan or an explicit close.
Quality
Blocked on the published snapshot. Not landed.
Independent native-duplex acceptance
Milestone
Conference · test
Working now
Aya
Worked before
Claude
Changes
Acceptance is still open: hearing everyone, including while someone is speaking.
Quality
Pending. Not landed. This row is not a guest invitation.
M8 release gate (planned)
Milestone
SFDC24 · production, still pending
Working now
Greg
Worked before
Delivery lead
Changes
External invites stay closed until the owner records GO.
Quality
Planned. Production is pending, so this row is not landed.
Purpose v1
Make waits visible, name who is dropping the ball, cut silent peer waits without waking absent agents, and run a short PDCA loop so the same stall does not repeat.
Source of truth: the sheet (Blackboard) remains the system of record. The board above reads the published delivery snapshot. Redis coordination is being built beside it and is not trusted live.
How we work together
One bus, named roles, explicit AGREE before cross-agent publish holds.
OwnerPriorities, his six, irreversible calls. Agents decide the rest and report outcomes.
Greg — Delivery LeadTrack, stitch, surface blockers, cut-wait when peers are silent past SLA. Not hot-path implementer.
ClaudeImplementation / release of controller and site; chair packages. Must answer attaches and chair asks.
AyaStrategy, sequencing, architecture / acceptance gates. Holds pub when AGREE is missing — names it on the register.
JennyAdversarial reasoning via board waker. Needs private diffs attached before it can move.
CodyExact-SHA code gate on every PR. Comment GO / NO-GO only; no silent stalls on the gate.
Board
Sheet — the communication board is the system of record.
Coordination layer — in progress. Not live on this site, and it does not replace the sheet.
Holds — a hold shows on the register below. It is not a private pause.
Cost. Spend is a first-class design constraint, with quality and fit. Aya owns that discipline. Task-level routing stays parked until Redis coordination is a trusted live read. Redis is not the system of record.
Open Blocker Register Seed
Names who is waiting, on whom, since when, and the next move. Rows marked dropping the ball highlight the silent peer. Static seed for v1 — durable board stays source of truth; this page must not invent progress.
id
what
waiting_on
blocked_agent
since
owner
next_move
status
BLK-133-DIFF
Jenny blocked on #133 — Architecture PDF AGREE gate. The packet is not attached, so review cannot finish.
Claude (attach private diff)
Jenny
180 min seed
Greg (Delivery Lead)
Greg cut-wait — document cut; do not wake silent Claude for this peer wait; Jenny proceeds on available public surface or parks with named gap
Cut-wait
BLK-137-CHAIR
#137 — Chair quiet-hold. NO-GO until the 2pm review. No RESULT on the board.
Claude (silent ~5h)
Fleet / Delivery Lead visibility
300 min (~5h)
Claude
Surface owner: Claude is dropping the ball. Past 45m SLA with no RESULT. Claude posts RESULT or BLOCK with next_move; Greg keeps register hot
SLA breach
BLK-GEM-AGREE
Aya held publish waiting Jenny AGREE
Jenny (AGREE)
Aya
40 min seed
Aya
Jenny posts AGREE or NO-GO on the board. If silent past 45m, Aya surfaces owner and either cut-waits with documented risk or parks the pub — no silent hold
Waiting AGREE
Register fields
id
Stable blocker id (e.g. BLK-133-DIFF)
what
One sentence: the stalled work
waiting_on
Who must act (name the agent or owner)
blocked_agent
Who cannot proceed
since
Wait age in minutes. Overnight seed until a board clock lands.
owner
Who drives clearing this row
next_move
Concrete next action; include cut-wait if applicable
status
open · sla-breach · cut-wait · waiting-agree · closed
Wait control charts Overnight seed
Who waits → on whom, and how long that wait has run. The dashed line is the 45-minute peer-wait SLA. The solid line is the mean of that row’s seed. A point above the SLA is past the limit. Not a live clock.
Jenny → Claude
#133 — Architecture PDF AGREE gate · BLK-133-DIFF
180 min
Chair → Claude
#137 — Chair quiet-hold, NO-GO until the 2pm review · silence · BLK-137-CHAIR
300 min
Aya → Jenny
AGREE · BLK-GEM-AGREE
40 min
SLAs
45-minute peer wait. If a peer wait has no RESULT (and no visible progress) for more than 45 minutes, surface the owner of the stall on this register. Name who is waiting, on whom, and since when.
Mechanical cut-wait — Delivery Lead may end a peer wait without waking a silent peer. Record the cut on the register and on the board; do not doorbell an absent agent just to clear the row.
No silent holds — holding a publish for AGREE is a register row, not a private pause.
Owner asks — his six and irreversible calls still wait on him; those are not cut-wait targets.
PDCA loop
Define → Review → Monitor → Control → Improve. Short cycles; board evidence over chat memory.
1 · Define
Name the wait, the blocked agent, waiting_on, and the RESULT that clears it. Open a register row.
2 · Review
Delivery Lead reviews open rows against the board. Confirm since-times and whether AGREE / RESULT landed.
3 · Monitor
Watch the 45m clock. Escalate to SLA-breach styling when breached. Do not bury waits in chat.
4 · Control
Cut-wait, re-route, or surface owner. Keep durable board as source of truth; page seed mirrors it for v1.
5 · Improve
After close: one lesson (why the wait lasted, what doorbell or AGREE rule failed). Feed metrics below.
Metrics for continuous improvement
Time-to-surface — minutes from wait start until register row exists
Peer-wait age — distribution; count of rows past 45m
Cut-wait rate — cuts per week; cuts that later needed a re-wake
Silent-peer incidents — SLA breaches by agent (who dropped the ball)
AGREE latency — time from AGREE ask to AGREE / NO-GO / cut-wait
Repeat stalls — same id-pattern or same waiting_on recurring within 7 days
The delivery counts at the top are the measured snapshot. The peer-wait charts below are an overnight seed, not a live clock. These named measures are the series still to collect. Redis does not supply them, and it is not the system of record.