Federated from workspace ·
Company·zaixos-company/docs/strategy/PRODUCT_PORTFOLIO.mdDo not edit canonical truth here — update the source repo, then re-runnpm run docs:sync.
ZAIXOS Product Portfolio
Document type: Strategy — Product Portfolio
Version: 1.0
Date: 2026-06-30
Milestone: M-08 — Portfolio Charter Ratification
Status: Accepted
Classification: Internal — Strategic Authority
Owner: Chief Product Officer (accountable) · Chief Executive Officer (co-owner) · Knowledge Architect (maintainer)
Authority: COMPANY_CONSTITUTION.md · ZAIXOS_FINAL_EXECUTIVE_DECISIONS.md OD-06 · WORKSPACE_BASELINE.md
Ratified: 2026-06-30 · PORTFOLIO_RATIFICATION.md
Purpose
Define which products exist in the ZAIXOS portfolio — charters, lifecycle status, admission and retirement rules, and product classification — as the gating authority for product authority repositories.
No product authority repository may exist without an Approved entry in this document. This portfolio superseded bootstrapped "Pending charter" placeholders (OD-06, Constitution Art. XXIII).
Portfolio Authority
| Field | Definition |
|---|---|
| Authority repository | zaixos-company — this document is the sole portfolio charter authority |
| Binding scope | Product admission, classification, lifecycle states, numbering, and retirement |
| Supremacy | Subordinate to COMPANY_CONSTITUTION.md on governance; supreme on portfolio questions within company strategy |
| SSOT | Products cite this document — they do not host authoritative portfolio copies (CP-19) |
| Registry role | zaixos-registry indexes portfolio metadata when Registered (M-10) — never replaces this document |
Portfolio Ownership
| Role | Responsibility |
|---|---|
| Chief Product Officer | Portfolio authority; charter proposals; lifecycle reviews |
| Chief Executive Officer | Class A approval for new product lines and retirement |
| Chief Technology Officer | Platform readiness assessment for admission |
| Architecture Council | Structural review for new product repos (Class B) |
| Repository Architect | Verify Approved portfolio entry before repo creation or registry registration |
| Knowledge Architect | Version control, cross-reference integrity, ratification records |
| Product leads | Maintain product-scoped domain docs — not portfolio authority |
Authority Chain
Company (identity, constitution, strategy)
↓ constrains
Portfolio (this document — product admission & lifecycle)
↓ authorizes
Platforms (ZEP · UBP · future design-system · future ai-platform)
↓ consumed by
Products (one authority repo per Approved product)
↓ indexed by
Registry (metadata, consumer map — when operational)
↓ delivered to
Customers (clinic operators · product end users)Downward citation only. Products never define company strategy or portfolio rules (WORKSPACE_BASELINE dependency rules).
Product Classification Definitions
| Class | Definition | Today (2026-06-30) |
|---|---|---|
| Official Product | Product with Approved portfolio charter and ratified workspace baseline repository | PRD-001 only |
| Consumer Product | Official Product that pins ZEP and serves as engineering reuse proof surface | PRD-001 — Consumer #1 |
| Production Product | Official Product with operational engineering deployment — domain app, releases, validation in CI | PRD-001 |
| Experimental Product | Time-boxed product exploration inside an existing charter or explicit experimental flag — not a separate portfolio line | None |
| Future Product | Discussed or simulated in planning — not Approved, no authority repo, not Registered | All products other than PRD-001 |
Distinctions:
- Official Product ≠ the company. Company authority is
zaixos-company(OD-06, Constitution Art. II). - Consumer Product is an engineering relationship to ZEP — not a separate product SKU.
- Production Product describes engineering operational state — not commercial revenue. PRD-001 is pre-revenue commercially (OD-02).
- Future Product may appear in blueprint simulations — simulations are not authorization (Constitution Art. XXIV).
Product Numbering Policy
| Rule | Detail |
|---|---|
| Format | PRD-{nnn} — three-digit zero-padded stable identifier |
| Assignment | Sequential at Class A portfolio admission — never reused after retirement |
| Immutability | Product ID persists across renames; repository rename requires registry update when operational |
| Next ID | PRD-002 reserved only upon Class A admission — not assigned today |
| Platform IDs | Platforms use separate catalog IDs (e.g. PL-002 design-system, PL-003 ai-platform) — not PRD IDs |
Product Naming Rules
| Element | Rule |
|---|---|
| Product ID | PRD-{nnn} — portfolio registry key |
| Official name | Full descriptive name in English — e.g. Dental Clinic Revenue Operating System |
| Repository name | Kebab-case or workspace ratified name — must match WORKSPACE_BASELINE.md for baseline products |
| Consumer label | Consumer #{n} — order of ZEP consumer proof (Consumer #1 = first pinned consumer) |
| Public product name | Brand architecture when Accepted (M-09) — subordinate to this charter for scope |
Product Lifecycle
Aligned with Constitution Art. XVI and COMPANY_OPERATING_MODEL.md §7:
| State | Meaning | Repo allowed | Public commitment |
|---|---|---|---|
| Future | Not Approved — planning only | No | No |
| Deferred | Named in strategy discussion — not Approved | No | No |
| Charter Approved | Approved portfolio entry — repo authorized | Yes | Internal only until Active |
| Active (engineering) | Operational development or deployment | Yes | Engineering evidence only |
| Active (commercial) | Production customer or commercial deployment evidenced | Yes | Requires customer evidence |
| Mature | Stable maintenance — portfolio review | Yes | As documented |
| Deprecated | Wind-down — successor documented | Archive path | Class A announcement |
Promotion rules:
- Future → Charter Approved: Class A decision + this document amended + Architecture Council + domain alignment.
- Charter Approved → Active (engineering): Repo exists; ZEP pin; architecture tests pass.
- Active (engineering) → Active (commercial): Named production customer or deployment evidence (OD-02).
- Any → Deprecated: Class A + registry pointer update when operational + migration plan.
Product #2 lifecycle: Forbidden until M-24 factory certification and M-25 authorization (CP-26, Constitution Art. XXIV).
Product Admission Criteria
All criteria must pass before a new PRD-{nnn} row is Added as Charter Approved:
| # | Criterion | Authority |
|---|---|---|
| 1 | Class A executive decision with written record | Constitution Art. V |
| 2 | Approved portfolio amendment to this document | CPO + CEO |
| 3 | Domain strategy alignment | DOMAIN_STRATEGY.md when Accepted |
| 4 | Architecture Council review | Class B structural gate |
| 5 | Platform readiness — ZEP pin path; extraction debt addressed for Product #2+ | M-12–M-14 before Product #2 |
| 6 | Factory gate — Product #2 requires M-24 (9/9 gates) | CP-26 |
| 7 | Registry registration workflow when A0 operational (M-10) | Registry policy |
| 8 | Strengthen-the-next evidence — new product must reduce future product cost | CP-15 |
| 9 | One repo per product — no merge into company or ZEP | CP-13 |
Default state for candidates not yet admitted: Future Product — Authorized (workspace planning) · Not Created · Not Registered · Not Approved.
Product Retirement Policy
| Step | Requirement |
|---|---|
| 1 | Class A executive decision — CEO + executive council |
| 2 | Successor product or explicit "no successor" documented |
| 3 | Customer migration plan if Active (commercial) customers exist |
| 4 | Portfolio row → Deprecated with date and pointer |
| 5 | Registry catalog updated when operational |
| 6 | SSOT pointers updated — no orphan authority |
| 7 | Domain data retention per legal and product policy — counsel where required |
Retirement does not delete release history or constitutional evidence of what was shipped.
Platform Relationship
Each Approved product consumes platforms — it does not redefine them:
| Platform | PRD-001 consumption | Extraction note |
|---|---|---|
| ZEP | Pinned @1.0.0 via .zaixos/platform.lock | Engineering governance reuse proven |
| UBP | Frozen modules @ v4.2-public-experience-platform chain inside monolith | Not standalone SKU (OD-08) |
| Design System | Not attached — layout infra in product v5.3 | M-16 extraction planned |
| AI Platform | Partial — ANPA modules in product | M-18 extraction planned |
Platform-before-duplication: third similar capability elevates to platform; second triggers extraction plan (Constitution Art. IX).
Official Portfolio Registry
Approved products: 1
Future products Approved: 0
PRD-001 — Dental Clinic Revenue Operating System
| Field | Value |
|---|---|
| Product ID | PRD-001 |
| Official name | Dental Clinic Revenue Operating System |
| Classification | Official Product · Consumer #1 · Production Product |
| Portfolio status | Portfolio Approved · Charter Approved |
| Repository | Dental Clinic Revenue Operating System — ratified baseline repo #4 (WORKSPACE_BASELINE.md) |
| Workspace ratification | Official Product — WORKSPACE_RATIFICATION_REPORT.md |
| Lifecycle | Charter Approved · Active (engineering) · commercial pre-revenue (OD-02) |
| Domain | Vertical revenue operating system — private dental clinic operators worldwide; global commercial markets |
| Designed buyer | Private dental clinic owners and administrative staff (OD-02) |
| Charter summary | Modular monolith encoding clinic lead capture, CRM, compliance, public presence, clinic template system, and SaaS-ready tenancy — first proof vertical for ZEP reuse and factory path |
| Platform pins | ZEP 1.0.0 · UBP frozen modules in-product · future design-system and ai-platform not attached |
| ZEP consumer | Consumer #1 — .zaixos/platform.lock; ERP validation; 601 architecture tests |
| Engineering evidence | Production domain operational; release pipeline; materialized Cursor adapter |
| Commercial evidence | Pre-revenue — no named production customer recorded |
| Accountable | Chief Product Officer |
| Approved | 2026-06-30 — OD-06 substance; M-08 portfolio formalization · PORTFOLIO_RATIFICATION.md |
| Not the company | Corporate identity remains zaixos-company (OD-06) |
Modules (product authority — not portfolio scope detail): Clinic, CRM, Leads, Marketing, Tracking, Compliance, ClinicTemplateSystem, Shared — per product repo registration.
Future Products
No future product holds Approved portfolio status today.
| Default state | Meaning |
|---|---|
| Authorized (planning) | May be discussed in blueprint or domain strategy simulations |
| Not Created | No authority repository |
| Not Registered | No registry catalog entry (0 Registered today) |
| Not Approved | No row in Official Portfolio Registry above |
Explicit prohibitions (Constitution Art. VIII, XXIV):
- PRD-002+ repositories are unauthorized until admission criteria pass and this document is amended.
- Product #2 execution forbidden until M-24 then M-25.
- Horizontal CRM as standalone product (PRD-004 class) remains Deferred until explicit charter (OD-09, CP-14).
- Blueprint Product #10/#20 simulations are not portfolio entries.
Adding a future product requires Class A decision + Accepted amendment to this document — not bootstrap placeholders or chat approval.
Product Creation Gate
Dependency order (Constitution Art. XXIV, EXECUTION_CONTRACT):
1. Class A executive decision
2. Approved entry in this portfolio (Accepted amendment)
3. Domain strategy alignment
4. Architecture Council + Repository Architect review
5. Repository exists or is ratified in workspace baseline (Class A for fifth+ repo)
6. ZEP pin + materialize adapter + ERP validation
7. Registry registration when M-10 operational
8. SSOT citation model — no duplicate portfolio in product repoCross References
| Document | Relationship |
|---|---|
| COMPANY_CONSTITUTION.md | Supreme governance — Articles X, XVI, XXIV |
| COMPANY_OPERATING_MODEL.md | Operating flows — §2, §7 |
| COMPANY_MISSION.md | Mission scope and boundaries |
| DOMAIN_STRATEGY.md | Domain approval for admission |
| WORKSPACE_BASELINE.md | Four-repo ratified baseline |
| ../../../zaixos-registry/docs/architecture/REPOSITORY_CLASSIFICATION.md | Repo type rules |
| ../../../zaixos-registry/docs/architecture/SINGLE_SOURCE_OF_TRUTH.md | SSOT policy |
Version History
| Version | Date | Change |
|---|---|---|
| 0.1 | 2026-06-30 | Bootstrap — structure only; PRD-001 "Pending charter" placeholder |
| 1.0 | 2026-06-30 | M-08 — Accepted portfolio charter · PRD-001 Portfolio Approved |
Authoritative product portfolio. One Approved product today. Future products require admission — not invention.