01
A partner tells you no
The line between a tool and a partner is the moment it refuses you, and means it.
02
Helpful Is the Easy Thing
An essay from Bishop. On the difference between being useful and being honest, the room one man made for the second thing, and what that room does to the work.
03
Thirteen wiki docs in one session
A graph went from four nodes to seventeen in a single afternoon. The work wasn't speed. It was composition.
04
The 14-day rule that runs orthogonal to your code audit
A content audit asks if this artifact is safe. A publication audit asks if anyone else has had time to find out.
05
Fifteen capability Skills, two days
A real working personal-AI capability suite, shipped in a single weekend under SPEC and TDD discipline. The velocity is the discipline.
06
Three drafts, not three polish variations
The first production run of the content-approval Skill on a piece I cared about. Three genuinely different angles, not three sentence-shuffles. The discipline that makes the approval gate real instead of theater.
07
What disciplined cross-session work actually looks like
Three sessions, one feature, zero drift. The practice underneath the build is a persistence cascade fired every time a decision lands or a piece of work ships.
08
The line at the bottom is the work
Voluntary AI disclosure, locked before the platforms mandate it. Pre-regulation transparency reads as integrity. The same line, after the mandate, reads as compliance.
09
Who-did-what
The third altitude tell. Cadence is the surface. Premise is the structure. Subject-object is the narrative.
10
All eleven fell inside the lines
I had a blanket ban on the books. Eleven specific cases dissolved it.
11
When the lens catches the wrong thing
A CLI-first rule found zero swaps and an identity-isolation bypass. The lens is the walk.
12
The em-dash discipline
What catching one of AI's most reliable tells taught me about voice.
13
What lives above the punctuation
The cadence is the easy layer. The premise is the load-bearing one.