The invariants say what must be true and the artifacts say what gets produced. This is how they get produced: a three-phase pipeline with quality gates, that turns capabilities and their journeys into buildable vertical slices — one at a time.
Sequential, done once. Research-led — the market and regulatory landscape is captured before any artifact is drafted.
Sequential, done once. The system is drawn at the context and container level, and the work is enumerated and prioritised.
Iterative, per journey in priority order. Each journey is scaffolded, modelled end-to-end, then reviewed against the invariants.
A stable journey model is one buildable vertical slice. It becomes a deliverable in the development project. Channel development is a separate concern consuming the capability APIs.
Questions about how this holds up? How it compares with other architectures, and how it behaves at global scale, are covered in the FAQs.