Unintended System Conditions. A USC is an unplanned state that builds up when principles are repeatedly violated. It is the default output of the system as currently designed, not a one-off incident or a people problem. Fixes aimed at symptoms improve things briefly before the condition reasserts itself. Which principles feed each condition is NOT stored here: it is derived at runtime from the consequence-to-condition links in the principle files.
Work cannot flow without constant coordination across team boundaries. Commitments depend on capabilities owned by teams whose priorities are set independently.
The team owns the commitment. Nobody owns the gap.
Work cannot flow through the delivery system without constant coordination across team boundaries. Every meaningful delivery commitment depends on capabilities owned by other teams whose priorities are set independently of the commitments they are asked to support. The team owns the deadline. The platform team, security team, or shared service owns the capability needed to meet it. Nobody owns the gap between them. This structural mismatch makes accountability impossible to fulfill by design.
In human-driven delivery, dependency density is felt as coordination overhead between teams. In an agentic system, dependencies do not disappear. They migrate. Agent pipelines create new technical dependencies between systems, data sources, and services that are less visible than human team dependencies but compound just as quickly when unmanaged.