Engineering notes

How we build AI systems that hold up in production.

Our guides are written for the people who fund and run projects. These notes are for the people who build them: agent architecture, evaluation harnesses and the security details we apply on client work. We share them openly — and update them as the models change.

What we apply on client work

Three rules behind every assistant we ship.

Model-agnostic by design

Frontier models now ship every few weeks. We keep prompts, tools and evals portable so you can switch between Claude, Gemini, GPT, Grok or an open-weight model on evidence, not marketing.

Evals before opinions

Every assistant we ship comes with a test set built from your real questions and documents, and a gate that blocks changes that make answers worse.

Secrets never meet generated code

Agents run tools in disposable sandboxes; credentials stay in a vault behind a proxy. A prompt injection has nothing to steal.