# 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.