4 Commits
Author SHA1 Message Date
David F GliddenandClaude Opus 5 2472ed8e88 [HARDENING] PENDING-126 + PENDING-122 Amendment 2 — what inducing red revealed, and REVIEWED-102..105 placed
All three findings came from contact while building a red fixture for the
REVIEWED-103 acceptance. None was sought; the search for a control that worked is
what exposed them.

The fleet already violates the condition REVIEWED-104 attached to the NEW
live-binding assertion, on a dependency the ruling did not consider. Three suites
crash on a gitignored corpus/index.db with a raw sqlite traceback, and run-fleet
reports FLEET RED indistinguishably from a code defect — while store.py rebuilds
that file in 0.628 seconds and the clone then runs 7/7 green. So the condition is
retroactive, not prospective. And test_retrieve.py already detects the absence and
skips with a named reason, which makes PENDING-124 recommendation (d) concrete: the
honest third state exists in this fleet, in one suite, and three others lack it.

R0's section_end bound is unguarded. Removing it leaves 31/31 passing. That is the
rule R0 was created to establish after two consumers disagreed on 3 of 253 patterns
with neither right — asserted in prose, correct-but-inert on the live corpus, and
therefore invisible to every test.

test_navigate crashes with StopIteration rather than naming a failure. The exit code
was always right; the legibility is missing — REVIEWED-100's own distinction,
recurring where its fix does not reach.

Also commits REVIEWED-102 through -105, placed by the steward and left uncommitted.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A35wiD55yRHj5U1ECZAX4t
2026-08-08 18:15:20 +02:00
David F GliddenandClaude Opus 5 02c6875def [PROPOSAL] PENDING-119 + PENDING-120: (e) is built, its wiring is not placed
119 — REVIEWED-101 condition 6 sends (e)'s consumer to ~/dotfiles/scripts/ on
cross-repo reasoning, while the same ruling's If-AUTHORIZED line says (e) needs no
cross-repo enumeration. The tension only became live because (e) was built as a
delegation to the gate that already enforced §1.1; a fresh sha-comparing script
would have made condition 6 straightforwardly right. Carries the finding that no
fleet suite validates live binding.

120 — the trigger's pathspec is corpus/ only, so engine/ and tests/ changes run no
suite. Demonstrated by the commit that built (e), which is also the first real
non-probe commit since the trigger landed: the hook ran and no declared check fired.

Both filed rather than fixed, on the steward's direction. PENDING-117 gains a
pointer-only AMENDMENT 2 so the thread is navigable from the ruled item.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A35wiD55yRHj5U1ECZAX4t
2026-08-08 16:44:41 +02:00
David F GliddenandClaude Opus 5 ac4745b599 session 2026-08-08 night: REVIEWED-99/100/101 placed; PENDING-117 amended + PENDING-118 filed; harvest #192 collision -> #194, #195 filed
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01A35wiD55yRHj5U1ECZAX4t
2026-08-08 15:11:29 +02:00
David F Glidden 1a6cdf6cf1 session 2026-08-08: REVIEWED-97 (vi disposition) placed + REVIEWED-98 draft; PENDING-114 authorized, PENDING-115 filed 2026-08-08 12:53:11 +02:00