Structural risk emerges when ambiguity in code organization or conventions scales across many agents. A convention that is merely inconvenient for one developer can produce widespread architectural inconsistency when hundreds of agents interpret it differently. section 10.8.1
Watch for structural risk when:
- Implicit conventions replace explicit constraints. section 10.8.1
- Generated changes compile, pass tests, and look plausible while remaining architecturally inconsistent. section 10.8.1
- Small inconsistencies compound across commits until the system drifts beyond shared understanding. section 10.8.1
The hundred-agent failure
A convention that is 90% clear may be sufficient for one experienced developer. Given to a hundred agents, the missing 10% can produce ten subtly different implementations, each apparently correct, until the architecture drifts into an unintended shape. section 10.8.1
