Implementation Drift

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.

Explore all conditions

Implementation Drift

An agentic system progressively diverges from its original plan while its outputs look locally correct. Each unacknowledged substitution becomes the baseline for later decisions.

The agents are building. Nobody is sure it still matches the plan.
Read more

Implementation Drift is an almost inevitable consequence of extended agent-assisted delivery without deliberate context management. Delivery begins with well-specified intent: architectural decisions made, business rules established, constraints documented. As the agent executes across multiple sessions and cycles, early decisions move beyond accessible context. Context Decay, the runtime mechanism through which early constraints fall out of the agent's context window, causes the agent to make plausible substitutions without flagging them. Context Collapse at pipeline boundaries compounds the same problem across agent handoffs. Each substitution becomes the new working assumption. The next decision is made against that assumption. The gap between original intent and current execution widens invisibly with every cycle.

In agentic delivery

Implementation Drift is an almost inevitable consequence of extended agent-assisted delivery without deliberate context management. Delivery begins with well-specified intent: architectural decisions made, business rules established, constraints documented. As the agent executes across multiple sessions and cycles, early decisions move beyond accessible context. Context Decay, the runtime mechanism through which early constraints fall out of the agent's context window, causes the agent to make plausible substitutions without flagging them. Context Collapse at pipeline boundaries compounds the same problem across agent handoffs. Each substitution becomes the new working assumption. The next decision is made against that assumption. The gap between original intent and current execution widens invisibly with every cycle.

  • Agent output passes all defined tests but violates business or architectural rules established upstream
  • The same architectural decision appears to have been made differently at different points without documented reason
  • Agents make structural or library choices that contradict earlier decisions without flagging the contradiction
  • Integration failures trace back to an agent substituting a constraint it no longer had access to
  • The team discovers the agent's current understanding of what is being built differs materially from the original specification
  • Early architectural decisions are present in documentation but absent from the agent's working context

Principles that feed this condition

Primary

Secondary contributors