Skip to content

Z0 — Reference-Architecture Framework

Asset: Z0  |  Workstream: [GTM]  |  Ownership: [SO]  |  Owner: Sagar Status: drafted

Purpose: The template every Z follows — like F0 is to the F-modules. Sets the five required artifacts so Z1–Z3 are consistent and a prospect/engagement always gets the same shape of blueprint.

The five required artifacts (every Z must have all five)

A reference architecture is not valid until it contains all five sections:

1. Module bill-of-materials (BOM)

A table of which claude.md §4 assets compose the platform, each pinned (version once F11 lands, M3; until then, "current main"), with status (🟦/🟩/roadmap-Mx) and its role in the architecture. This is the spine — it must validate against the §4 catalog (every line resolves to a real asset).

2. Architecture diagram

A d2 diagram (ties to V2, the auto-diagram generator, roadmap M2b) of the deployed topology — subscription, network, identity, compute, data, CI/CD flow. Until V2 lands, an ASCII/mermaid sketch + a written topology description.

3. Compliance mapping

The Y7 coverage for this vertical's target framework(s) — which controls the BOM covers, honestly, with process controls excluded. Reuses the G2 frameworks mappings.

4. Cost estimate

A sandbox / illustrative monthly cost for the composed platform (Azure list prices, region-dependent), with the big-ticket items called out (AKS, Firewall, Defender plans, LAW ingestion). Marked illustrative — finalized per client's region + scale. Pairs with U1 (budget module).

5. Deploy guide

The order of operations to stand the platform up — which module applies first, what each depends on, and the runbook(s) that verify it. References the real docs/runbooks/test/* runbooks.

Composition rules

  • F-modules are the building blocks; B-modules are the per-client compositions; a Z is the named bundle. (Consistent with claude.md D20.)
  • A Z never invents new infrastructure — if a blueprint needs something not in §4, that's a gap to add to the catalog first, then reference.
  • Delta-documented: Z2/Z3 are expressed as Z1 + a delta (the additional controls), not as standalone re-listings — keeps them maintainable.
  • Honesty: shipped subset vs roadmap is explicit per BOM line.

Validation (the Z0 DoD, inherited by every Z)

  • All five artifacts present.
  • Every BOM line resolves to a real §4 asset (validate against the catalog).
  • Diagram renders (or sketch + topology prose present pre-V2).
  • Compliance mapping attached (Y7).
  • Cost estimate present (illustrative OK, marked).
  • Deploy guide references real runbooks.

DoD (Z0 itself)

  • Framework defines all 5 required artifacts. (Met.)
  • Z1 instantiates it fully with no missing section. (Met.)