Artifact drift occurs when a design document, test suite, or other handoff artifact becomes stale as constraints, implementations, and decisions change. A polished artifact can preserve its timeline while no longer representing what agents actually used. section 5.6.5
Drift creates several practical failure modes:
- Context loss: handoffs omit rejected alternatives, emerging constraints, and discovered edge cases. section 5.6.5
- Version ambiguity: agents may update the original, create a new version, or work from undocumented corrections. section 5.6.5
- Verification theater: artifacts appear complete while testing the wrong requirements or describing a system changed several commits earlier. section 5.6.5
- Synchronization overhead: maintaining documents, cross-references, and dependencies consumes agent tokens and reviewer attention. section 5.6.5
A design document that drifted
A design document accurately captures the initial plan. After two implementation iterations introduce new constraints, the document remains polished but no longer describes the system or the assumptions guiding decisions. A passing test suite may reinforce the illusion if it validates obsolete requirements. section 5.6.5
