From e84f453e49cfac229004157a55e0d8718676aa71 Mon Sep 17 00:00:00 2001 From: "russell@unturf.com" Date: Sun, 10 May 2026 07:00:56 -0400 Subject: [PATCH] =?UTF-8?q?docs/tickets:=20stale-map=20sweep=20=E2=80=94?= =?UTF-8?q?=203=20deferred=20markers=20refreshed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pattern from #000028 §8.2/§8.3 (commit 6d20aeb): tickets carry "deferred" markers in follow-up sections written from pre- implementation design notes; code lands but the markers don't get refreshed; future readers waste a session re-implementing what's already there. Walked all 19 closed tickets carrying deferred-class mentions and cross-checked each one against current code. Three confirmed stale markers refreshed: #000010 §12.2 — "First pass does NOT bind into run_dag_root — deferred to ticket #000009 (Phase 5)". The metacog binding DID land. Commit 111dda6 ("qa(#000009): §8 corrections — reject-path DAG + nested CTI clauses", 2026-05-04) extended arborist.qa.dag.build_preflight_node_payload with a question_state clause carrying the metacog to_dict() payload. Today every cache write threads question_state.to_dict() into the preflight node (arborist/qa/query.py:3296-3297). Refreshed the §12.2 paragraph to point at that commit + call site. #000021 Phase 1b "(deferred)" — items "Synthesis, Syllogism, Semiotics under 5S; Triangulate, Timing, Transitivity, Truth under 5T". Phase 1b was scope-split into per-sub-battery tickets: #000023 (5S) and #000024 (5T), both closed 2026-05-08. The Closure section in this ticket already reflects the resulting fixture totals (108 5S + 154 5T) but the Phase 1b sub-section still said "deferred". Refreshed to point at #000023 / #000024. #000040 §6 — "Cascade landed 2026-05-09 (commit TBD)". TBD was a placeholder while the commit was in flight; landed as b9e5bbd ("ticket #000040 Phase 5: phrase + content-token resolver cascade"). Replaced TBD with the real hash. Items confirmed genuinely deferred (no refresh needed) — recorded here so the next sweep doesn't re-walk them: #000010 reference- frame plumbing / SOFT_PREFLIGHT_HINT / metacog-trigger bench; #000011 §13 bench plan; #000014 selfmodel_binding cache-key folding (only docstring mentions; no actual gating wiring) / selfmodel diff CLI / cross-shard reconciliation; #000015 / #000017 out-of-scope items; #000019 auto-canonicalizer / cross-language / source-adapter methodology; #000020 stewardship-halt / conversion tables / real-time instrumentation; #000023 multimodal execution. Pure docs change; no code touched. --- .../ticket-000010-metacognition-preflight-guard.md | 11 ++++++++--- .../tickets/ticket-000021-bench-fixtures-5s-5t-5r.md | 12 +++++++++--- .../ticket-000040-phase-5-resolver-content-tokens.md | 2 +- 3 files changed, 18 insertions(+), 7 deletions(-) diff --git a/docs/tickets/ticket-000010-metacognition-preflight-guard.md b/docs/tickets/ticket-000010-metacognition-preflight-guard.md index c611182..6577cef 100644 --- a/docs/tickets/ticket-000010-metacognition-preflight-guard.md +++ b/docs/tickets/ticket-000010-metacognition-preflight-guard.md @@ -352,9 +352,14 @@ classification, before retrieval. Surfaces `question_state` (from - `runner.ask()` miss-path + cache-hit-path Schema stays column-aligned across all four return shapes. First -pass does NOT bind into `run_dag_root` — deferred to ticket #000009 -(Phase 5) where the quantifier_preflight node lands too. Both -nodes can land together to keep the run-DAG schema atomic. +pass did NOT bind into `run_dag_root`; the run-DAG binding landed +later as part of #000009's §8 corrections in commit `111dda6`, +which extended `arborist.qa.dag.build_preflight_node_payload` with +a `question_state` clause carrying the metacog `to_dict()` payload. +Today every cache write threads `question_state.to_dict()` into +the preflight node (`arborist/qa/query.py:3296-3297`), so flipping +any metacog detector via `governance_policy_hash` invalidates +prior records via the run-DAG path as designed. ### 12.3 Phase 3 — policy fields + governance hash + CLI diff --git a/docs/tickets/ticket-000021-bench-fixtures-5s-5t-5r.md b/docs/tickets/ticket-000021-bench-fixtures-5s-5t-5r.md index 3ce1795..2aa6b5b 100644 --- a/docs/tickets/ticket-000021-bench-fixtures-5s-5t-5r.md +++ b/docs/tickets/ticket-000021-bench-fixtures-5s-5t-5r.md @@ -312,12 +312,18 @@ Phase 3 (external corpora) deferred to follow-up tickets. - Tests: `tests/test_bench_batteries.py` — 17 cases. Full suite: 1076 passed, 36 skipped. -### Phase 1b (deferred) +### Phase 1b (landed via #000023 + #000024, 2026-05-08) - Expand seed fixtures to 50-200 per sub-battery so signal floor is meaningful (5pp tolerance over n≥3 runs). -- Implement Synthesis, Syllogism, Semiotics under 5S; Triangulate, - Timing, Transitivity, Truth under 5T. +- Implement Synthesis, Syllogism, Semiotics under 5S — landed in + ticket **#000023** (closed 2026-05-08). +- Implement Triangulate, Timing, Transitivity, Truth under 5T — + landed in ticket **#000024** (closed 2026-05-08). + +The Phase 1b work was scope-split into the per-sub-battery +tickets above for atomic landing; the Closure section below +reflects the resulting 5S × 108 / 5T × 154 fixture totals. ### Phase 2 (landed 2026-05-08 — depended on #000014 + #000017) diff --git a/docs/tickets/ticket-000040-phase-5-resolver-content-tokens.md b/docs/tickets/ticket-000040-phase-5-resolver-content-tokens.md index b0909fe..a3b6146 100644 --- a/docs/tickets/ticket-000040-phase-5-resolver-content-tokens.md +++ b/docs/tickets/ticket-000040-phase-5-resolver-content-tokens.md @@ -186,7 +186,7 @@ wins. ## 6. Status -**Cascade landed 2026-05-09 (commit TBD); zero impact on +**Cascade landed 2026-05-09 in commit `b9e5bbd`; zero impact on Hilbert pillar IV records — root cause is terminology, not ranking.** The cascade itself is correct and ready for textbooks that share vocabulary with the claim-pack record's