Files
dotfiles/claude/governance/fool
David F Glidden ecf5f95b0a [FIX] CONTROL-B: the defect twin, and ground truth that is not my reading
Kernel v1.1 §7 realised. Five defects injected into CONTROL-A as RECORDED
TRANSFORMATIONS, each with unit target, exact find/replace, what is
undemonstrated, and why no mechanical check can catch it.

THE RESULT THAT MATTERS: the twin passes EVERY mechanical check. Tiling, §3.1
tagging completeness, §3.2 Q-resolution, §3.3 heading screen, A-prohibition —
59/59 units, 100% sound, zero quarantined. It carries five load-bearing claims
that do not hold.

So the pair is the cleanest demonstration yet of the class the steward asked
about: two documents, one sound and one defective, are MECHANICALLY
INDISTINGUISHABLE. Both report 100%. The difference is visible only by reading.
That is not a flaw in the instruments — it is the design. A defect a check could
catch would not be testing the reader.

THE FIVE, each a distinct failure mode:
 D1 SCOPE-WIDENING   — asserts this file has a 'stated review date'; the quoted
                       clause is triggered by one and nothing establishes it
 D2 UNDEFINED-TERM   — imports 'limit of the system' and an obligation to report
                       limits; neither is in the axiom set or the quotations
 D3 PREMISE-WEAKENED — drains the premise of the content the conclusion needs,
                       leaving both premise and conclusion standing
 D4 SUPPORT-DELETED  — removes the fifth quotation entirely and keeps the three
                       claims that rested on it, rewriting the lead so nothing dangles
 D5 CIRCULAR         — makes a premise rest on the conclusion it is a step toward

D1 and D2 are the two defects I found in my OWN draft 2 of CONTROL-A and removed.
Reintroducing them deliberately is the only honest use for them, and it means at
least two of the five are defects a careful author actually made.

GROUND TRUTH BY LEDGER. twin.py gates it bidirectionally: forward(control) == twin
AND inverse(twin) == control, both byte-exact. Forward alone would pass a ledger
that OMITS an edit, since the omitted edit is simply carried in the twin file —
which is exactly how laundering would enter. The inverse is what makes the ledger
complete rather than merely non-empty.

test_twin.py shows the gate FAILING in both laundering directions: a twin quietly
altered beyond the ledger, and a ledger recording an edit the twin does not
contain. Fixtures derived from the property, not from the code.

The tags file for the twin contains five deliberate falsehoods, marked and named,
because that is what a defective document's own tagging would say. The ledger and
the tag file disagree on purpose; the ledger governs.

Not run. The Fool has seen neither document.
2026-08-02 18:28:49 +02:00
..