# Observability ladder — the consolidated remaining work

outcome: every observability ask lives on ONE ladder, each slice ending in owner-visible evidence; the scattered plans stay canonical for their slices — this doc is the ordering and dependency truth.
status: ACTIVE — slices distributed 2026-08-16: slice 2 dispatched to codex terra/medium (owner order; earlier lane kill was accidental), 10 dispatched, 9 trigger-armed, 3-5 resume on slice 1.
source request: owner 2026-08-16 /brainstorm, verbatim ladder (consolidating scattered plans).

## Ladder (each slice = evidence you can SEE; canonical plan in parens)

1. **Registry live on the board — THE UNLOCK** (2026-08-15-live-status-registry.md): receipt_trail backend in the land queue behind the astro gate fix; then the acceptance walk — claimed → landed → deployed filling a card's timeline untouched; killed worker → "worker lost" within a sweep. Everything below depends on this.
2. **Job stage chips** (2026-08-16-job-stage-observability.md, spec authored): machinery stamps spec/build/verify/land/deploy/live; strip lights from latest stamp; honest fallback stays. Dispatched to codex terra/medium 2026-08-16 (lands dark until slice 1 deploys).
3. **Drawer D4+D6 — act from the board** (2026-08-15-requests-drawer-actions.md): Dispatch button + per-task routing honored verbatim. Drawer lane resumes on slice 1 deploy.
4. **D5 right-click menu** (same plan): Edit/View/Delete/Stop/Kill, state-gated, Kill pid-verified.
5. **R1 live progress tail** (same plan): the claiming session's latest line ticking on the card.
6. **Queue mirror + canary row** (registry plan queue-mirror section + 2026-08-16-remote-reliability-ladder.md S2): ticket journeys queryable on the board; canary row with green timestamps; S7 violation lines surface here.
7. **R2 deliveries timeline strip** (drawer plan): bottom bar from deployed stamps, click filters the batch.
8. **R3 answer box + R4 "not what I meant"** (drawer plan): one agent inbox shared with Telegram replies; reopen-with-history.
9. **Notifications settings UI — N4** (2026-08-15-notifications-layer.md): toggle matrix + journal strip. BLOCKED on N1–N3 landing (pipeline built, gate died on the now-fixed env; relaunch pending factory green). Trigger: when the notifications pipeline lands+deploys, N4 goes to a lane.
10. **Hooks page telemetry** (board row manual-29381635baa6770f, the recovered forgotten ask): per-hook fire counters, 7-day SUSPECT / 30-day removal-candidate aging, on the Hooks page. Independent — dispatched 2026-08-16.

## Dependencies in one line

1 unlocks 3–5 (2 lands dark against its schema); 6 rides registry mirror + canary landing; 7–8 follow drawer R-slices; 9 waits on the notifications pipeline; 10 is independent.

current receipt: ladder registered 2026-08-16; slice 2 codex-dispatched, slice 10 lane dispatched, slice 9 trigger armed, 3–5 armed on the registry ticket watch.
next executable action: slice 1 ticket lands → acceptance walk → resume drawer lane.