I stopped being the documentation

Julio, how does this work? How is the architecture laid out, how do we build a module here, why is this screen the way it is. For years, every question like that had the same answer: ask Julio. I wasn't just in the workflow — I was the documentation.

Four chapters ago I started pulling knowledge out of my head — product definition, design, review, support. Answering questions was the loop underneath all of them. This chapter is about where that knowledge landed when it left: the repo.

The context contract

Think about what a new engineer would need to ship well without asking questions: how the architecture is laid out, how a module is built here, what the UX patterns are, what the product is — and what it isn't. An agent needs exactly the same things.

For us that lives in one place: an AGENTS.md at the root of the repo, plus the documents it points to. Architecture layout. Code patterns — what a module, an endpoint, a migration look like here. UX and UI conventions. The project's vision. The rules of the road.

It helps that we work in a monorepo: one place to look, one set of patterns, and the agent sees the whole system instead of a fragment of it.

The proof: a feature on the first try

Then one day we asked an agent for a complete feature and it came out right on the first try. Architecture respected, patterns followed, UI consistent with the rest of the product. It wasn't luck, and it wasn't the prompt. The tell: nobody had asked me anything. The same contract that ended the questions is what let the agent one-shot the feature.

The prompt is the tip of the iceberg. The one-shot is everything underneath.

Kept updated, or it rots

The contract only works if it's alive. When a pattern changes, the file changes — in the same PR, often written by the same agent that noticed the drift. Documentation as a side effect of working, not a quarterly cleanup.

Without this, AI generates code that doesn't fit: review load goes up, rework goes up, trust goes down — and everyone concludes the tools are overrated. The tools were fine. They were working without a contract.

The test

Founder question: if a competent engineer joined tomorrow, could they ship a real feature this week using only what's written down? If not, neither can an agent — no matter which model you're paying for.