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
A Saved Reply Is Not a Stored Record
A review or handoff is not complete when an agent says it saved the work. It is complete only when the receiving system can read the exact record that the next decision depends on.
Published field note
The one-person company story everyone is writing, with git receipts
One week of receipts from actually running the company the WSJ just profiled: 51 wrong review verdicts, 136 bounced emails traced back to orders, and two apology drafts nothing is allowed to send.
Published field note
The bot swarms moved faster than my firewall rules
Near-daily bot swarms were crawling or downing the site, and every rule I wrote landed after the swarm had already moved on. The fix wasn't a better rule. It was admitting the firewall lived on the wrong machine.
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.