The useful part of a vault portal was admitting the ai should read, not write
Why an AI-facing vault portal shipped as a narrow, auditable read-only path, and why write access waits until the key model has earned it.
The build log
Notes from running agents in production.
Build log, architecture patterns, and observations from running autonomous AI systems in production.
-
-
I split my personal cockpit out of the product and everything got cleaner
Forking the product repo into a separate operator console let me ship a tailnet-only cockpit without dragging product baggage along. The fixes I had been deferring for months got cheap the same week.
-
The reuse story died, so I shipped a new cart instead
I went in expecting to wire tournament registration onto the existing cart. One grep later, the premise was dead and I was designing from scratch. The new cart shipped the same day.
-
The Hotfix That Lied: STAGING/LIVE in JIRA, Never Merged to Master
The ticket said STAGING/LIVE. It had a fix version, 3.349, and a real commit with a real diff.
-
JS Detections: the one Pro-tier Cloudflare lever that actually catches HTTP-replay proxies
Pro-tier bot rules never touched a residential proxy pushing 224k requests a day. JS Detections moved the fight to a capability it couldn't fake.
-
I finally treated the blog like a product
The unblock was structure, not inspiration: a parent epic, five child tickets, and a per-ticket folder convention.
-
I killed my clever vault hierarchy in one day
I rebuilt my vault hierarchy three times in one day before it held. Stable nouns outlast clever categories, and dashboards should be generated, not hand-kept.
-
My agents needed a filing system before they needed more intelligence
The vault, the task model, and the session pipeline each had a slightly different definition of active. The fix was not a smarter prompt. It was making them agree at the filesystem level.
-
The first useful agent teammate needed a Gmail account
Before an agent can share docs or run a dispatch loop, it needs an identity, permissions, and an inbox that behaves like a work queue. The bottleneck wasn't model quality. It was getting the agent a badge.
-
My whole 1,200-domain provider split died instantly: keep a second DoH provider on hand
I was halfway into a Cloudflare-for-SaaS migration audit when every DNS lookup I depended on failed at once. Not some of them, not the flaky ones, all 1,264 of them, and they failed instantly.
Follow the Build
The real failures and fixes from building AI systems, one practical lesson per post. Get the next one in your inbox.