Architecture
- Two locks on a static siteThis site is static, but it has a private studio where I write and keep documents. It is guarded twice: once at the edge by an identity service, and again inside the code by checking the signed token myself. Why one lock is not enough, and the ten tests that prove the second one.
- An AI harness that can't lie quietlyYou cannot stop a language model from inventing a fact. You can build the harness around it so that an invented fact has nowhere to hide. The design of the small, private AI editor I use for documents that must stay true.
- Decks as dataAsking a model to produce a PowerPoint file gives you something hard to edit and impossible to govern. I built a deck generator that treats a presentation as structured data first. Sixteen components, twenty tests, and one rule that settled every argument.
- Rebuilding Sylang on the data platformSylang started as a text language in git, the way my old architecture language worked. This summer I moved its source of truth into the customer's own data platform. The decisions, the trade-offs, and the numbers behind them.
- Isolation is not a promptRunning one agent framework for several users, I hit session and memory leaking between instances. The fix was not a better system prompt. It was operating-system isolation and a small control plane.
- One MCP layer instead of 500 integrationsWhen every AI client wants to talk to every engineering tool, the integration count grows as a product, not a sum. The arithmetic behind why I put one MCP layer in front of an enterprise engineering tool estate.