Skip to main content

16 docs tagged with "ai-build-phase"

View all tags

Anti-patterns: what can go wrong

Six operational anti-patterns of Phase 4: the unsupervised build, optimistic parallelization, late synchronization, siloed Decision Log, track-by-track review, and the technical unanimity gate.

Connection to Phase 4: AI Build Phase

When the Gate Review is complete, the team has a system of Agents, Rules, and Skills. The construction phase doesn't start with a briefing — it starts with context.

Connection to Phase 5: Market Phase

Construction is not the end of thinking. It's the way to put thinking to the test. Three specific transfers connect AI Build Phase to Market Phase.

Context Drift: this phase's specific risk

Context Drift is the gradual accumulation of technical decisions that, individually reasonable, silently move the built solution away from the original problem. In parallel construction, it distributes across tracks.

Effort

AI Build Phase effort depends on solution complexity, team structure, and construction model. Measured in Story Files completed and coordination quality, not calendar time.

Exit criterion: the Gate Review

The AI Build Phase is complete when stakeholders recognize the entire system — not just its components — as faithful to the Problem Statement and Solution Brief.

Parallel construction anatomy

The internal structure of parallel construction: the dependency graph, the distributed Decision Log, integration synchronizations, and the QA Agent's role.

Phase 04: AI Build Phase

Operational guide for executing Phase 4: setup, Story File-driven construction, gap management, fidelity review, and closure. With parallel construction model.

Phase 04: AI Build Phase

Build well because it was thought well. The phase where context materializes into a solution faithful to the defined problem.

Phase artifacts

Six artifacts that evidence faithful construction: distributed Decision Log, updated graph, synchronization minutes, Build Validation Report, Context Document, and the Iteration Brief.

The parallel construction model

How to manage simultaneous construction by multiple teams and AI agents without losing coherence. The dependency graph, role hierarchy, and distributed Decision Log.

The step-by-step process

The five steps of Phase 4: environment setup, Story File-driven construction, gap management, fidelity review, and Decision Log closure.

What AI Build Phase is and what it isn't

AI Build Phase is a process of context materialization, distributed fidelity supervision, and coordinated gap management. It is not free design, nor discovery, nor unrequested improvement.

Who participates and how the team organizes

Phase 4 introduces a functional hierarchy with five decision levels. The Context Engineer supervises, the Tech Lead coordinates, Dev Leads execute, and the QA Agent protects.

Why this phase exists

Phase 4 exists so that AI's construction speed becomes an asset, not a risk. Its function is to protect context integrity during construction.