Mindbridge · engineering status

Track board

Your four pinned tracks, one column each, matching the sessions you run. Everything else sits on the bench below in declared order. Nudges fire where the labels disagree with that order.

Order and impact lines come from docs/status/track-order.json, which is written by hand — no query can derive "what a user cannot do while this is broken". Everything else is read from gh issue list. Generated 2026-08-17 09:22 UTC.

🔴 security holds 1 p0 and is not pinned — your declared order puts it on the bench while the labels say it is the worst thing open.

Pinned — one per session

ama-trust

27 open · – p0 · 3 p1

⚠︎ Needs a ruling from you

ADR-144 (the AMA turn judge) is proposed, not accepted — four open questions block any…p2#3309

Regina asks a question about their own spreadsheets and gets nothing back.

AMA: verify arithmetic in the emitted answer, not just in derive()p1#2899
AMA: coverage as a structured ledger, not a prose caveatp1#2900
AMA: a renderable attachment scored INVISIBLE would leak if disclosure enforcement is…p1#3096

1 standing ruling

The AMA turn ceiling stays unbounded — characters were never the binding constraint, the 60s deadline is (2026-08-08).

attachment-truth

5 open · – p0 · 3 p1

Documents do not reach the graph intact, so every answer is thinner than the data allows.

message_attachments: a message can carry N files (ADR-145 D1/D2)p1#3324
A document's audience can be decided by an arbitrary carrier message (ADR-145 D4)p1#3325
The library caps documents at one per message via a PRIMARY KEY (ADR-145 D5)p1#3326

viewer-truth

14 open · – p0 · 11 p1

A person sees themselves as more than one user — disjointed identity across surfaces.

fix(compose): proactive nudge + AMA narrative prose must attribute the sender by…p1#1314
nodes_v2.properties.user_id owner-stamp is never cleared once written, and a stale…p1#3080
W3: the client resolves the viewer itself, and now disagrees with the serverp1#3148

ama-disclose

8 open · 2 p0 · 3 p1

⚠︎ Needs a ruling from you

AMA-DISCLOSE became the largest disclosure queue in the repo without anyone deciding it…p2#3295

Content reaches someone who should not see it. Nobody experiences this until it is catastrophic, which is why it loses to everything above and needs a standing allocation instead.

AMA: facts fail OPEN on missing audience while messages fail CLOSED —…p0#2905
traverse_graph renders the RAW canonical_name in a candidate's title at…p0#3155
business_context ships to the client ungated by disclosure levelp1#2824

2 standing rulings

Reading a full question and answer in-process is permitted; the privacy boundary is the judge's OUTPUT schema, not its input (2026-08-14).
Any model call over answer text routes through the already-allow-listed provider path, or the build does not start (2026-08-14).

The bench — everything else, in declared order

#	track	open	p0	p1	what breaks without it
5	wire-truth	3	–	1	What WhatsApp actually carried never reaches us — senders unnamed, replies and mentions lost. next: WhatsApp senders with no usable pushName render as… #3054
6	connector-truth	2	–	2	A customer connects a source and it dies days later. 5 of 9 production Gmail connectors are dead now. next: chore: Complete Google OAuth App Verification for Gmail… #1241
7	security	4	1	3	Cross-tenant exposure and privilege defects — one tenant's data reachable from another. next: idx_node_aliases_person_per_source is a cross-tenant… #2968
8	edge-truth	7	–	4	Edges do not mean what they say, so traversal answers are confidently wrong. next: fix(extraction): relationship typing structurally wrong… #1465
9	nightly-nudge	8	–	2	Proactive cards reach the wrong people, or nobody. next: Nightly-nudge event extraction has no tier or… #3116
10	billing	2	–	2	Signup cannot complete, or usage is not metered against what a contract promises. next: Web Google signup can never complete — the OAuth… #2768
11	retention	3	–	2	Deletion is promised in customer copy and no tenant-wide deleter exists. next: ADR-138 stage 6: the tenant-wide deleter has no… #2941
12	test-truth	11	–	1	Coverage that reads as present and cannot fail — the suite is green about things it never checks. next: Suggested-questions node-side tenant_id predicate is… #3016
13	measurement	1	–	1	Nothing tells us when a customer's ingestion has stopped. next: Nothing tells us when a customer's connector dies — the… #3060
14	llm-cost	3	–	–	What providers invoice us is not reconciled against what we think we spent. next: Cost alerts fire into the void — cost_alert_status()… #3131
15	mr-drain	3	–	–	Suppressions and debt accumulate faster than they are drained. next: MR-DRAIN Part C: ratchet the 603 hook suppressions… #2976
16	doc-truth	1	–	–	The feature catalog describes a product we do not have. next: The status-page churn's biggest lane is still open:… #3316
17	regina-staging-gate	1	–	–	Regina's full-fidelity staging and its gated drain. next: fix(source): Exchange and Slack live drains write one… #2875
–	ama-trust:spreadsheets unranked	6	–	–	next: AMA renders a spreadsheet inline by reconstructing… #3193

95 open issues carry no track, 0 of them p0 or p1. In a one-session-per-track workflow an untracked issue has no tab, so it is nobody's.

1 housekeeping nudge

ama-trust:spreadsheets is unranked — 6 open, and no entry in track-order.json, so it sits outside your ordering entirely. Rank it or fold it into its parent track.