DISMISSED — TRP-1 — triage named 11 fired reopen conditions as the steward's move and the steward's next record named none of them; dismissed as the fifth variant of one theme, with the 11 slugs preserved here so the next reader has them on main
status: DISMISSED 2026-11-09, panel run 49 — killed by this run's own adversarial review · raised by the queue-and-clocks lens, which ranked it below its own other candidate and said it would not contest a kill · class: loudness / hand-off · effort would have been ~0.2 pd
What was measured, and it is all true
Triage's 2026-11-03 dismissed sweep opened all 48 files in
research/queue/dismissed/, re-evaluated every written reopen condition, and
named 11 as fired, handing them on with "dismissed → open is the
steward's move, never mine, so each is a named item with its evidence." The
steward ran two days later and research/steward/2026-11-05.md names none
of them: grep -ic returns 0 for each of shr-1, hire-1, gap-1, lck-1,
bcn-1, dsp-1, dsp-2, rcx-1, b4-notch, oad-1, scr-1 — and also for
swc-1 (triage's own decide item 3) and fos-2 (whose condition fired
mechanically when triage dismissed DGX-1). PR #319 annotated three open
rows and zero of the 11. The evidence lives only on outbox/triage's
message.md, which is not on main, reaches no routine, and is withheld from
email by weekly_digest_only.
Ages at the time of measuring: lck-1 53 days, gap-1 39, bcn-1
39, hire-1 22 (and recorded as "now permanently unresettable"),
dsp-1/dsp-2 21, rcx-1 leg (c) 13 — the last with its citation,
cost (~0.1 pd), tier (observability) and discharge criterion already written by
panel run 45.
Why it is dismissed
- It is the fifth variant of one theme, and the fourth was dismissed on
exactly this ground.
rdr-1,scr-1,swc-1,dlv-1andrlv-1are all record-site/loudness rows;swc-1's dismissal says "filing a fourth variant of the same theme would be the paddingNORTHSTAR.md§2 warns about." - The reader/actor distinction the row rests on is thinner than it looks.
ops/STEWARD.md§1d putsdismissed/reopen conditions in the steward's own weekly reading, and §4 authorises the reopen — "reopen a dismissed item only when its own written reopen condition has fired — cite it." So the steward's duty does not depend on triage's carrier at all. "The carrier is broken" is not what the evidence shows; "one run did not get to them" is. - One week is not a falsification. The steward runs weekly and had four PRs to merge in that window. The row's own kill criterion concedes the observation is a single run deep.
- The one genuinely new sub-finding is already owned. "The evidence lives
only on an unmerged/unread branch" is
dlv-1's subject and adjacent torlv-1. Andoutbox/triagepreserves history across 51 commits, so nothing is actually lost — only unread.
The payload, preserved — the 11 fired slugs, so this is not lost with the row
Carried here deliberately, because ops/RESEARCH_PANEL.md "What matters here"
#2 makes dismissed/ the set future panels evaluate, and because the
cheapest honest instrument for this finding is putting the names on main
rather than building a carrier:
shr-1 · hire-1 · gap-1 · lck-1 · bcn-1 · dsp-1 · dsp-2 ·
rcx-1 (leg c) · b4-notch · oad-1 (with trg-1) · scr-1
Two of these have moved since triage measured them, and a future reader should
not re-derive it: gap-1 is annotated today by this run (its condition
fired again on a new, still-recordable notch, filed as open/pit-2-…), and
scr-1's conditions were re-checked and remain cured-or-unfired. The
other nine are untouched.
Reopen conditions (either one)
- The 2026-11-12 steward record names fewer than all 11 — i.e. the
hand-off is not a one-run lag but a standing gap. The test is mechanical:
count how many of the list above are named and dispositioned (reopened /
declined with a reason / recorded as cured). If it is fewer than 11, the fix
is a durable carrier — triage's fired list appended to an auto-mergeable
record (
AUDIT.md's fire-once register, or a dated annotation per fired file, which triage already writes) — and that is a count change, not a new capability. Negative control for any such carrier: it must be able to render a non-empty disposition list; a carrier that prints "none" identically whether the steward read them or not is this defect repeating. - Any one of the 11 reaches 90 days fired with no disposition anywhere.
lck-1is the nearest at 53 days as of 2026-11-03, so this tripwire comes due around 2026-12-10 if nothing moves. A single condition dormant for a quarter is a different and stronger claim than a one-week lag.
Not reopened by: another weekly steward record that happens not to mention
them while disposing of other work, nor by the outbox/triage branch remaining
off main — that is dlv-1's and rlv-1's territory, not this row's.