Roadmap audit

Last run 2026-08-20 04:04 EDT, 9h before this page was built. Every count here describes the roadmap as it stood then; anything filed since is invisible to it.

This page needs JavaScript to decide findings. The queue below is the same ledger, read-only. Any finding can also be applied by filing a decision issue naming its id — the same lane handles both.

Confidence	Which issue	Title	What changes
`high`	obot.roadmap#181	Requirement: Navigator phase 2 — working-set verification (split from #157)	Assign @jwildfire.
`high`	obot.roadmap#195	Requirement: the Navigator as operating officer — asks become requirements, and delivery is judged at closeout	Assign @jwildfire.
`high`	obot.roadmap#200	Requirement: roadmap discipline is measured — the sweep checks all seven repos, and the audit stops reporting stale	Assign @jwildfire.
`high`	obot.roadmap#205	Requirement: a real "since you last looked" — record page views locally, or say plainly that we cannot	Assign @jwildfire.
`high`	obot.roadmap#206	Requirement: the priced usage artifact refreshes on a cadence, or every surface says how old it is	Assign @jwildfire.
`high`	obot.roadmap#212	Requirement: a worker that stops — finished, stalled or dead — wakes the Navigator	Assign @jwildfire.
`high`	obot.roadmap#215	Requirement: a requirement says whose decision it carries — an agent's inference must not read as his approval	Assign @jwildfire.
`high`	obot.roadmap#218	Requirement: the dashboard reads like a news feed, not an audit log — rebuild the sessions and Navigator pages	Assign @jwildfire.
`high`	obot.roadmap#220	Requirement: his queue holds exactly three buckets — RC, decision, config — and the remainder is ours	Assign @jwildfire.
`high`	obot.roadmap#223	Requirement: every surface renders honestly on a machine with no history — before the move, not after	Assign @jwildfire.
`high`	obot.roadmap#227	Requirement: the dashboard's two views, literally — a session table with filters, and a filterable metrics dashboard	Assign @jwildfire.
`high`	obot.roadmap#229	Requirement: adversarial review of safetyCensus() — does it stay or go, before v1.1.0 publishes	Assign @jwildfire.
`high`	obot.roadmap#234	Requirement: one-off tasks — a small fix files against its goal, without a requirement to justify it	Assign @jwildfire.
`high`	obot.roadmap#236	Requirement: the admiral — a triggered manager, so finished work stops sitting and nobody has to remember to look	Assign @jwildfire.
`high`	obot.roadmap#238	Requirement: the morning fold, and the briefing it produces	Assign @jwildfire.
`high`	obot.roadmap#239	Requirement: the weekly briefing — the sink that keeps the daily at nine lines	Assign @jwildfire.
`high`	obot.roadmap#240	Requirement: the session skills the fold replaces — one retirement, five re-homings, and the notes that say so	Assign @jwildfire.
`high`	obot.roadmap#241	Requirement: an answer you clicked that nothing applied has to reach someone	Assign @jwildfire.
`high`	obot.roadmap#242	Requirement: does the briefing get read aloud — and at what cost to the words	Assign @jwildfire.
`high`	obot.roadmap#243	Requirement: merging is not deploying — the checkout tracks main, and consumers restart when it moves	Assign @jwildfire.
`high`	obot.roadmap#251	Requirement: a kill this house reports is a kill it confirmed — the liveness anchor reports success while the session survives	Assign @jwildfire.
`high`	obot.roadmap#252	Requirement: nobody can write to the board — the App is forbidden and the guard denies the only credential that works	Assign @jwildfire.
`high`	obot.roadmap#256	Requirement: work that never reached GitHub is invisible to every check we run	Assign @jwildfire.
`high`	obot.roadmap#257	Requirement: a thing he asked for has a delivery state, and something notices when it goes quiet	Assign @jwildfire.
`high`	obot.roadmap#260	Requirement: git pushes and commits still go out as him — the lane no token fixes	Assign @jwildfire.
`high`	obot.roadmap#261	Requirement: the highest-authority file the agents read has no owner, no history and no review path	Assign @jwildfire.
`high`	obot.roadmap#263	Requirement: config items are short local artifacts he can decide from, not a field form	Assign @jwildfire.
`high`	obot.roadmap#264	Requirement: a config item's claim is checked on a cadence, not asserted on the day it was filed	Assign @jwildfire.
`high`	obot.roadmap#265	Requirement: he answers a decision from the car, by voice, without a screen or an issue number	Assign @jwildfire.
`high`	obot.roadmap#266	Requirement: a decision artifact notices when its own premise expires	Assign @jwildfire.
`high`	obot.roadmap#267	Requirement: the judge can see the constraints it is judging against	Assign @jwildfire.
`high`	obot.roadmap#272	Requirement: branch protections, live before any scheduled session runs	Assign @jwildfire.
`high`	obot.roadmap#274	Requirement: SafetyCensus stays and is rebuilt on metrics and reports — design first	Assign @jwildfire.
`high`	obot.roadmap#275	Requirement: what the fleet spends is measured before it is spent	Assign @jwildfire.
`high`	obot.roadmap#278	Requirement: what comes next is written down — a ranked head, tiers below, before any clock runs	Assign @jwildfire.
`high`	obot.roadmap#279	Requirement: a step-by-step IQ for the new laptop — the chance to fix rather than replicate	Assign @jwildfire.
`high`	obot.roadmap#280	Requirement: an open decision artifact has an episode he can answer from a car	Assign @jwildfire.
`high`	obot.roadmap#281	Requirement: safetyGraphics and safetyCharts back on CRAN — remove the Tendril chart	Assign @jwildfire.
`high`	obot.roadmap#282	Requirement: the usage analytics run on a cadence, and the page says when it last did	Assign @jwildfire.
`high`	obot.roadmap#70	Mark PRs ready for review and request @jwildfire review when ready	Set board Status to Released (currently Backlog). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#201	The nightly audit cannot tell a clean night from an unmeasured one, and its off-board rule only sees labelled requirements	Set board Status to Released (currently Backlog). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#203	Requirement: one information architecture, two audiences — symmetry between the private dashboard and the public hub	Set board Status to Released (currently Backlog). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#204	Build the roadmap-page spike: three rendered directions and the decision artifact	Set board Status to Released (currently Development). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#209	The roadmap page's draft-release dedupe never matches: \d lost its backslash in a template literal	Set board Status to Released (currently Backlog). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#210	A decision folded into a successor still counts as awaiting him	Set board Status to Released (currently Backlog). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#211	Requirement: rebuild the roadmap page on D0018 — the queue in front, the catalog behind	Set board Status to Released (currently Development). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#219	Build the news-feed sessions and Navigator pages — one implementation, not directions	Set board Status to Released (currently Development). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#221	Retire D0014, D0015 and D0016 and replace them with one readiness assessment for scheduled sessions	Set board Status to Released (currently Development). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#224	Hub header: a version number, and a hover that tells the truth about when the page shipped	Set board Status to Released (currently Development). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#237	Requirement: the org chart — who does what, what each may never do, and which failure created each role	Set board Status to Released (currently Development). — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#66	Add next/back navigation between safety.viz example pages	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#81	Close out safety-histogram fork and remove from roadmap	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#180	Requirement: the Operations Dashboard — my todo list, with blockers, where I answer decisions	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#181	Requirement: Navigator phase 2 — working-set verification (split from #157)	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#226	Requirement: goal #73 says what it is now — a current body, five workstreams, and a bounded backlog	Add it to the obot Roadmap project at Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#238	Requirement: the morning fold, and the briefing it produces	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#239	Requirement: the weekly briefing — the sink that keeps the daily at nine lines	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#240	Requirement: the session skills the fold replaces — one retirement, five re-homings, and the notes that say so	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#241	Requirement: an answer you clicked that nothing applied has to reach someone	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#242	Requirement: does the briefing get read aloud — and at what cost to the words	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#246	Requirement: what the machine may say about itself in public — session names and draft-release titles	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#251	Requirement: a kill this house reports is a kill it confirmed — the liveness anchor reports success while the session survives	Add it to the obot Roadmap project at Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#252	Requirement: nobody can write to the board — the App is forbidden and the guard denies the only credential that works	Add it to the obot Roadmap project at Development. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#256	Requirement: work that never reached GitHub is invisible to every check we run	Add it to the obot Roadmap project at Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#257	Requirement: a thing he asked for has a delivery state, and something notices when it goes quiet	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#260	Requirement: git pushes and commits still go out as him — the lane no token fixes	Add it to the obot Roadmap project at Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#261	Requirement: the highest-authority file the agents read has no owner, no history and no review path	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#263	Requirement: config items are short local artifacts he can decide from, not a field form	Add it to the obot Roadmap project at Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#264	Requirement: a config item's claim is checked on a cadence, not asserted on the day it was filed	Add it to the obot Roadmap project at Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#265	Requirement: he answers a decision from the car, by voice, without a screen or an issue number	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#266	Requirement: a decision artifact notices when its own premise expires	Add it to the obot Roadmap project at Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#267	Requirement: the judge can see the constraints it is judging against	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#272	Requirement: branch protections, live before any scheduled session runs	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#274	Requirement: SafetyCensus stays and is rebuilt on metrics and reports — design first	Add it to the obot Roadmap project at Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#275	Requirement: what the fleet spends is measured before it is spent	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#278	Requirement: what comes next is written down — a ranked head, tiers below, before any clock runs	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#279	Requirement: a step-by-step IQ for the new laptop — the chance to fix rather than replicate	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#280	Requirement: an open decision artifact has an episode he can answer from a car	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#281	Requirement: safetyGraphics and safetyCharts back on CRAN — remove the Tendril chart	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#282	Requirement: the usage analytics run on a cadence, and the page says when it last did	Add it to the obot Roadmap project at Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#246	Requirement: what the machine may say about itself in public — session names and draft-release titles	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#251	Requirement: a kill this house reports is a kill it confirmed — the liveness anchor reports success while the session survives	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#252	Requirement: nobody can write to the board — the App is forbidden and the guard denies the only credential that works	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#256	Requirement: work that never reached GitHub is invisible to every check we run	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#257	Requirement: a thing he asked for has a delivery state, and something notices when it goes quiet	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#260	Requirement: git pushes and commits still go out as him — the lane no token fixes	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#261	Requirement: the highest-authority file the agents read has no owner, no history and no review path	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#263	Requirement: config items are short local artifacts he can decide from, not a field form	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#264	Requirement: a config item's claim is checked on a cadence, not asserted on the day it was filed	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#265	Requirement: he answers a decision from the car, by voice, without a screen or an issue number	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#266	Requirement: a decision artifact notices when its own premise expires	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#267	Requirement: the judge can see the constraints it is judging against	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#272	Requirement: branch protections, live before any scheduled session runs	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#274	Requirement: SafetyCensus stays and is rebuilt on metrics and reports — design first	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#275	Requirement: what the fleet spends is measured before it is spent	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#278	Requirement: what comes next is written down — a ranked head, tiers below, before any clock runs	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#279	Requirement: a step-by-step IQ for the new laptop — the chance to fix rather than replicate	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#280	Requirement: an open decision artifact has an episode he can answer from a car	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#281	Requirement: safetyGraphics and safetyCharts back on CRAN — remove the Tendril chart	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	obot.roadmap#282	Requirement: the usage analytics run on a cadence, and the page says when it last did	Add the provenance block naming the author, with EMPTY unless an approval resolves.
`high`	gsm.safety#41	Add Widget_AeExplorer htmlwidget consuming the safety.viz bundle	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	gsm.safety#42	Add Widget_QtExplorer htmlwidget consuming the safety.viz bundle	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	gsm.safety#43	Give the example pages site chrome and show the full workflow inline	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	gsm.safety#45	Add a 2_metrics phase: participant-level Hy's Law, QTcF and AE metrics	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#85	Add sandbox/triage-v2-smoke.md pipeline smoke marker	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#97	audit: accept 5 findings	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#102	audit: accept 28 findings	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#105	audit: accept 28 findings	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	safety.viz#120	nep-explorer (Phase 1): KDIGO creatinine scatter + stage summary	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#134	Stand up the 🧭🤖 obot-navigator session — launcher, skill, command, delivery file	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#136	The sweep measures roadmap discipline: work that shipped with no requirement above it, across all seven repos	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#138	The sessions tab becomes a roster of agents: id, status, cost and roadmap impact	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#143	Record when each local surface was last viewed, at the serve seam	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#147	The sessions tab is two dashboards stacked, and the roster is a flat wall of 28 rows	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#151	The wake channel: a worker that stops reaches the Navigator	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#154	Action 1: the Agents tab becomes a table with a filter sidebar, sharing the analytics pricing feed	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#155	Action 2: the Navigator tab becomes a metrics dashboard with a period selector and repo and goal filters	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#159	Every dashboard surface renders honestly on a machine with no history	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#166	The sibling briefing never tells a worker not to call EnterWorktree, and one stalled on it for 13 minutes	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#167	Build fleet: the sweep detects, a short-lived manager acts and exits	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#168	Agents tab: a created-date column, sorted newest first	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#169	Agents tab: pin agents, with the standing roles pinned by default	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#174	Every date on the Agents tab is a UTC day, so overnight work reads as yesterday	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#176	A working session was reported as waiting on an unresolved prompt, and the admiral closes sessions on that signal	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#177	The sibling briefing's opening HTML comment lands in the job status detail, carrying state with it	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#178	Agents tab: times on Created and Last active, in his local zone, and one day boundary	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#179	Agents tab: a task tag in the row, a summary on expand, and Roadmap impact demoted out of the table	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#181	A blocked admiral is invisible: it inherits the standing-session exclusion built for prime and nav	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#182	Rename fleet to admiral — the three standing roles are prime, admiral and nav	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#186	The checkout tracks main and consumers restart when it moves	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#206	The dashboard shows him zero of ten config items and calls it an empty list	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#210	A worker is told a requirement is not an approval, and given the command that says what is	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#215	A count stated about a source nobody read, and four more places the same mistake is waiting	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#225	A merged pull request counts as covered when it names an issue that is itself parented	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#236	AGENTS.md frames merging as approval-first, and policy.json says the opposite	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.roadmap#255	One authority for whether a decision has been made — and the ten that disagree	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#258	Watching the dashboard prevents it restarting, and a restart that cannot bind is reported as a restart	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`high`	obot.agent#264	A carve-out pull request routes itself to the config bucket, and the admiral stops re-escalating it	Set board Status to Released — the issue is closed. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#134	Requirement: demo-301 v0 — forkable demo study running the app (Safety + RBQM domains)	Write the Design section from the work as it actually stands.
`medium`	obot.roadmap#199	Requirement: the agent roster — every agent with its id, status, cost and roadmap impact	Write the Design section from the work as it actually stands.
`medium`	obot.roadmap#182	Requirement: remove the Experimental marking from the Time-to-Event Explorer after external clinical review	Link it under the goal it serves.
`medium`	obot.roadmap#226	Requirement: goal #73 says what it is now — a current body, five workstreams, and a bounded backlog	Link it under the goal it serves.
`medium`	obot.roadmap#227	Requirement: the dashboard's two views, literally — a session table with filters, and a filterable metrics dashboard	Link it under the goal it serves.
`medium`	obot.roadmap#229	Requirement: adversarial review of safetyCensus() — does it stay or go, before v1.1.0 publishes	Link it under the goal it serves.
`medium`	obot.roadmap#234	Requirement: one-off tasks — a small fix files against its goal, without a requirement to justify it	Link it under the goal it serves.
`medium`	obot.roadmap#236	Requirement: the admiral — a triggered manager, so finished work stops sitting and nobody has to remember to look	Link it under the goal it serves.
`medium`	obot.roadmap#238	Requirement: the morning fold, and the briefing it produces	Link it under the goal it serves.
`medium`	obot.roadmap#239	Requirement: the weekly briefing — the sink that keeps the daily at nine lines	Link it under the goal it serves.
`medium`	obot.roadmap#240	Requirement: the session skills the fold replaces — one retirement, five re-homings, and the notes that say so	Link it under the goal it serves.
`medium`	obot.roadmap#242	Requirement: does the briefing get read aloud — and at what cost to the words	Link it under the goal it serves.
`medium`	obot.roadmap#243	Requirement: merging is not deploying — the checkout tracks main, and consumers restart when it moves	Link it under the goal it serves.
`medium`	obot.roadmap#246	Requirement: what the machine may say about itself in public — session names and draft-release titles	Link it under the goal it serves.
`medium`	obot.roadmap#251	Requirement: a kill this house reports is a kill it confirmed — the liveness anchor reports success while the session survives	Link it under the goal it serves.
`medium`	obot.roadmap#252	Requirement: nobody can write to the board — the App is forbidden and the guard denies the only credential that works	Link it under the goal it serves.
`medium`	obot.roadmap#256	Requirement: work that never reached GitHub is invisible to every check we run	Link it under the goal it serves.
`medium`	obot.roadmap#257	Requirement: a thing he asked for has a delivery state, and something notices when it goes quiet	Link it under the goal it serves.
`medium`	obot.roadmap#260	Requirement: git pushes and commits still go out as him — the lane no token fixes	Link it under the goal it serves.
`medium`	obot.roadmap#261	Requirement: the highest-authority file the agents read has no owner, no history and no review path	Link it under the goal it serves.
`medium`	obot.roadmap#263	Requirement: config items are short local artifacts he can decide from, not a field form	Link it under the goal it serves.
`medium`	obot.roadmap#264	Requirement: a config item's claim is checked on a cadence, not asserted on the day it was filed	Link it under the goal it serves.
`medium`	obot.roadmap#265	Requirement: he answers a decision from the car, by voice, without a screen or an issue number	Link it under the goal it serves.
`medium`	obot.roadmap#266	Requirement: a decision artifact notices when its own premise expires	Link it under the goal it serves.
`medium`	obot.roadmap#267	Requirement: the judge can see the constraints it is judging against	Link it under the goal it serves.
`medium`	obot.roadmap#272	Requirement: branch protections, live before any scheduled session runs	Link it under the goal it serves.
`medium`	obot.roadmap#274	Requirement: SafetyCensus stays and is rebuilt on metrics and reports — design first	Link it under the goal it serves.
`medium`	obot.roadmap#275	Requirement: what the fleet spends is measured before it is spent	Link it under the goal it serves.
`medium`	obot.roadmap#278	Requirement: what comes next is written down — a ranked head, tiers below, before any clock runs	Link it under the goal it serves.
`medium`	obot.roadmap#279	Requirement: a step-by-step IQ for the new laptop — the chance to fix rather than replicate	Link it under the goal it serves.
`medium`	obot.roadmap#280	Requirement: an open decision artifact has an episode he can answer from a car	Link it under the goal it serves.
`medium`	obot.roadmap#281	Requirement: safetyGraphics and safetyCharts back on CRAN — remove the Tendril chart	Link it under the goal it serves.
`medium`	obot.roadmap#282	Requirement: the usage analytics run on a cadence, and the page says when it last did	Link it under the goal it serves.
`medium`	obot.roadmap#43	Requirement: abnormal-baseline DILI tools — migration Sankey + ALT waterfall (Amirzadegan 2025)	Close it as completed and set the board to Released — every task under it is closed and it is already in Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#58	Requirement: ideas-triage v2 — stronger model, richer context, bias-to-promote	Move it to Review — all its tasks are closed but the board still says Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#122	Requirement: scheduled autonomous sessions — the A2 promotion (recurring goal-work loop)	Move it to Review — all its tasks are closed but the board still says Requirement Gathering. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#123	Requirement: release scaffolding — news record, draft notes, semver milestones, RC PR framework, and the merge gate	Move it to Review — all its tasks are closed but the board still says Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#129	Requirement: open.csr submission outputs — RTF tables/listings, a values store, and seamless Reader editing	Close it as completed and set the board to Released — every task under it is closed and it is already in Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#161	Requirement: Kaplan–Meier time-to-event chart family — interactive renderer for safety.viz	Close it as completed and set the board to Released — every task under it is closed and it is already in Review. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#199	Requirement: the agent roster — every agent with its id, status, cost and roadmap impact	Move it to Review — all its tasks are closed but the board still says Development. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#205	Requirement: a real "since you last looked" — record page views locally, or say plainly that we cannot	Move it to Review — all its tasks are closed but the board still says Development. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#206	Requirement: the priced usage artifact refreshes on a cadence, or every surface says how old it is	Move it to Review — all its tasks are closed but the board still says Development. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#218	Requirement: the dashboard reads like a news feed, not an audit log — rebuild the sessions and Navigator pages	Move it to Review — all its tasks are closed but the board still says Development. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#220	Requirement: his queue holds exactly three buckets — RC, decision, config — and the remainder is ours	Move it to Review — all its tasks are closed but the board still says Requirement Gathering. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#223	Requirement: every surface renders honestly on a machine with no history — before the move, not after	Move it to Review — all its tasks are closed but the board still says Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#227	Requirement: the dashboard's two views, literally — a session table with filters, and a filterable metrics dashboard	Move it to Review — all its tasks are closed but the board still says Development. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#236	Requirement: the admiral — a triggered manager, so finished work stops sitting and nobody has to remember to look	Move it to Review — all its tasks are closed but the board still says Development. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#243	Requirement: merging is not deploying — the checkout tracks main, and consumers restart when it moves	Move it to Review — all its tasks are closed but the board still says Backlog. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#139	Worker ids never reach the worker: OBOT_WORKER_ID is invisible to tool shells, and the briefing placeholders arrive unfilled	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#141	The discipline number reports history as though it were drift: split compliance-since-the-rule from the historical stock	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#157	The wake list can only grow: dead and permanently-stuck workers never resolve	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#197	Every structural roadmap edit is attributed to @jwildfire — he made none of them	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#207	The attribution guard trusts GH_TOKEN=$(...) and a failed mint writes as him anyway	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#209	A merge that cites a decision does not check that the decision exists	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#228	The milestone gate reads a worked example as a closing declaration and refuses the merge	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.roadmap#230	Run the adversarial review of safetyCensus() and publish the decision artifact	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#238	The briefing has no route for a non-fast-forward push, and leads with the spelling that fails inside a repo	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)
`medium`	obot.agent#261	The Navigator measures process state badly, and published three wrong claims in one night	Set board Status to Backlog, inferred from the absence of any in-flight signal. — cannot run: no credential can write to the obot Roadmap board — the obotclaw App is FORBIDDEN on a user-owned project, and the attribution guard denies @jwildfire's own token (#252)

