The pattern catalog
Proven on one engagement.
Applied to every engagement.
How we build is the method — the pipeline, the gates, the receipts. This is the other half: the patterns that method keeps producing. Each one was proven on a real engagement before it earned a place here, and each writeup carries its receipts — the numbers are real; the clients are simply unnamed.
§ 01 The Engagement Hub proven in production
One front door for everything we build together.
Every engagement gets a hub: one login, one URL, and every deliverable — decisions, designs, test rounds, evidence — citable at a stable address.
Read the pattern →§ 02 Infrastructure as Code, All of It proven in production
Every environment is declared, reproducible — and disposable. Except your data.
We provision engagement infrastructure from Terraform modules: environments are cattle you can reset with one command, and the data layer is protected by construction.
Read the pattern →§ 03 API + MCP From One Seam proven in production
Build the capability once. Every consumer — human, app, or AI agent — gets it.
Capabilities live once behind a single gateway; the web app, the REST API, the CLI, and the MCP surface your AI tools call are all adapters over the same seam — with the same authorization.
Read the pattern →§ 04 Testing That Teaches designed — first pilot scheduled
Acceptance rounds, retests, and training material — one content framework.
UAT runs on your hub as typed, versioned test plans with captured evidence and answered dispositions — and the same framework is built to mint regression pools and seed training.
Read the pattern →§ 05 Progressive Grounding proven in production
AI sessions that start oriented — instead of spending your budget re-learning your business.
Every AI session grounds in layers: hard safety rails first, a compiled orientation brief, then a one-line map of every artifact — descending into detail only where the task needs it.
Read the pattern →§ 06 The Vault proven in production
Your decision record lives in the repository — and you keep it when we leave.
Every engagement builds a vault: decisions, designs, requirements, and evidence as plain text in the same repository as the code they govern. One history, with git’s machinery behind it.
Read the pattern →§ 07 Release Trains proven in production
Releases with intake, gates, and a close that refuses to lie.
Named, scheduled releases: work is admitted through intake, soaks in a reset-in-one-command slot, and closes through a guard that checks the deliverables actually exist.
Read the pattern →§ 08 The Canonical Template proven in production
Your engagement starts at hour one, not month three.
Every new engagement clones a golden repository that already encodes the fleet’s lessons — the hub, the vault, the grounding, the infrastructure modules, the verification gates.
Read the pattern →§ ·· The rest of the catalog
Sixteen patterns and counting.
8 public writeups so far — not the whole shelf. Still being written up, among others:
Want the one that fits your problem before it’s published? Bring us an intent — the fastest way to see a pattern is on your own engagement.