MAP 09 / V0.1
Map 09 / Pipeline

Client build

How a Voyager client site goes from signed contract to managed-fleet client: 7 modules, each ending in a gate that must go green before the next starts. Two tracks run through it — Track A, the identical baseline spine (the automation target), and Track B, the brand and content divergence (human judgment). Renders the canonical Build Pipeline flow map from the Knowledge Base.

Track A — baseline spine (automatable)
Track B — client divergence (human)
gate — checkable predicate
Track:
Status: