From 2bbd12a270266240628dc5eed840aa5d100d2530 Mon Sep 17 00:00:00 2001 From: "russell@unturf.com" Date: Sat, 2 May 2026 12:27:38 -0400 Subject: [PATCH] =?UTF-8?q?docs(bench):=20rename=20qa-modes-bench-2026-05-?= =?UTF-8?q?02.md=20=E2=86=92=20qa-modes-bench.md?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 2026-05-02 journal is the LIVING bench doc — it absorbs each day's bench results and rolls forward. Pinning a date in the filename made it look like a frozen snapshot when it is in fact the working journal. Naming pattern moving forward: docs/qa-modes-bench.md — living journal (latest run) docs/qa-modes-bench-2026-04-30.md — historical snapshot (frozen for the JSON-mode hardening day) Future dated snapshots stay dated. The bare 'qa-modes-bench.md' is always the current state of the substrate. Updated references in: - CLAUDE.md (× 2) - aborist/qa/prompts.py - aborist/qa/query.py - docs/bench-maxing.md The 2026-04-30 references in docs/cti-architecture.md, docs/test-coverage-audit-2026-05-01.md, docs/verifier-semantic-gap-design.md, docs/TICKETS.md correctly point at the historical snapshot and stay as-is. --- CLAUDE.md | 4 ++-- aborist/qa/prompts.py | 2 +- aborist/qa/query.py | 2 +- docs/bench-maxing.md | 2 +- docs/{qa-modes-bench-2026-05-02.md => qa-modes-bench.md} | 0 5 files changed, 5 insertions(+), 5 deletions(-) rename docs/{qa-modes-bench-2026-05-02.md => qa-modes-bench.md} (100%) diff --git a/CLAUDE.md b/CLAUDE.md index fbefb3f..7e695a3 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -153,7 +153,7 @@ revert without reading why. When in doubt, walk the `verifier_method="claim_lattice"`; `answer_mode` on the run-DAG + `json_fixups` disambiguate. Each mode folds into `governance_policy_hash`. See `aborist/qa/verify.py`, - `docs/qa-modes-bench-2026-05-02.md`. + `docs/qa-modes-bench.md`. - **Four-rung ladder (lattice-mode display layer)**: POINTER-LINKED → ANCHOR-WARRANTED → EVIDENCE-WARRANTED → (ENTAILMENT-VERIFIED reserved); UNGROUNDED below. Each rung names a strictly stronger @@ -325,7 +325,7 @@ Architecture / ongoing work: - `docs/cti-architecture.md` — CTI Clause Tree Intelligence. - `docs/mesh.md`, `docs/mesh-deploy.md` — mesh wire + deploy. -- `docs/qa-modes-bench-2026-05-02.md` — latest bench (post-Rule-8 / +- `docs/qa-modes-bench.md` — latest bench (post-Rule-8 / post-warrant-generalization / post-frame-detector). Quote 0.50, pointer 0.23, JSON 0.44. Concurrency landed alongside. - `docs/qa-modes-bench-2026-04-30.md` — JSON-mode hardening journey diff --git a/aborist/qa/prompts.py b/aborist/qa/prompts.py index c597e08..bbc479b 100644 --- a/aborist/qa/prompts.py +++ b/aborist/qa/prompts.py @@ -18,7 +18,7 @@ copy. Bumping any of these strings folds into ``governance_policy_hash`` in both code paths simultaneously, so the cache namespace partitions cleanly across the substrate. See -``docs/qa-modes-bench-2026-05-02.md`` for the bench-driven +``docs/qa-modes-bench.md`` for the bench-driven hardening history. """ from __future__ import annotations diff --git a/aborist/qa/query.py b/aborist/qa/query.py index b8dda9a..98370d4 100644 --- a/aborist/qa/query.py +++ b/aborist/qa/query.py @@ -413,7 +413,7 @@ DEFAULT_QUERY_POLICY = { # (backward-compatible at the API boundary). The mapping itself # lives in policy so changes fold into governance_policy_hash and # partition the cache namespace cleanly. See - # docs/qa-modes-bench-2026-05-02.md "recommended context budget". + # docs/qa-modes-bench.md "recommended context budget". "max_context_chars_by_mode": { "quote": 24000, "claim_lattice_pointer": 24000, diff --git a/docs/bench-maxing.md b/docs/bench-maxing.md index cc01b61..45f36a0 100644 --- a/docs/bench-maxing.md +++ b/docs/bench-maxing.md @@ -107,7 +107,7 @@ during the JSON-mode hardening journey: - **Doc captures the journey, not just the end state.** `docs/qa-modes-bench-2026-04-30.md` shows the day's progression (baseline → retry → trim-and-verify → pointer-IDs → stop-sequence - → self-heal). `docs/qa-modes-bench-2026-05-02.md` continues the + → self-heal). `docs/qa-modes-bench.md` continues the journey through Rule 8 promotion, anchor-class warrant generalization, per-mode context budgets, and the bench-harness upgrades named below. Each row is a named failure + fix + bench diff --git a/docs/qa-modes-bench-2026-05-02.md b/docs/qa-modes-bench.md similarity index 100% rename from docs/qa-modes-bench-2026-05-02.md rename to docs/qa-modes-bench.md