The worst open items first, then every track with the one thing that moves it next. Counts and the NEXT column are measured at build time from the same fetch as the what's-next queue, in global queue order β and a track page may name a different next item by its own ordering criterion, which is by design: the track page is authoritative within its track.
| Track | Open | State | One line | Next |
|---|---|---|---|---|
| EDGE-TRUTH | 7 | Active | Stage 5a live β AUTHORED means authorship in 100% of its rows; the relationship-typing bug is next. | #1465 fix(extraction): relationship typing structurally wrong β sister typed as spouse, PARENT b |
| WIRE-TRUTH | 3 | Active | Done-condition rests on the SQL-lane audience surface; the WhatsApp capture items are Mizo-facing. | #3334 Re-run the deterministic floor-invariant policy over the 138 legacy rows (follow-up to #32 |
| AMA-TRUST | 27 | Active | Spreadsheet queryability half filed and ordered; the sub-track stands at 6 open. | #2899 AMA: verify arithmetic in the emitted answer, not just in derive() |
| ATTACHMENT-TRUTH | 5 | Active | ADR-145 cluster: one file per message, audience by arbitrary carrier, recovery from maildir. | #3325 A document's audience can be decided by an arbitrary carrier message (ADR-145 D4) |
| AMA-DISCLOSE | 8 | Active | The disclosure queue β five p0, one client-reachable leak live now. | #2905 AMA: facts fail OPEN on missing audience while messages fail CLOSED β conversation-anchore |
| CONNECTOR-TRUTH | 2 | Active | The compliance pair β OAuth App Verification and CASA Tier 2 β both p1. | #1241 chore: Complete Google OAuth App Verification for Gmail (Restricted) + Calendar (Sensitive |
| TEST-TRUTH | 11 | Active | Coverage that reads present and cannot fail; every item is the same defect class. | #3016 Suggested-questions node-side tenant_id predicate is unproven β no fixture has a second te |
| VIEWER-TRUTH | 14 | Active | Reconciler live hourly; the client lane is next. | #3243 A linked account that resolves to no person node is silently dropped from the nightly nudg |
| RETENTION | 3 | Active | 30-day deletion promised, no tenant-wide deleter; over-deletion in the deleter that exists first. | #2941 ADR-138 stage 6: the tenant-wide deleter has no resumability design for a partial failure |
| DOC-TRUTH | 1 | Attention | Catalog drift 0; both open issues are gap-trackers, not work. | #3316 The status-page churn's biggest lane is still open: every track's prose lives in one file |
| LLM-COST | 3 | Active | Alerts fire into the void; reconciliation never automated. | #3131 Cost alerts fire into the void β cost_alert_status() has no delivery channel, and two are |
| MEASUREMENT | 1 | Held | Deferred by owner; the connector-liveness issue survives the deferral. | #3060 Nothing tells us when a customer's connector dies β the health score can't, and shouldn't |
| MR-DRAIN | 3 | Held | Paused for WIRE-TRUTH; resume at the ratchet. | #2976 MR-DRAIN Part C: ratchet the 603 hook suppressions (ratchet FIRST), then audit and drain |
| BUILDKITE MIGRATION | β | Stopped | Stopped by the owner β do not resume, do not propose. | β |
| REGINA-GOVERNOR | β | Clear | Deliberately closed; kept as a row so it reads that way. | β |
| SUPPORT-BRAIN | β | Held | Console merged and live; remaining work blocked on the stopped Honcho instance. | β |
| BILLING | 2 | Attention | Live, sealed grandfathered; signup can never complete. | #2768 Web Google signup can never complete β the OAuth full-page redirect destroys the form stat |
| SECURITY | 4 | Attention | Cross-tenant UNIQUE index (p0) plus three p1s; close defaults at the schema. | #2968 idx_node_aliases_person_per_source is a cross-tenant UNIQUE index (no tenant_id) |
| NIGHTLY-NUDGE | 8 | Attention | Needs a call: per-user opt-out is still a product decision. | #3116 Nightly-nudge event extraction has no tier or disclosure gating at all |
| REGINA-STAGING-GATE | 1 | Attention | SAP staging live; the PostgresβSQL Server pivot is drafted as an open PR β the box needs re-provisioning. | #2875 fix(source): Exchange and Slack live drains write one ingestion_runs row per message |
Untracked: 95. Untracked p1: 0 β the pile this page once tracked at 26 drained three ways during the 2026-08-14 reconciliation: labelled onto tracks, closed, or re-triaged. The total is derived at build time; the set itself is deliberately not enumerated here because it decays within a day of any filing β the what's-next page lists every untracked issue in order.
The rows above count labels, not issues. They sum to 103 against 99 issues on a track, because 4 issues carry two track labels: the disclosure cluster (issue #3283, issue #3284), the attachment-model cluster (issue #3325, issue #3327) and the nudge-audience predicate (issue #3243).
Sub-track: the spreadsheet cluster (6 open) is a cluster inside AMA-TRUST and is deliberately absent from every figure above.
Pages: every track has a source page in docs/status/ and a published URL on Cloudflare Pages, linked from the name below; the three non-track rows (BUILDKITE MIGRATION, REGINA-GOVERNOR, SUPPORT-BRAIN) have no page.
Catalog health: 2,604 rows, 2,522 citing a real path. Coverage: platform/ 1,045 cited rows, 5 uncovered files; website/ 206 cited rows, 0 uncovered files.