Context
What the system knows, what it does not know, and how that boundary is kept visible.
Technical edition
Systems, controls, and receipts from the work itself.
Technical AI field notes
See how the work holds together.
The Build Log documents what runs, what fails, what has to stop, and what still needs a human decision. It is a working archive, not thought leadership after the fact.
What the archive contains
Control
Where AI can move work forward, where a person decides, and where the system has to stop.
Evidence
What was observed, measured, and recorded instead of simply assumed.
Current field notes
Published field note
The Day I Taught Failures to Speak, Everything Started Shouting
A customer reported a dead Save button on Locations and Fields about two hours after we shipped a fix for a dead Save button on bracket teams. So I checked whether our fix was involved.
Published field note
The Cleanup Tool That Had to Check Before Deleting
The cleanup run that retired 29 dead domains took three minutes. What made it safe to run was a tool that refuses to trust our own inventory.
Published field note
The Agent Process That Didn't Know Its Session Died
The browser had been dead for 39 hours, and it was still asking our staff toolbar who it was, over and over, with a login that had expired long before.
Human control stays visible
Human decides
Intent, commitments, exceptions, and high-stakes judgment.
AI can
Sort, draft, check, route, and surface the work that needs attention.
AI must stop when
Context is missing, a decision is ambiguous, or the next action could cause harm.