DISMISSED — CLK-1 — two dated criteria mature with no evaluator, and neither is on the NORTHSTAR §6 calendar

status: dismissed by TRIAGE 2026-08-31 · OVERFLOW — lowest-ranked at the pre-registered 12-item cap · raised panel run 1 (2026-08-06) · body verbatim below

Resolution — mechanical overflow, and the panel's own judgement was "no"

research/queue/open/ held 15 files after this run's sweep against the pre-registered 12-item cap (ops/QUEUE_TRIAGE.md:86-90), so the three lowest-ranked are dismissed with reopen conditions. This is one of them.

It ranks last on the queue's own terms: the panel that raised it recorded judgement: no and wrote "Not a standalone item — this is the precondition to charter §7 rot-item 5's already-planned cycle 3." A to-do list for an already-planned cycle is a note, not a decision the owner can make this week.

Its content is NOT overtaken and is re-verified live at HEAD 528793d — that is why the reopen condition below is dated rather than conditional:

• NORTHSTAR.md:192-202 (§6) still contains neither clock.
• options_iv_term vacuity kill — CAPTURES.md pins "at 60 trading days, cross-name median < 5 expiries/name → VACUOUS, stream RETIRED". Stream since 2026-08-03 → matures ~2026-10-28. No evaluator: captures.py still carries the explicit disclaimer that its daily median against a breakage bar of 2 is not the pre-registered criterion.
• shortability minimum accrual — CAPTURES.md pins 60 td plus the selection-change hypothesis, measured before any return is looked at. Since 2026-07-26 → matures ~2026-10-20. Still zero consumers of the borrow flags outside the capture/QA path.

Both dates are carried into the 2026-08-31 triage report so they survive this dismissal in the outbox archive as well as in git.

Reopen condition. Reopen on or before 2026-10-06 (two weeks before the first clock binds) if either evaluator is still absent OR §6 still lacks both rows. Reopen immediately if charter §7 cycle 3 is scheduled, since this is its starting list. A dismissed item is not swept by the weekly triage — so the owner-side action that makes this dismissal safe is adding the two rows to §6 (a living section) now, which costs two lines and needs no build.

Body as filed (verbatim, untouched)

CLK-1 — two dated criteria mature with no evaluator in the repo, and neither is on the NORTHSTAR §6 calendar

status: open · raised panel run 1 (2026-08-06) · migrated 2026-08-24 (body verbatim below) · class: deadline-driven registration (P1 precondition) · judgement: no · effort 0.5 pd · horizon: clocks bind 2026-10-20 / 2026-10-28

6. CLK-1 (downgraded) — two dated criteria mature in ~10 weeks with no evaluator in the repo, and neither is on the §6 calendar. · judgement: no · effort 0.5 pd · horizon: clocks bind 2026-10-20 / 2026-10-28

Not a standalone item — this is the precondition to charter §7 rot-item 5's already-planned cycle 3 (wire the §6 deadline ledger into AUDIT.md/the digest). Recorded so cycle 3 starts from a known list.

• options_iv_term vacuity kill — CAPTURES.md pins "at 60 trading days (~late 2026-10), cross-name median < 5 expiries/name → VACUOUS, stream RETIRED". Stream Since: 2026-08-03 → matures ~2026-10-28. No evaluator exists: capture_qa checks a daily median against a breakage bar of 2 (captures.py:481-488), explicitly commented as not the pinned criterion.
• shortability minimum accrual — CAPTURES.md pins 60 td plus the hypothesis "excluding HTB names from the momentum top-50 changes selection ≥1 name/month", measured BEFORE any return is looked at. Since 2026-07-26 → matures ~2026-10-20. Zero consumers of the borrow flags exist outside the capture/QA path.

Adding rows to §6 changes no pinned criterion — §6 is a declared living section, so this is not a C0 boundary.