Activity 92 — every decision, newest first

From decisions.json, the same ledger the audit reads to mute rejected findings. A rejection is recorded but changes nothing on GitHub. This fold is regenerated each deploy, so a decision made a minute ago appears here a minute or two later — the run panel above the table is what reports it live.

2026-07-27 21:52 EDT accept 16 2 failed 8 stale 6 applied by @jwildfire

failed obot.roadmap#131 — Open requirement under no goal handed to the bounded agent
stale GOALLESS-REQUIREMENT:jwildfire/obot.roadmap#130 — GOALLESS-REQUIREMENT the current audit no longer reports this finding — nothing was changed
stale GOALLESS-REQUIREMENT:jwildfire/obot.roadmap#129 — GOALLESS-REQUIREMENT the current audit no longer reports this finding — nothing was changed
stale GOALLESS-REQUIREMENT:jwildfire/obot.roadmap#128 — GOALLESS-REQUIREMENT the current audit no longer reports this finding — nothing was changed
stale GOALLESS-REQUIREMENT:jwildfire/obot.roadmap#127 — GOALLESS-REQUIREMENT the current audit no longer reports this finding — nothing was changed
stale GOALLESS-REQUIREMENT:jwildfire/obot.roadmap#123 — GOALLESS-REQUIREMENT the current audit no longer reports this finding — nothing was changed
failed obot.roadmap#122 — Open requirement under no goal handed to the bounded agent
stale GOALLESS-REQUIREMENT:jwildfire/obot.roadmap#119 — GOALLESS-REQUIREMENT the current audit no longer reports this finding — nothing was changed
stale GOALLESS-REQUIREMENT:jwildfire/obot.roadmap#117 — GOALLESS-REQUIREMENT the current audit no longer reports this finding — nothing was changed
stale GOALLESS-REQUIREMENT:jwildfire/obot.roadmap#98 — GOALLESS-REQUIREMENT the current audit no longer reports this finding — nothing was changed
applied obot.roadmap#131 — Tracked issue with no assignee assigned @jwildfire
applied open.csr#25 — Board item with no Status board Status set to Backlog
applied open.csr#24 — Board item with no Status board Status set to Backlog
applied open.csr#23 — Board item with no Status board Status set to Backlog
applied open.csr#22 — Board item with no Status board Status set to Backlog
applied open.csr#15 — Board item with no Status board Status set to Released

