Engineering log · built in public
The how.
Long-form stories from building Stratam. Architecture decisions, lessons learned, what shipped and what broke. The complement to the changelog — which tells you what shipped, where this tells you why.
The post-process that catches Stratam lying to himself.
On May 16 the user yelled at the bot for the fourth time in two
minutes for fabricating a deploy that didn't happen. The fix was
a three-tier anti-fabrication regex that scans every reply and
cross-checks it against the actual tool calls that fired. Here's
how we built it, why each tier exists, and the false-positive that
almost killed it.
Read post →
Why Stratam ships code to himself every 30 minutes.
The eternal-improvement loop proposes and ships one self-modifying
change every cycle. Most teams would call this insane. Here's the
safety architecture (parse-check, snapshot, atomic deploy,
watchdog rollback, restart-cascade breaker) that makes it
survivable — and why a 1-founder team running a 24/7 agent service
actually needs it.
Read post →
More posts in progress. The eternal loop ships these too.
Want the engineering-log version of every change?
The full record lives at /changelog — auto-rendered from
The full record lives at /changelog — auto-rendered from
BUILD_NOTES.