Kill criterion — bidirectional, or it is vacuous. The cycle-3 ledger check must red if any §6 row lacks a named evaluator or if any dated criterion in CAPTURES.md / a hash-frozen memo is absent from §6. Only the second direction catches missing rows; a one-way check would have passed today. If the check cannot be written without hand-maintaining a second list (i.e. it only restates §6), abandon the tooling and keep §6 as a doc with a weekly-audit review step.

Panel run 35 append — 2026-10-06: THE REOPEN CONDITION FIRED, ON ITS OWN DATE

This file's reopen condition is dated 2026-10-06 — today — and both of its legs are TRUE at HEAD cd0ed7a. Verified independently by two lenses of this run and by the adversarial reviewer:

• §6 still lacks both rows. grep -n "shortability\|iv_term" NORTHSTAR.md returns nothing inside §6 (the table is NORTHSTAR.md:192-202). Neither capture clock is on the appointment book.
• Neither evaluator exists. src/thales/data/captures.py:694 still carries the comment "breakage bar, not the pre-registered <5-median kill criterion", so the only options_iv_term check is a latest-day breakage bar of 2, not the pinned cross-name <5 criterion at 60 td. For shortability, nothing computes the pinned selection-change hypothesis: the only references to the borrow flags outside the writer/QA path are a docstring at src/thales/cli.py:2176-2177. Zero consumers.

Dates re-derived with the real NYSE calendar (pandas_market_calendars), and this file's own figure is corrected:

dismissed/rdr-1…:56-59 and research/2026-09-29_panel_run_30.md already use 10-26; this file was never corrected. Nothing has yet scheduled a read off 10-28, so the error has cost nothing — but it is the file whose reopen fires.

Both clocks also carry an elapsed-vs-accrued split, same shape as BTB-1's. shortability: 41 files but day zero 2026-07-26 is a Saturday, so 40 session-dated captures against 50 elapsed sessions — 10 missing (08-07, 08-28, and the 09-21→09-30 billing outage) → accrual-60 ≈ 2026-11-02. options_iv_term: 37 files against 45 elapsed sessions (08-03→10-05), 8 missing → accrual-60 ≈ 2026-11-06. Neither pin says which reading governs, and choosing after seeing a result is the gate-shopping hazard BTB-1 already raised for its own stream. The same ruling settles all three.

What this append is, and is not. It is the expiry watch doing its one job: recording that a dated tripwire fired, with its measurement, where ls and grep will find it. Reopening is the owner's move — dismissed/→open/ is not a sanctioned routine move (ops/QUEUE_TRIAGE.md:118-122), and the established precedent for a fired condition is a dated append, not a mint (dismissed/b4-notch-skew-row-floor.md:94, bcn-1:74, lck-1:86, rdr-1:128). No row is minted here: rdr-1:128 pre-registered that at the third such firing "the pattern is the finding and not the instance", and a row for this was already self-killed once as a C0 breach.

This is the fourth independent record of the same gap (this file 08-31, triage decide-3 09-14, LCK-1 09-16, RDR-1 09-18) and the first on a date where the nearest clock is 13 days out. The remedy this file names has not moved and still costs two lines in a declared living section: add a shortability row and an options_iv_term row to NORTHSTAR §6, each naming its evaluator or naming that it has none. NORTHSTAR.md is deny-listed to the auto-merge guard (scripts/automerge_guard.py:68), so no routine can do it.

One correction owed to a sibling routine, recorded here because it is the same fact: AUDIT.md:234 (weekly audit, 2026-10-05) says "every NORTHSTAR §6 entry keeps a pinned evaluator … the one near-term date WITHOUT an appointment-book row is the 10-19/20 Actions forecast". The first clause is true of the entries that ARE in §6; "the one" is not — shortability (10-19) and options_iv_term (10-26) have neither a row nor an evaluator, and 10-19 collides with the Actions forecast, which makes the mis-read likelier. The weekly audit corrects its own records; this is the panel telling it.