Anti-patterns: what can go wrong

Phase 4 can fail in predictable ways. The methodology section already describes the conceptual anti-patterns (the Speed Trap, Context Drift). This section covers the operational anti-patterns that emerge during execution, especially in parallel construction.

1

The Unsupervised Build

›

2

Optimistic Parallelization

›

3

Integration Synchronization Too Late

›

4

Siloed Decision Log by Track

›

5

Track-by-Track Fidelity Review

›

6

The Technical Unanimity Gate Review

›

Quick reference

Anti-pattern	Symptom	Root cause	Prevention
Unsupervised Build	Surprises during integration	Context Engineer absent during construction	Real-time visibility into all Decision Logs
Optimistic Parallelization	Collisions between tracks	Unverified dependency graph	Explicit parallelization authorization
Late Synchronization	Accumulated incompatibilities	Synchronizations not defined in the graph	Synchronizations by graph, not by calendar
Siloed Decision Log	Unescalated cross-track decisions	No visibility between tracks	Distributed Decision Log with impact classification
Track-by-Track Review	Incoherent system despite correct components	Tendency to evaluate by track	Mandatory Block 0: system review
Technical Unanimity Gate	Technically correct solution that doesn't solve the problem	Stakeholders excluded from gate	Mandatory sign-off from non-technical stakeholders