docs: tickets/ subdir + delete naming-deferral, ref-frame, coverage-audit

Two cleanup operations bundled (separate scopes, single commit
since they share the doc-tree settle):

1. Move ticket-NNNNNN-<slug>.md files into docs/tickets/. The
   directory makes browsing the design log easier; the index
   stays at docs/TICKETS.md (top-level pointer). Convention text
   in TICKETS.md updated to spell the new path.

2. Delete three docs whose load-bearing content has either been
   absorbed into the codebase or distilled into closed tickets:

   - docs/naming-deferral.md (147 lines) — explained why we
     don't rename claim_lattice → CTI/PROMETHEUS-Σ. Decision
     stays in place; the rationale is no longer worth a
     dedicated doc. Inline citations removed from
     cti-architecture.md (4 refs), warrant.py, ticket-000003
     (closed-ticket internal ref).
   - docs/reference-frame-failure-class.md (169 lines) — Orwell
     case journal that motivated the phrase-pattern retrieval
     route. The route shipped; the analysis is now duplicate
     with the closed Ticket #000002. Inline citation removed
     from CLAUDE.md retrieval pipeline section + frame.py.
   - docs/test-coverage-audit-2026-05-01.md (46 lines) —
     point-in-time audit checking 16/16 of fox's §11 list. Tests
     themselves live in tests/; the audit was a one-shot
     checkmark exercise.

References updated:
  CLAUDE.md, aborist/qa/frame.py, aborist/qa/retrieval_plan.py,
  aborist/qa/warrant.py, docs/cti-architecture.md, docs/TICKETS.md,
  docs/tickets/ticket-000003 + ticket-000004 (internal links).

Net: -362 lines + tickets/ subdir. 751/34 tests still pass.

2026-05-02 12:51:09 -04:00

3.3 KiB

Raw Blame History

Ticket #000004 — Directive coverage in bench summary

Status: closed · landed in commit acd1f9c (2026-05-01) Opened: 2026-05-01 Closed: 2026-05-01 Directive: D8 — Automate only after the invariants are test-pinned. Directive coverage in the bench output is the substrate that makes D1-D7 enforcement visible per-run. Scope: Wire the seven-point program into bench/qa_sweep.py so each row carries a directive_compliance dict and the markdown summary emits a per-mode coverage table. Audience: fox + future blackops shifts. Hard constraint: the bench output never edits the run-DAG, the audit chain, or the providence_cache. Directive compliance lives alongside the existing per-row signals (deflection, capacity, strict-rate); never feeds back into the proof path.

Why this ticket exists

The seven-point program is governance prose unless the bench enforces it per-run. Without per-row directive compliance, an operator can't tell whether a strict-rate climb came from real substrate work or from accidentally weakening one of the directives.

Per the five-step algorithm step 5 ("automate only after test- pinning"): the bench harness IS the automation substrate, so it must enforce the directives before any feature gets layered on top.

Implementation summary (landed `acd1f9c`)

bench/qa_sweep.py:

_directive_compliance(answer_mode, result, err) — pure helper computing per-row pass/fail for the directives whose pinning is observable from a single bench row (D2, D3, D4, D6, D7). D1, D5, D8 are global properties of the substrate; tracked once in the program doc rather than per-row.
Each _run_one result row gains a directive_compliance: dict field.
_summarize aggregates per-row booleans into per-mode directive_pass: dict[str, int] counts.
_render_markdown emits a ## directive coverage (seven-point program) section with a per-mode per-directive table showing count/N (pct%).

Per-row checks:

ID	Check
D2	`answer_mode in ("claim_lattice_pointer", "claim_lattice")`
D3	lattice mode + `run_dag_root` populated (full Module L pending #000002)
D4	`run_dag_root` populated (retrieval-plan hash pending #000001)
D6	warrant ran (lattice mode today; per-shape gating pending #000003)
D7	`audit_mode in {STRICT, HYBRID, UNGROUNDED}` (renderer pinned in `test_cli_render.py`)

Tests

5 tests in tests/test_bench_qa_sweep.py:

test_summarize_aggregates_directive_pass_counts_per_mode
test_render_markdown_directive_coverage_section
test_directive_compliance_helper_marks_quote_mode_d2_false
test_directive_compliance_helper_marks_lattice_mode_d2_true
test_directive_compliance_returns_empty_on_error_row

Closure rationale

Filed as a closed ticket immediately so the design log captures the artifact alongside the work. The convention from ../TICKETS.md: "Closed tickets stay in place as the design log; do not delete tickets — they are the design log."

Future evolutions (per-row D1/D5 tracking, error-row directive weighting, cross-mode comparison) get their own tickets. This one documents the v1 substrate.

3.3 KiB Raw Blame History