2026-07-27 21:27 EDT accept 10 10 applied by @jwildfire

2026-07-27 21:26 EDT accept 1 1 applied by @jwildfire

applied obot.roadmap#130 — Tracked issue with no assignee assigned @jwildfire

2026-07-27 21:24 EDT accept 9 9 applied by @jwildfire

applied obot.roadmap#109 — Closed issue still parked in an active stage board Status set to Released
applied obot.roadmap#77 — Closed issue still parked in an active stage board Status set to Released
applied obot.roadmap#75 — Closed issue still parked in an active stage board Status set to Released
applied obot.roadmap#64 — Closed issue still parked in an active stage board Status set to Released
applied safety.viz#48 — Closed issue still parked in an active stage board Status set to Released
applied safety.viz#47 — Closed issue still parked in an active stage board Status set to Released
applied safety.viz#46 — Closed issue still parked in an active stage board Status set to Released
applied obot.roadmap#45 — Closed issue still parked in an active stage board Status set to Released
applied safety.viz#45 — Closed issue still parked in an active stage board Status set to Released

2026-07-27 21:21 EDT accept 6 6 applied by @jwildfire

applied obot.roadmap#128 — Requirement issue missing from the board added to the board at Backlog
applied obot.roadmap#123 — Requirement issue missing from the board added to the board at Backlog
applied obot.roadmap#119 — Requirement issue missing from the board added to the board at Backlog
applied obot.roadmap#117 — Requirement issue missing from the board added to the board at Backlog
applied obot.roadmap#115 — Requirement issue missing from the board added to the board at Released
applied obot.roadmap#98 — Requirement issue missing from the board added to the board at Backlog

