gtm/z/ — Z-Series Reference Architectures

Workstream: [GTM] / [B] / [A]  |  Ownership: [SO→CO]  |  Owner: Sagar

"Here's the exact platform we deploy for companies like you." Each Z is a named, documented composition of the existing module library (F/B/H/D/C series) for a vertical — a bill-of-materials + architecture diagram + compliance mapping + cost estimate + deploy guide. Both a sales accelerator (prospects buy outcomes faster when they see the blueprint) and a delivery accelerator (an engagement starts from a known-good composition, not a blank page).

---

Files

ID	Asset	File	Status
Z0	Reference-architecture framework	Z0-framework.md	✅ drafted
Z1	SaaS Startup Reference Platform	Z1-saas-reference-platform.md	✅ drafted (sales-doc form; full deploy = shipped Baseline)
Z2	FinTech Reference Platform	Z2-fintech-reference-platform.md	✅ drafted (delta vs Z1; full deploy tracks M2b/M4)
Z3	Healthcare Reference Platform	Z3-healthcare-reference-platform.md	✅ drafted (delta vs Z1; full deploy tracks M4)

The relationship to the F-series

Z0 is to the Z-blueprints what F0 (modules/_contracts/) is to the F-modules: it sets the pattern so Z1–Z3 are consistent. The document/diagram form is buildable now from shipped modules; the fully-deployable + advanced-tier variants track the modules they reference (flagged inline with their milestone).

Honesty rule

Every BOM line is a real claude.md §4 asset. Assets not yet shipped are flagged (roadmap — Mx). The sales-doc form of a Z is valid now; "fully deployable today" is claimed only for the shipped subset. Nidhi reviews compliance mappings.