# DISMISSED — RDR-1 — a reopen condition filed in `queue/dismissed/` has no reader on its date; considered as a governance row and REJECTED on buildability and slot cost status: dismissed at adversarial review, panel run 26 (2026-09-18) · class considered: registration hygiene (G5) / the queue's own instrument · **every mechanism claim below was verified twice — by the queue lens and independently by the adversarial reviewer — and none is disputed. The row is killed because the fix is an OWNER PROSE EDIT that no implementer may make, and spending a queue slot on it at 13/12 would evict buildable work to hold a two-sentence change.** --- ## What was considered `ops/RESEARCH_PANEL.md` "What matters here" #2 states the design plainly: > "A dismissal must carry its resurrection condition. Write 'killed because X; > reopens if Y' — that turns `queue/dismissed/` from a blocklist into a set of > standing tripwires future panels EVALUATE (did Y become true?) instead of > merely skipping. A dismissal without a reopen condition is rot." All 28 files in `queue/dismissed/` carry a reopen condition. **Zero rot by the procedure's own definition.** The defect is one level up: *nothing reads them on their date.* ## The mechanism claims — verified, recorded so nobody re-derives them Checked with `grep -rni "reopen" ops/` and `grep -rn "dismissed" ops/`. Every hit is **write-side** (the panel writes dismissals with conditions; triage may `git mv` open→dismissed with conditions) or **prior-art read** ("never re-litigate"). Not one instructs a routine to EVALUATE a condition: 1. `ops/QUEUE_TRIAGE.md` §1 "Sweep" opens *"For every item in `research/queue/open/`"*. Its "Also check" list adds `approved/`, `built/` and stalled PRs — **`dismissed/` is absent.** 2. `ops/prompts/triage.md:34` (the live prompt): *"Sweep every file in `queue/open/` for EXPIRY"* — open/ only. 3. `ops/RESEARCH_PANEL.md` §1 sends the panel to `dismissed/` **for prior art**. The "evaluate the tripwires" sentence lives only in the non-operative "What matters here" preamble; no step executes it. 4. `ops/RESEARCH_AUDIT.md` M4 samples `dismissed/` for the *opposite* question (does a recent `open/` item restate a dead idea?). 5. The panel's own expiry-watch prompt names `open/` and `approved/` only — **the defect reproducing itself inside the instrument built to catch it.** Today's `dismissed/` sweep happened only because the panel's lead added it to the lens brief by hand. ## The harm is measured, not hypothetical - **LCK-1** — its event-conditioned reopen fired ~2026-09-11 and survived **queue triage 09-14 and panel runs 21, 22 and 23** before run 24 caught it by hand on 09-16. - **ERN-1** — a provisional kill invisible for 30 days because it sat in the frozen pre-migration archive. - **The pending one, and the reason this file exists: CLK-1's reopen is dated 2026-10-06 and BOTH of its legs are ALREADY TRUE at today's HEAD.** It guards the only two forward clocks maturing before the December gate — **shortability 2026-10-19** and **options_iv_term 2026-10-26** — neither of which has a pinned evaluator, and neither of which appears in NORTHSTAR §6 at all, against §6's own header rule that *"every entry must have a pinned evaluator before maturity."* Both dates were re-derived this run from the committed capture files (37 shortability files from 2026-07-26, two known holes; 33 `options_iv_term` files from 2026-08-03, no holes) and reproduce queue triage's 09-14 arithmetic exactly. Three independent records of this same gap — CLK-1's dismissal (08-31), triage's Decide-3 item 2 (09-14), LCK-1's panel annotation (09-16) — and it has never been a row. ## Why it was killed anyway 1. **It is not implementer-buildable.** The fix is one sentence in `ops/QUEUE_TRIAGE.md` §1 plus its mirror in `ops/prompts/triage.md` — routine self-modification, in a path the auto-merge guard exists to protect, and the mirror must move in the same sitting or the repo merely *looks* correct. A queue row's function is to reach `approved/` and be built; this one could sit in `approved/` forever with nothing legitimate to pick it up. 2. **The slot cost is real and lands on someone else.** `queue/open/` stands at **13 against its pre-registered 12-item cap** (`ops/QUEUE_TRIAGE.md:86-91`); Monday's triage must already evict one incumbent mechanically. A 14th row would evict a second — converting a two-sentence owner edit into the eviction of real work. That is exactly the trade the cap was written to force, and this row loses it. 3. **The precedent is this shop's own.** ERN-1 was migrated into `dismissed/` with a dated default precisely because it "costs no open slot, no registry row." The escalation, not the slot, is the right instrument here. 4. **The parser leg is rejected outright** (~0.4 pd): a machine-checkable sweep buys a second detector that can itself fail quiet — the exact failure class this finding is about. 28 files is a `grep`. ## Handed over instead — the owner ask, in full Two sentences, ~0.1 pd, and **it must move in one sitting or not at all**, because a prose edit whose prompt mirror lags is how two routine prompts in this shop rotted invisibly: > Add to `ops/QUEUE_TRIAGE.md` §1 and to `ops/prompts/triage.md`'s sweep step: > *"Also sweep `research/queue/dismissed/` for reopen conditions dated within > the next 14 days or whose triggering event has already occurred; report each > one, and reopen only what the owner approves."* **And the harder consequence the owner can discharge in two lines regardless of the procedural fix:** add the shortability (2026-10-19) and `options_iv_term` (2026-10-26) clocks to NORTHSTAR §6 with their evaluators. §6 is a declared living section, so this crosses no C0 boundary, and it closes the concrete October exposure whether or not the sweep sentence is ever written. ## Reopens if - **(a)** CLK-1's two clocks — shortability (~2026-10-19) and `options_iv_term` (~2026-10-26) — still lack **both** a pinned evaluator **and** a NORTHSTAR §6 row **on or after 2026-10-06**. That is the escalation route failing a third time with the first clock binding in under two weeks; or - **(b)** a **third** dismissed reopen condition is found to have fired unevaluated (LCK-1 is one, ERN-1 is two) — reopen immediately, at which point the pattern is the finding and not the instance. ## Dies permanently This file is never reopened if any line in `ops/QUEUE_TRIAGE.md`, `ops/prompts/triage.md`, `ops/RESEARCH_PANEL.md` or `ops/prompts/panel.md` instructs a routine to **evaluate** (as opposed to write into, move into, or read for prior art) the reopen conditions in `research/queue/dismissed/`. Verified absent 2026-09-18; every hit in `ops/` is write-side or prior-art.