Make context visible

Pre and post coding agents: getting a group of smart, opinionated people aligned on intent will always be one of the hardest yet most valuable parts of shipping great software. With coding agents, this problem gets worse. You can build the wrong thing really fast, in five directions at once.

The fix isn't better agents. It's about getting to the best context. We get to the best by getting the most relevant stakeholders involved.

In most tools, context is a flat chat log or a static document. Scott treats context as a directed acyclic graph — like git, but for intent. Every version, every branch, every fork is preserved. Anyone on the team can time-travel to any point and understand the full line of thinking that led to the current proposal.

This matters because it makes visible which parts of a proposal came from an agent and which came from the human leading the project. Teammates can dig into how you got to your proposal — not just the final output. They can see when the agent suggested an approach, when the human overrode it, and when the team debated alternatives.

The DAG is what makes intent review substantive rather than ceremonial. Reviewers aren't approving a document — they're approving a line of reasoning they can fully inspect.