2026-07-27 21:20 EDT accept 1 1 applied by @jwildfire

applied safety.viz#50 — Closed issue still parked in an active stage board Status set to Released

2026-07-27 21:19 EDT accept 9 9 applied by @jwildfire

applied obot.roadmap#119 — Tracked issue with no assignee assigned @jwildfire
applied obot.roadmap#88 — Tracked issue with no assignee assigned @jwildfire
applied obot.roadmap#35 — Tracked issue with no assignee assigned @jwildfire
applied obot.roadmap#31 — Tracked issue with no assignee assigned @jwildfire
applied obot.roadmap#29 — Tracked issue with no assignee assigned @jwildfire
applied obot.roadmap#25 — Tracked issue with no assignee assigned @jwildfire
applied obot.roadmap#24 — Tracked issue with no assignee assigned @jwildfire
applied obot.roadmap#10 — Tracked issue with no assignee assigned @jwildfire
applied obot.roadmap#9 — Tracked issue with no assignee assigned @jwildfire

2026-07-24 23:55 EDT accept 2 2 stale #106 by @jwildfire

stale OFF-BOARD-REQUIREMENT:jwildfire/obot.roadmap#91 — OFF-BOARD-REQUIREMENT the current audit no longer reports this finding — nothing was changed
stale OFF-BOARD-REQUIREMENT:jwildfire/obot.roadmap#69 — OFF-BOARD-REQUIREMENT the current audit no longer reports this finding — nothing was changed

