Engineering · Jul 2026 · 4 min
Teaching agents to respect your ADRs
Code generation is easy. Code that honors two hundred prior architecture decisions is not. How we compile ADRs into constraints the Architect agent can’t ignore — and what broke along the way.
Read the post// resolve constraints before planning
const adrs = await graph.query('adr')
.binding(workItem.systems)
.active();
const plan = architect.plan(workItem, {
constraints: adrs, mode: 'strict'
}); // violations fail at plan timeThe DAG is the org chart
When work flows between agents, topology is management. What we learned designing the routing layer.
3 min read
Audit trails that write themselves
Provenance as a pipeline property: every artifact knows its intent, its decision, and its approver.
3 min read
Evaluating prompts like code
Regression suites for instructions: how promptvc catches behavioral drift before production does.
3 min read
Writing for two audiences
Your next design doc will be read by agents. What that changes about how engineers write — and what it doesn’t.
3 min read
Ontology migrations without downtime
Evolving the schema of organizational truth while a thousand agents are reading it.
3 min read
Human gates that scale
Approval fatigue is a design flaw. Where human judgment actually belongs in an agent pipeline.
3 min read