Explore
Change the lock
Twenty-six weeks of daily sessions with an AI that could not read the work it was helping with, told from the record. Press play and watch the wall beside the door fill up with everything that grew to keep a hand-uploaded copy current, each note on the week git says it appeared. Then watch what happens to the wall on the week the lock gets changed.
The door · 2 March to 5 September · every date from git
1 on the wall
wk 1 of 26
4 Mar · week 1
Session one. The instructions go up.
A chat project with a hand-uploaded copy of the repository behind it. The rules open with ask for the state file, search the project’s copy, frame every retrieval as an ask. Three sessions this week, then five most weeks for twenty-six.
The surface can read the work
the instructions, as they stood on 28 August
The instructions card · what was taped to the wall
flip the switch, or scrub to the move
Standing rule, first and above everything else
Boundary
Session open, every time
Retrievals
Session middle
Session close
Writing
Read the full article
Method or compensation, on SubstackThe essay carries the four corrections that started this, the sticking front door, what a barcode study found about workarounds, and the counted retraction behind the switch above. Adjacent, if you came for why a copy cannot see its own rot, is Stale by design.
Get the next one
One essay a week on making data and AI systems trustworthy enough to act on.