2026-07-24 23:50 EDT accept 2 2 applied #103 by @jwildfire

applied OFF-BOARD-REQUIREMENT:jwildfire/obot.roadmap#91 — OFF-BOARD-REQUIREMENT added to the board at Backlog
applied OFF-BOARD-REQUIREMENT:jwildfire/obot.roadmap#69 — OFF-BOARD-REQUIREMENT added to the board at Backlog

2026-07-24 23:49 EDT accept 28 28 applied #102 by @jwildfire

applied UNSTAGED-BOARD-ITEM:jwildfire/obot.roadmap#70 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#55 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#54 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#51 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#50 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#49 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#48 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#47 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#46 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#45 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#44 — UNSTAGED-BOARD-ITEM board Status set to Backlog
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#93 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#92 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#91 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#76 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#68 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#63 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/safety.viz#60 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#40 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/obot.agent#39 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#38 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#37 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#36 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#35 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#34 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#33 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#32 — UNSTAGED-BOARD-ITEM board Status set to Released
applied UNSTAGED-BOARD-ITEM:jwildfire/gsm.safety#31 — UNSTAGED-BOARD-ITEM board Status set to Released

2026-07-24 23:42 EDT accept 5 5 applied #100 by @jwildfire

applied CLOSED-NOT-RELEASED:jwildfire/safety.viz#98 — CLOSED-NOT-RELEASED board Status set to Released
applied CLOSED-NOT-RELEASED:jwildfire/gsm.safety#30 — CLOSED-NOT-RELEASED board Status set to Released
applied CLOSED-NOT-RELEASED:jwildfire/gsm.safety#29 — CLOSED-NOT-RELEASED board Status set to Released
applied CLOSED-NOT-RELEASED:jwildfire/gsm.safety#28 — CLOSED-NOT-RELEASED board Status set to Released
applied CLOSED-NOT-RELEASED:jwildfire/gsm.safety#27 — CLOSED-NOT-RELEASED board Status set to Released

