David F GliddenandClaude Opus 5
33754673b8
! 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
Custom Scripts
This directory contains custom scripts that will be symlinked to ~/bin.
Setup
- The symlink script will link all scripts from this directory to
~/bin - Make sure
~/binis in your PATH (add to.zshrc):export PATH="$HOME/bin:$PATH"
Adding New Scripts
- Create your script in
~/dotfiles/bin/ - Make it executable:
chmod +x script_name - Run the symlink script to link it to
~/bin
Script Guidelines
- Start with proper shebang:
#!/usr/bin/env bashor#!/usr/bin/env zsh - Add help/usage information
- Use meaningful names
- Document what the script does