Claude

claude-compass — working notes

Notes on my rule-based guard for Claude Code: the hook contract, the Python/Go pair, the shared test set, and the holes I found along the way.

two robots standing on either side of an easel holding a blank page layout — the familiar round-headed robot gesturing at the design, and a square-headed robot with a flat unimpressed expression holding a clipboard

I Let Two AIs Argue Over My Homepage — To See If They Actually Think Differently

A single model playing scrum master is just one mind doing all the voices. So I gave two models from two different labs the same deliberately vague design brief, let them collide, and watched what each one refused to give up. I wasn’t trying to prove the merge was better — I was trying to prove they were different.

the robot holding up a phone showing a message bubble, an arrow curving across to the boy in the cap who holds his own phone showing the same bubble as it arrives

Every Robot in My House Can Text Me Now

My house is full of automation that never told me anything — until I gave it one push bus. The first thing I taught it to do was warn me before Claude Code cuts out mid-task.

the boy in the cap holding up a small ordinary key, but the shadow it casts on the wall behind him is a clawed hand gripping a huge jagged sword; the robot beside him looks on

🚩 I Built a Usage Dashboard and Tripped Claude Fable 5's Safety Net

I asked Claude Fable 5 to help me self-host a dashboard for my own Claude usage. Halfway through, its dual-use safety measures flagged the conversation and downshifted me to Opus 4.8. Nothing I did was wrong — the request just had the shape of something that is. That gap, between what a thing looks like and what it’s for, turns out to be the whole story.