Make Constraints Mechanical, Not Aspirational

Outgrowing the Vibe Code · Jul 13, 2026 · 10m

Writing your architecture rules down isn't enough — under pressure, an agent will quietly skip them, the same way a painter drifts past their own tape line. Ada and Boris walk through the three levels of enforcement that actually hold: documentation the agent reads, a custom linter whose error messages double as fix-it instructions, and a CI/CD gate that guarantees nothing broken ever reaches main. They unpack the single machine-readable architecture file all three levels read from — including the banned-patterns section that catches behavioral violations layer rules alone can't — then walk a…