CONCEPT
Architectural Drift
The gradual accumulation of <em>unrecorded coupling decisions</em> that produces accidental system structure—enabled by zero-cost refactoring.
Architectural drift is the progressive, often imperceptible accumulation of coupling decisions that individually seem harmless but collectively produce a system whose structure is accidental rather than designed. When the cost of changing interfaces approaches zero (as in AI-augmented individual building), the designer can refactor components rapidly without the coordination overhead that once forced deliberation. An interface modified Monday creates a dependency constraining a Wednesday decision. The Wednesday decision is made without reference to Monday's change because the designer doesn't remember it—made quickly, in flow, not recorded as architecturally significant. By Friday the system contains coupling that the designer cannot reconstruct, because decisions were made incrementally at a pace exceeding the capacity for deliberate architectural thought.
In The You On AI Field Guide
The organizational model provided natural resistance to drift through coordination costs. Changing an interface between Team A's component and Team B's component required meetings, negotiations, documentation, testing across both teams. The overhead was high enough that teams only changed interfaces when the benefit clearly exceeded the cost. This friction served an architectural function—it forced teams to think carefully about coupling