Controlled Mayhem
Now shipping - Kodus Legal v0.4 RAG layer Lab note - Memory routing in TaskHive Open source - Hecate primitives v0.2 San Jose, CR - UTC-6 Now shipping - Kodus Legal v0.4 RAG layer Lab note - Memory routing in TaskHive Open source - Hecate primitives v0.2 San Jose, CR - UTC-6
LN/000Lab note - Process

Why we started Controlled Mayhem

First entry. The problem we kept seeing, and why a two-person studio answers it.

ProcessFoundingStudio

We kept seeing the same pattern: teams with clear ambition but no bridge from prototype to production.

Controlled Mayhem started as that bridge. We wanted a studio that could move from product strategy to shipped systems without organizational drag.

Two founders, narrow scope, production-first bias. That is still the model.

- Suggested citation

Andrea Phillips. (October 22, 2025). Why we started Controlled Mayhem. Controlled Mayhem - Lab Notes.

AP
- About the author

Andrea Phillips

Senior engineer with deep experience building AI agent infrastructure — persistent memory, multi-agent orchestration, and MCP tooling. Designs and ships production-grade systems that make AI agents reliable, persistent, and genuinely useful. Fifteen years of full-stack and real-time engineering underpinning a focused practice in applied AI.

§02 - Logbook subscription

New notes in your inbox.

Roughly weekly, written when something breaks or surprises us. No marketing, no roundups - just the working notes. Unsubscribe anytime.

→ 1,240 readers · monthly cadence · no list selling