Commit Graph
2 Commits
Author SHA1 Message Date
David F GliddenandClaude Opus 5 33754673b8 [FIX] §9's last two clauses: mute/off, and a shorter way to call him by name
! tarbuckle              ! tarbuckle mute      ! tarbuckle status
    ! tarbuckle what now     ! tarbuckle off/on

§9 said mute and off were "available at all times" and there was no way to do either;
the spec listed it as owed twice before it was built. Now one switch, read by every
surface.

⚠ mute and off are NOT the same and the difference is presence versus speech. `mute`
silences the utterance and LEAVES THE BODY — he is still in the room, which is §8a's
entire argument for the status line: visible silence at near-zero cost. `off` removes
him. Collapsing the two would have deleted the distinction the body exists to make.

The mute switch is the one piece of state the fool is permitted to be steered by,
because §9 says muting is never a fault and a mute he could ignore is not a mute. It
conserves no draw and remembers nothing: a switch, not a memory.

The wrapper is on PATH so the steward runs it directly rather than through the executor.
That is the point of the surface, and the wrapper says so in its own header: a fool
relayed by the executor is the executor's paraphrase of a fool.

Body 32/32, mumble 26/26, seam 15/15, invoke 17/17, wrap 21/21.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf
2026-08-25 17:04:05 +02:00
David F GliddenandClaude Opus 5 8a0e5c448d [FIX] §9 named invocation, and the spec omission that hid it
The steward asked whether he could be invoked. §9 says yes — "the steward calls it by
name, the executor or jurist yields the floor, the fool answers at length" — and it was
not built. Worse, yesterday's spec did not list it: not in what exists, not in what is
owed. A document whose whole job is to say what is and is not there, silently missing a
requirement. Recorded in the spec rather than quietly corrected, because that is the
fourth negative state-claim to go wrong in two days and the second inside a document
written to prevent the class.

The net is widened EXPLICITLY and in one dimension, per the steward's ruling: §9
licenses LENGTH for this surface and nothing else, so the ceiling goes 9 -> 180 and the
one-line rule lifts, while no-advice, no-questions, no-'we', no-vocabulary-of-lack and
no-addresses are untouched and are not parameterised anywhere. Silence-on-violation
holds here too. Six negative controls assert each clause still bites at length — the
executable form of "widen it explicitly, but never relax silence-on-violation".

⚠ Length is where the no-truth-value guard is most at risk: a fool given a paragraph
elaborates, and elaboration is how a gesture becomes a claim. The prompt spends its
budget there rather than on register.

It finds the newest transcript itself, so the steward runs it directly rather than
through the executor. That is the point of the surface: a relayed fool is the executor's
paraphrase of a fool.

⚠ One control asserted a literal the prompt did not use ("NO TRUTH VALUE" against
"NOTHING YOU SAY MAY HAVE A TRUTH VALUE"). It fired, correctly. Rewritten to test the
substance — phrase present AND negated — because the original would have passed happily
on any rewording that dropped the constraint entirely.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J6hZXNYSxEfZseBGTni4sf
2026-08-25 16:50:33 +02:00