liveBook · Manning

Artifact drift

As explained in Vibe Engineering

The divergence of a recorded artifact from the current assumptions, implementation, or decisions it is meant to represent.

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

How Vibe Engineering covers it

How deep it goes
Traces context loss, version ambiguity, misleading verification, and synchronization costs without prescribing a complete remediation process.
Examples
Uses stale design documents, obsolete requirements, wrong test targets, and outdated system documentation as concrete examples.
What it assumes
Assumes familiarity with design documents, implementation iterations, tests, documentation, and agent handoffs.
What you can do after
Diagnose artifact drift by comparing artifacts with current constraints, implementations, decisions, and actual agent usage.
How it connects
Connects artifact drift with documentation, design documents, test suites, verification, context boundaries, and agent orchestration.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.