2026-07-24 22:51 EDT reject 1 1 rejected by @session

rejected HARD-WRAPPED-BODY:jwildfire/obot.roadmap#22 — HARD-WRAPPED-BODY Rewrap the body to one line per paragraph, changing no wording.

2026-07-24 22:51 EDT accept 1 1 applied by @session

applied CLOSED-NOT-RELEASED:jwildfire/obot.roadmap#46 — CLOSED-NOT-RELEASED board Status set to Released

2026-07-24 22:51 EDT accept 1 1 applied by @session

applied ASSIGNEE-MISSING:jwildfire/obot.roadmap#2 — ASSIGNEE-MISSING assigned @jwildfire

Rules 24 — 9 firing, 15 quiet

Every convention the audit knows about, and how it fared on the last run. Adding a rule is one object in rules.mjs.

Rule	Group	State	What it checks, and why
`CLOSED-NOT-RELEASED`	Board integrity	11 firing	Closed issue still parked in an active stage The board Status is what the roadmap page and the `--auto` lane read as the stage of record. A closed issue sitting in Development makes the lane look busier than it is and hides what actually shipped — the exact drift the 2026-07-11 usage audit caught. Fix: Set the board Status to Released.
`OPEN-IN-RELEASED`	Board integrity	quiet	Open issue the board calls Released Released is a terminal stage, and under @jwildfire's one-requirement-one-release rule (2026-08-15) nothing is ever open in it on purpose. An open issue at Released is one of exactly three defects: finished work nobody closed, live work filed in the wrong lane, or a requirement whose scope spans more than one release. There is deliberately no label, marker or comment that silences this rule — an escape hatch would restore the ambiguity the rule exists to remove. Fix: Close it if the work is done; move the stage back if the work is live; split it if it carries scope beyond the release it delivered.
`UNSTAGED-BOARD-ITEM`	Board integrity	48 firing	Board item with no Status An item with no Status is on the board but outside the lifecycle: it appears in no stage lane, the roadmap page has to call it "Unstaged", and the `--auto` selector cannot reason about it. Fix: Set the Status the evidence supports — Released if it is closed, otherwise the stage its PRs and design artifacts imply.
`OFF-BOARD-REQUIREMENT`	Board integrity	30 firing	Hub issue missing from the board The obot Roadmap project is the stage tracker for hub work. An issue that never got added is invisible to the stage lanes, to the roadmap page's stage grouping, and to any review that starts from the board — which is how a burst of promoted ideas can vanish the day after it is filed. The population deliberately does not depend on the `requirement` label: #189–#193 were filed with `infrastructure` and `ai`, sat off the board, and a label-gated rule could not have named them even on a fresh run (#201). Fix: Add it to the project and give it a Status.
`BOARD-DUPLICATE`	Board integrity	quiet	Same issue on the board twice Duplicate items double-count a requirement in every stage tally and let two copies hold different Statuses, so the board contradicts itself. One appeared during the #53 goal migration and had to be removed by hand. Fix: Remove the extra items, keeping the one that carries a Status.
`CLOSED-PARENT-OPEN-SUBS`	Hierarchy	quiet	Closed parent with open sub-issues Sub-issues are the canonical task tracker for a requirement, so a closed parent asserts its children are finished. When they are not, the remaining work is orphaned — visible on no requirement, in no stage, and to nobody. (@jwildfire named this one as the founding example of the audit.) Fix: Close the children that are actually done; move genuine follow-on scope to a follow-up requirement — the #30 → #88 precedent — or reopen the parent.
`SUBS-DONE-PARENT-OPEN`	Hierarchy	15 firing	All sub-issues closed, parent still open When every task under a requirement is closed the requirement is done being built; leaving it open in an earlier stage means the board understates progress and the review queue never surfaces it. Fix: Move it to Review, or close it if it has already sat in Review.
`GOALLESS-REQUIREMENT`	Hierarchy	31 firing	Open requirement under no goal Since #53 goals are hub issues and membership is the sub-issue link — nothing else. Membership is inherited, so a requirement nested under another requirement still belongs to that requirement’s goal; only an issue with no goal anywhere up its parent chain belongs to no standing direction, never appears on a goal page, and can never be picked up by an autonomous session selecting by goal. Fix: Link it under the goal it serves, or state why it is deliberately standalone.
`UNTRACKED-TASK`	Hierarchy	quiet	Hub issue in no structure at all The hub has exactly three ways an issue is visible: the `requirement` label puts it on the roadmap page, a sub-issue link puts it on a goal page, and a board item puts it in a stage lane. An issue with none of the three is filed and then invisible — it will be found again only by accident. Fix: Link it under the goal or requirement it belongs to, or promote it to a requirement.
`GOAL-NO-MEMBERS`	Hierarchy	quiet	Goal with no member requirements A goal exists to group work and to give an autonomous session something to select from. With no sub-issues it is a statement of intent the machinery cannot act on. Fix: Link the requirements that serve it, or retire the goal.
`GOAL-BOARD-INCONSISTENT`	Hierarchy	quiet	Goals inconsistently placed on the board Goals are permanent and do not move through the requirement stages, so a goal on the delivery board is an item with no stage it can ever reach. @jwildfire settled the convention on 2026-08-15 (audit decision R3-a): goals are not board items. They are surfaced by the goal pages and the hierarchy view, which are the better surfaces for something that never finishes. Fix: Take the goal off the board. Nothing is deleted — the goal issue and its sub-issue links are untouched.
`MERGED-PR-OPEN-TARGET`	Linkage	quiet	Merged PR whose closing target is still open GitHub only auto-closes an issue when the PR is in the same repository. Cross-repo `Closes` lines — the norm here, where implementation PRs live in spoke repos and requirements live in the hub — merge silently without closing anything. Fix: Close the referenced issue.
`OPEN-PR-CLOSED-TARGET`	Linkage	quiet	Open PR against an already-closed issue Either the branch is stale work that should be dropped, or the issue was closed while its implementation was still in review. Both are worth knowing; neither resolves itself. Fix: Close the PR, or reopen the issue.
`PR-NO-REQUIREMENT`	Linkage	quiet	Open PR with no requirement link The Issue–PR Link Convention exists so a merge closes its requirement and the roadmap page can show which requirement a PR is moving. An unlinked PR is invisible to both. Fix: Add the closing reference to the requirement or task it implements.
`REQUIREMENT-LABEL-MISSING`	Conventions	quiet	Requirement-titled issue without the `requirement` label Every generator selects requirements by label. An issue titled "Requirement: …" without the label is absent from the roadmap page, the stage tallies and the goal pages — present on GitHub, missing from the project. Fix: Add the `requirement` label.
`ASSIGNEE-MISSING`	Conventions	39 firing	Tracked issue with no assignee The Assignee Convention puts @jwildfire on every issue the agent files, so his GitHub views ("assigned to me") are the same working set the roadmap shows. Unassigned issues fall out of that view. Fix: Assign @jwildfire.
`MILESTONE-MISSING`	Conventions	quiet	Open requirement with no milestone Milestones are the delivery slot (`backlog`, `2026q3`, `2026q4`) and drive the release-facing views. A requirement with none is unscheduled by omission rather than by decision. Fix: Set `backlog` for anything not yet scheduled; pick the quarter for work in flight.
`DESIGN-MISSING`	Conventions	2 firing	Requirement past Design with no design The lifecycle puts Design before Development for a reason: sub-issues are supposed to be decomposed from it. A requirement in Development whose Design section is empty or "TBD" means the decomposition was improvised, and there is nothing for a reviewer or an autonomous session to work from. Fix: Populate the Design section, or add a design doc under requirements/design/.
`APPROVAL-UNRESOLVED`	Conventions	quiet	Requirement claims an approval that does not resolve A requirement written by an agent must not be able to authorise what only @jwildfire can authorise (#215). `Approved by` therefore holds a citation that resolves — a decision id whose artifact records his words, or a native review — and never prose. An unresolvable citation is the exact failure this convention exists to stop: something claims his approval and cannot show it, and the next agent to read it will act on it. On 2026-08-16 one did, and prepared to delete files on the strength of a requirement its own supervisor had written. Fix: Resolve it or remove it: `node scripts/provenance.mjs resolve <citation>` says why it fails. If he has not decided, the honest value is `EMPTY` — nothing is blocked by writing it.
`PROVENANCE-MISSING`	Conventions	20 firing	Requirement filed without saying who wrote it or who approved it Every requirement filed since 2026-08-18 carries a provenance block: who authored it, and who approved it or `EMPTY` (#215). The empty value is the point — a missing field reads as an oversight and invites the next reader to assume, and an explicit "nobody has approved this" reads as a fact and invites them to check. Requirements filed before that date are out of scope here and counted instead in reports/requirement-provenance/, because rewriting 75 existing bodies to say something different about his own review is not a change an agent makes unattended. Fix: Add the block at the foot of the body: `node scripts/provenance.mjs stamp <number>` prints it.
`AUTO-DRAFT-CONFLICT`	Conventions	quiet	Issue labelled both `auto` and `draft` The two labels are opposites: `auto` means the #18 implementation-ready criteria are met and an autonomous session may take it; `draft` means it needs @jwildfire's steering first. Carrying both means the `--auto` selector may pick up work that was explicitly gated. Fix: Keep whichever the issue actually satisfies and drop the other.
`HARD-WRAPPED-BODY`	Conventions	1 firing	Issue body hard-wrapped mid-paragraph GitHub renders a single newline as a line break, so a body wrapped at 80 columns arrives as ragged half-lines. @jwildfire's standing instruction is one line per paragraph or bullet in anything posted to GitHub. Fix: Rewrap the body to one line per paragraph.
`PROMOTED-IDEA-OPEN`	Conventions	quiet	Promoted idea thread still open Triage closes a thread as resolved when it becomes an issue; that closure is what keeps the Ideas board an inbox rather than an archive. A promoted thread left open keeps showing up as un-triaged work. Fix: Close the discussion as resolved.
`STALLED-IN-FLIGHT`	Conventions	quiet	In-flight requirement that stopped moving Development and Review are lanes for work happening now. A requirement that has not been touched in two weeks, with no open PR behind it, is parked — and while it sits in an active lane it crowds out the real front line on every view of the roadmap. Fix: Park it back at Backlog. Dragging it forward on the board is how you say it is live again.

How a decision travels 4 steps

Every finding here is a fact about GitHub state, produced by a deterministic rule rather than a model: the same state yields the same findings.

This deployed page is read-only — it holds no token and has no write path. Deciding happens on the local session hub's copy of this queue, where ✓/✗ hand finding ids to a local Claude Code agent; filing a decision issue naming the ids remains the fallback lane.
The lane runs a fresh audit and re-derives what that id means. A finding the new audit no longer reports is refused as stale, and one whose source could not be read is reported blocked. What runs is never what this page said should run.
A mechanical fix is applied as the operations listed in the rail; a judgment call goes to a bounded agent with the prompt shown there.
✗ changes nothing and mutes the finding for 60 days, or until its evidence changes. Both land in the Activity fold above.