Federated from workspace ·
Company·zaixos-company/PRD-000_PRODUCT_CHARTER.mdDo not edit canonical truth here — update the source repo, then re-runnpm run docs:sync.
PRD-000 Product Charter
Document type: Product Charter — Constitutional Foundation
Product ID: PRD-000
Official name: ZAIXOS Experience Platform
Version: 1.1
Date: 2026-07-01
Status: Proposed v1.1 — Architecture Council amendment applied · Pending Class A portfolio ratification
Classification: Internal — Product Authority
Owner: Chief Product Officer (accountable) · Chief Executive Officer (co-owner) · Chief Product Architect (co-owner)
Subordinate to: docs/company/COMPANY_CONSTITUTION.md · docs/strategy/PRODUCT_PORTFOLIO.md · COMPANY_FOUNDATION_FREEZE.md
Technical subordinate: PRD-000_PRODUCT_ARCHITECTURE.md · PRD-000_ENGINEERING_EXECUTION_PLAN.md
Predecessor milestone: M-17 Corporate Surface — COMPLETE (frozen; not modified by this charter)
Portfolio note: Filing this charter does not constitute portfolio admission. PRD-000 remains a planning identifier until Class A amendment to PRODUCT_PORTFOLIO.md and factory gates M-24 → M-25 are satisfied per Constitution Art. XXIV and CP-26.
This document defines why PRD-000 exists, what it owns as a product, who it serves, and how success is measured. It does not define implementation, sprints, module code, or platform internals.
1. Product vision
Why PRD-000 exists
M-17 delivered the Corporate Surface — a static, cite-only trust and evaluation layer at zaixos.com. That surface answers: Who is ZAIXOS? What is proven today? What is direction only?
PRD-000 exists because trust alone does not complete a commercial relationship. Prospects, customers, and partners need a primary interactive experience through which they discover intent, receive structured proposals, approve engagements, and maintain ongoing account relationships — with AI embedded in the workflow, not bolted on as a chat widget.
PRD-000 is the official ZAIXOS Experience Platform: the product that demonstrates what ZAIXOS can build when PL-001, PL-002, and PL-003 are consumed together under governed engineering discipline. It is intended to become Consumer #2 of the shared platform stack and the public interactive face of the company after M-17.
Primary question
What do you want to build — and how do we move from intent to a governed, reviewable engagement?
How PRD-000 differs from the Corporate Surface (M-17)
| Dimension | M-17 Corporate Surface | PRD-000 Experience Platform |
|---|---|---|
| Purpose | Trust, credibility, honest evaluation | Interactive commercial and customer experience |
| Nature | Static / SSR marketing surface — no product business logic | Dynamic application — sessions, CRM, proposals, portal |
| AI | Messaging about AI approach only | AI as primary interaction model inside governed workflows |
| Audience outcome | Orient and evaluate; route to Contact | Discover, qualify, propose, approve, deliver, retain |
| Authority | M17_CORPORATE_SURFACE_WORKBOOK.md v1.1 — COMPLETE · frozen | This charter + product architecture |
| Deploy today | Interim Astro site per MD-017_DEPLOY_VEHICLE_DECISION.md | Not authorized until portfolio + engineering gates pass |
| Relationship | Upstream credibility layer — links into PRD-000 when authorized | Downstream experience layer — does not replace or redesign M-17 IA |
| Evidence model | Trusted static information — cite-only summaries of authority and proof | Live operational experience — real production usage under §2 P-01 |
M-17 remains the permanent corporate credibility baseline — it provides trusted static information (who we are, what is proven today, what is direction only). PRD-000 provides the live operational experience through which ZAIXOS runs and demonstrates its commercial lifecycle. The surfaces are complementary, not redundant.
PRD-000 extends the apex domain with interactive and commercial capabilities (/solutions, discovery entry, pricing evaluate surfaces, knowledge, customer portal) per PRD-000_PRODUCT_ARCHITECTURE.md §12 — without changing M-17 core navigation or page inventory.
Strategic position
PRD-000 is not a marketing website. It is a vertical-agnostic company experience product that:
- Proves multi-platform consumption (ZEP + Design System + AI Platform) as Consumer #2.
- Delivers the A2 commercial motion (build & platform partnerships) as an AI-native product experience.
- Routes A1 vertical demand to PRD-001 when catalog fit matches — without duplicating PRD-001 domain.
- Makes ZAIXOS's AI architecture legible through use, not claims — preview-safe, human-accountable, contract-bound.
- Operates as the Living Showcase of ZAIXOS engineering philosophy — see §2 P-01.
2. Product principles
Constitutional principles binding all PRD-000 product decisions. They govern scope, AI strategy, success criteria, and long-term positioning. Implementation detail remains in PRD-000_PRODUCT_ARCHITECTURE.md.
P-01 — Living Showcase Principle
PRD-000 must be defined as the first production environment of ZAIXOS itself.
ZAIXOS is not only a vendor of AI-enabled business systems — it is the first production operator of the platforms and methodology it sells. The company, engineering process, Runtime, AI Platform, Design System, products, workflows, and future systems are built using the same governed engineering discipline offered to customers. PRD-000 is where that discipline becomes observable to the outside world.
| Rule | Requirement |
|---|---|
| Operational first | The company must operate its own commercial lifecycle through PRD-000 — discovery, qualification, proposal, approval, delivery coordination, and customer relationship for A2 partnerships and internal pipeline |
| Real usage | The platform continuously demonstrates real operational usage rather than marketing claims |
| Evidence priority | Evidence must come from real production operation whenever possible — platform pins, pipeline states, approval gates, workspace artifacts |
| Honest labeling | Capabilities must always be labeled honestly (Today vs Direction) per Brand P5 |
| No fiction | No fictional customers · no fake success stories · no demo-only marketing |
| Authority order | Operational evidence has higher authority than promotional content |
Living Showcase is an operational product principle. It is not:
- Marketing
- Documentation
- A blog
- A case study
- A demo environment
Knowledge center articles, M-17 cite-only summaries, and sales narratives may support evaluation — they do not substitute for Living Showcase proof inside PRD-000.
Governance (product): ZAIXOS internal commercial pipeline runs through PRD-000 — not parallel shadow systems presented as showcase. Synthetic or preview-labeled data is permitted only in explicit preview contexts (e.g. prototype preview stage). Evaluate surfaces that cite platform evidence must link to live operational state where possible.
3. Product mission
Business problem
Organizations evaluating ZAIXOS face two friction points that the Corporate Surface cannot resolve:
Evaluation friction. Build partners and enterprise prospects need structured discovery — requirements, scope boundaries, timeline and cost framing, and a reviewable proposal — not a contact form and email thread alone.
Relationship friction. After initial interest, there is no unified product surface for proposal review, approval, contract handoff, project visibility, and long-term customer self-service. Context fragments across email, documents, and ad hoc tools.
Mission statement
PRD-000 exists to convert qualified intent into governed commercial relationships — through AI-assisted discovery, reviewable proposals, and a durable customer workspace — while routing vertical product demand to portfolio-approved products and proving that ZAIXOS platforms compose into a credible company-scale experience.
Why it exists (company alignment)
| Company mandate | PRD-000 contribution |
|---|---|
| Encode operational knowledge in auditable software (COMPANY_MISSION.md) | Commercial discovery and delivery artifacts become structured, versioned product data |
| Strengthen-the-next product economics (CP-15) | Second consumer proof reduces cost of future products |
| Honest operator partnership (Brand P5) | Today vs direction labeling; human approval for binding commercial terms |
| AI in architecture, not hype (Brand P3) | Live demonstration of Layer 2 product AI — preview-safe, bounded |
| Pre-revenue honesty (PRODUCT_PORTFOLIO.md) | No implied customers, revenue, or factory autonomy |
PRD-000 does not replace company strategy, portfolio authority, or PRD-001 vertical operations.
4. Product scope — what belongs inside PRD-000
Scope is organized by capability domain. Implementation shape is defined in PRD-000_PRODUCT_ARCHITECTURE.md bounded contexts — this charter defines product ownership only.
4.1 Discovery & intelligence
| Capability | Product intent |
|---|---|
| AI Solution Architect | Guides prospects through structured problem framing aligned to catalog templates |
| Discovery Engine | Maintains session state, phases, and continuity from first visit through requirements assembly |
| Interactive Requirement Collection | Captures intent, constraints, integrations, and success criteria as structured artifacts |
| AI Consultant / AI Conversations | Multi-turn discovery dialogue — primary interaction surface for anonymous and authenticated users |
| Lead Qualification | Scores and routes intent: vertical product (A1) vs custom build (A2) vs defer |
4.2 Commercial generation
| Capability | Product intent |
|---|---|
| Proposal Generator | Produces interactive, versioned proposal drafts from discovery artifacts |
| Timeline Estimator | Frames delivery phases with explicit assumptions — not guaranteed dates without human review |
| Cost Estimator | Provides indicative pricing bands; enterprise/final pricing requires human approval (AD-007) |
| Prototype Preview | Preview-safe visualization of proposed solution shape — direction and scope communication, not production software |
| Proposal Approval | Customer and internal approval workflow with audit trail |
| Quotation & contract handoff | Formal priced quotations and counsel-reviewed contract envelope initiation |
4.3 Customer relationship
| Capability | Product intent |
|---|---|
| Customer Workspace | Post-close delivery space: milestones, deliverables, member access |
| Customer Portal | Authenticated self-service: proposals, account settings, workspace visibility |
| Customer Dashboard | Summary of active engagements, status, and next actions |
| Project Progress | Milestone and deliverable tracking with honest status labeling |
| Documents | Versioned commercial and delivery documents scoped to organization |
| Contracts | Contract records, signature status, integration with e-sign providers |
| Notifications | Transactional alerts for proposal, approval, and workspace events |
4.4 Company experience extensions (post-M17)
These capabilities extend zaixos.com — they are not M-17 pages:
| Surface | Product intent |
|---|---|
| Solutions evaluate | Template-oriented solution exploration for A2 |
| Technology evaluate | Platform consumption credibility for technical diligence |
| Pricing evaluate | Honest pricing posture — pre-revenue and approval-gated where required |
| Security evaluate | Security posture summary for diligence — cite evidence, not certifications without record |
| Knowledge center | Company-hosted articles and revision history |
| Public proposal share | Token-scoped read-only proposal links |
4.5 Internal operations
| Capability | Product intent |
|---|---|
| Staff CRM | Pipeline: accounts, leads, opportunities, activities, stage automation |
| Sales approval queues | Human gate for proposals, enterprise pricing, and non-standard terms |
| Administration | RBAC, catalog management, content moderation, analytics |
| Funnel analytics | Product-scoped events from visit through closed-won |
4.6 Platform consumption (product role, not redesign)
PRD-000 consumes platforms — it does not redefine them:
| Platform | Product consumption |
|---|---|
| PL-001 ZEP | Engineering governance, materialization, ERP validation, local dev |
| PL-002 Design System | Public and authenticated UI primitives, Filament theme |
| PL-003 AI Platform | Conversation, prompts, streaming, memory, context, agents, jobs — via product adapters only |
| PL-004 (future) | Planning intelligence stub — optional enrichment when registered |
5. Explicit exclusions — what does NOT belong inside PRD-000
Frozen or external ownership
| Exclusion | Owner | Rule |
|---|---|---|
| M-17 Corporate Surface pages and IA | M-17 workbook — COMPLETE | No redesign; PRD-000 links and extends only |
| Company constitution, portfolio, brand SSOT bodies | zaixos-company | Cite-only — never embedded in product repo |
| Registry inventory authority | zaixos-registry | Product registers when admitted — does not own catalog truth |
| Platform internals | PL-001 / PL-002 / PL-003 / PL-004 | Consume contracts — no fork, no redesign |
| PRD-001 vertical domain | PRD-001 | Clinic CRM, compliance modules, clinic tenancy — route, do not re-host |
| UBP frozen modules inside PRD-001 | PRD-001 monolith | Not duplicated in PRD-000 |
Product non-goals
| Exclusion | Rationale |
|---|---|
| Marketing website as primary identity | M-17 owns static trust layer; PRD-000 owns interactive experience |
| Horizontal CRM as standalone SKU | Portfolio-deferred (OD-09); CRM here serves company commercial motion only |
| Autonomous business execution | No AI-approved binding contracts, pricing, or legal terms without humans |
| AGI / autonomous executive claims | Brand prohibited claims; Constitution Art. XI |
| Factory Layer 3 marketing | L3 factory not marketable pre-M-24 (BRAND_MESSAGING.md) |
| Invented portfolio products | Catalog routes only to Approved products (today: PRD-001 only) |
| Direct LLM provider SDK usage outside AI adapters | Platform-first AI boundary |
| Public developer platform at initial GA | Post-GA scope per architecture |
| Real-time WebSocket discovery (initial GA) | SSE sufficient; WebSocket deferred |
| Medical/clinical operations | No clinical advice; regulated seriousness via product boundaries only |
Replacing zaixos-company as company authority | OD-06 — company ≠ product |
| Living Showcase substitutes | Marketing pages, documentation, blog posts, case studies, or demo-only environments do not satisfy §2 P-01 — operational product evidence required |
| Fictional showcase data | Fictional customers, fake success stories, or demo-only marketing presented as production proof — CP-21, Brand prohibited claims |
6. Product users
| User | Definition | Primary needs | Primary surfaces |
|---|---|---|---|
| Internal operator (ZAIXOS) | ZAIXOS as organization — first production tenant of PRD-000 | Run own commercial lifecycle on the same platforms sold to customers; maintain Living Showcase integrity | Staff CRM, discovery, proposals, workspace, approval queues |
| Prospect | Anonymous or identified visitor exploring build or partnership | Fast orientation, trustworthy discovery, clear next step | Discovery entry, AI conversation, evaluate pages |
| Customer | Authenticated organization member with active or closed commercial relationship | Proposal review, approvals, workspace visibility, support | Customer portal, dashboard, documents |
| Partner | Build & platform partner (A2) evaluating governed delivery | Evidence of ZEP discipline, scoped engagement path, diligence materials | Discovery, technology/security evaluate, proposals |
| Internal sales | Staff owning pipeline and commercial approval | CRM, proposal workflow, approval queues, send/share controls | Filament CRM, proposal administration |
| Engineering | ZAIXOS engineers supporting delivery | Workspace context, integration hooks, honest status — not public marketing | Internal views, workspace, integration refs |
| Executives | CPO, CEO, leadership reviewing pipeline and proof | Funnel integrity, consumer #2 proof, honest metrics | Analytics, dashboard summaries, approval queues |
Audience routing (inherited from brand — not reinvented):
- A1 — Product buyers: Catalog fit assessment → route to PRD-001 when rules match.
- A2 — Build & platform partners: Discovery → proposal → workspace on PRD-000.
Organization model: Customer-owned data scopes to Organization after identity establishment; anonymous discovery may exist before attachment with session migration on authentication. ZAIXOS operates as the first production organization tenant under §2 P-01.
7. Relationship diagram — layer responsibilities
┌─────────────────────────────────────────────────────────────────┐
│ COMPANY (zaixos-company) │
│ Constitution · Portfolio · Brand · Strategy · Legal framework│
│ Role: Supreme governance — no application deploy │
└────────────────────────────┬────────────────────────────────────┘
│ constrains (cite-only)
▼
┌─────────────────────────────────────────────────────────────────┐
│ CORPORATE SURFACE (M-17) — COMPLETE │
│ Static trust & evaluation @ zaixos.com (interim Astro deploy) │
│ Role: Who we are · trusted static information · honest direction │
│ Does NOT: sessions · CRM · discovery · proposals │
└────────────────────────────┬────────────────────────────────────┘
│ links / handoff when PRD-000 live
▼
┌─────────────────────────────────────────────────────────────────┐
│ PRD-000 — ZAIXOS EXPERIENCE PLATFORM │
│ Interactive commercial & customer product @ zaixos.com extensions│
│ Role: Live operational experience · discover · propose · deliver │
│ Consumer #2 target: PL-001 + PL-002 + PL-003 │
└────────────┬───────────────────────────────┬────────────────────┘
│ consumes │ routes vertical fit
▼ ▼
┌────────────────────────────┐ ┌────────────────────────────────┐
│ PL-001 Engineering (ZEP) │ │ PRD-001 Dental Clinic ROS │
│ PL-002 Design System │ │ Vertical revenue OS · A1 │
│ PL-003 AI Platform │ │ Consumer #1 · portfolio Approved│
│ PL-004 ZIP (future stub) │ └────────────────────────────────┘
│ Role: Shared frozen │ │
│ platforms — product │ ▼
│ adapters only │ ┌────────────────────────────────┐
└────────────────────────────┘ │ FUTURE PRODUCTS (PRD-002+) │
│ Not authorized until portfolio │
│ admission + factory path │
└────────────────────────────────┘Layer responsibility summary
| Layer | Responsibility | Must not |
|---|---|---|
| Company | Strategy, admission, brand truth, legal framework | Host product runtime |
| M-17 Corporate Surface | Trusted static information, portfolio honesty, evaluation routing | Run business logic, AI sessions, or operational showcase |
| PRD-000 | Live operational experience; full commercial and customer loop; Living Showcase (§2 P-01) | Redefine company strategy or M-17 IA |
| PL-001 / PL-002 / PL-003 | Shared engineering, UI, AI runtime | Contain product-specific commercial rules |
| PRD-001 | Clinic vertical operations end-to-end | Own company-wide discovery or A2 build motion |
| Future products | Additional vertical domains when admitted | Appear in catalog without portfolio row |
8. Customer journey
End-to-end journey PRD-000 must support. Each stage has explicit human accountability and preview-safe AI assistance where AI is involved.
First visit
│
▼
Conversation ─── AI-assisted discovery; intent capture; fail-closed form fallback
│
▼
Discovery ─── Structured requirements artifacts; catalog fit assessment (A1 vs A2)
│
▼
Prototype ─── Preview-safe scope visualization; labeled as proposal communication
│
▼
Proposal ─── Interactive draft; versioned; shareable via token link
│
▼
Approval ─── Customer review + internal sales/legal gates; enterprise pricing human-approved
│
▼
Project ─── Closed-won triggers workspace provisioning; milestones defined
│
▼
Portal ─── Authenticated self-service; documents, progress, support cases
│
▼
Long-term relationship ─── Retained workspace history; expansion discovery; catalog routing to productsJourney rules
| Stage | AI role | Human role |
|---|---|---|
| First visit → Conversation | Guide questions; assemble context | Brand honesty; no urgency manipulation |
| Discovery | Structure requirements; suggest catalog fit | Sales review for non-standard scope |
| Prototype | Generate preview artifacts | Customer interprets as directional, not delivered software |
| Proposal | Draft sections from discovery | Sales approval before customer send; AD-007 pricing gate |
| Approval | Notifications and checklist only | Customer sign-off; staff approval for non-standard terms |
| Project → Portal | Status summaries where implemented | Delivery team owns milestone truth |
| Long-term | Assist re-discovery in new sessions | Account ownership in CRM |
M-17 handoff: Corporate Surface CTAs route to PRD-000 discovery entry when live — Contact remains valid fallback until then.
PRD-001 handoff: When catalog fit rules match dental vertical A1 intent, journey routes to PRD-001 evaluation — no merge of product domains.
9. AI strategy
AI credibility in PRD-000 derives from the Living Showcase Principle (§2 P-01) — ZAIXOS operates its own discovery and commercial workflows on PL-003 under the same preview-safe, human-accountable constraints sold to customers. Interface novelty is not the proof; production usage under governance is the proof.
How AI is used
PRD-000 is the company's first product-native demonstration of Layer 2 AI (BRAND_MESSAGING.md) — workflow-embedded, contract-bound, and preview-safe.
| Use | Description |
|---|---|
| Discovery dialogue | Multi-turn conversation assembling requirements via PL-003 conversation + memory scoped to session |
| Solution framing | AI Solution Architect persona maps intent to catalog templates and scope boundaries |
| Artifact generation | Proposal sections, timeline bands, cost indicators — drafts for review, not binding output |
| Qualification | Structured signals for A1 product route vs A2 build motion |
| Portal assistance | Contextual help inside authenticated tasks — not a generic always-on chatbot |
All AI runtime flows through PL-003 via product adapters — no direct provider SDK in business contexts.
Why AI is the interface instead of traditional navigation
Traditional marketing navigation assumes the visitor already knows what to click. PRD-000's primary question — What do you want to build? — is conversation-native:
- Intent is unstructured at entry; dialogue reduces evaluation friction faster than static page trees alone.
- A2 partnerships require bespoke scope — forms alone cannot capture nuance without fatigue.
- Demonstrating AI architecture requires using it under the same constraints ZAIXOS sells: preview, approval, boundaries, fail-closed degradation.
- M-17 already provides static orientation; PRD-000 adds the interactive layer without duplicating brochure navigation as the primary model.
Traditional navigation remains for evaluate pages, knowledge, legal links, and wayfinding — AI leads entry and discovery, not every surface.
Boundaries (non-negotiable)
| Boundary | Rule |
|---|---|
| No AGI claims | AI assists defined workflows — not general intelligence marketing |
| No autonomous business | AI does not close deals, sign contracts, or finalize enterprise pricing |
| Preview-first | Generated commercial artifacts require review before customer commitment |
| Fail-closed | PL-003 unavailable → structured form fallback + contact path |
| Cost caps | Anonymous session budgets — no unbounded public AI spend |
| Legal | AI does not produce binding contract language without counsel/human review |
| Memory | Session-scoped by default; no training on customer artifacts without explicit future policy |
| Honesty | Partial Layer 2 implementation labeled where shipping status requires |
| L3 Factory | Not marketed from this product — pre-M-24 |
Primary interaction model (direction): Users interact with system intelligence inside the task — aligned with brand architecture commitment and honest shipping status.
10. Future roadmap
Roadmap phases are product capability horizons — not implementation schedules. Engineering sequencing lives in PRD-000_ENGINEERING_EXECUTION_PLAN.md.
Current (today)
| State | Meaning |
|---|---|
| M-17 COMPLETE | Corporate Surface live — frozen IA and content |
| PRD-000 planning | Architecture authority filed; this charter proposed |
| Portfolio | Not Approved — no product authority repo deploy |
| Factory | 7 / 9 gates — Product #2 forbidden until M-24 |
| Platforms | PL-001 @ 1.0.0 GA · PL-002 @ 1.0.0 · PL-003 @ 0.7.0 · PL-004 bootstrap only |
Near-term (first product horizons after authorization)
Gated by: Class A portfolio admission · M-24 factory certification · M-25 second consumer authorization · engineering bootstrap.
| Horizon | Capabilities |
|---|---|
| H1 — Discovery loop | Anonymous discovery session · AI conversation · requirements artifacts · CRM lead creation · fail-closed fallback |
| H2 — Commercial draft | Proposal generator · share links · internal sales approval · indicative timeline/cost bands |
| H3 — Customer identity | Organization model · magic-link auth · portal shell · proposal viewing |
| H4 — M-17 extension parity | In-product hosting of evaluate extensions without M-17 IA change · workbook §9 migration |
| H5 — Closed-won delivery | Workspace provisioning · milestones · basic document store |
First production outcome (architecture-aligned): A visitor completes Discovery and receives a reviewable proposal draft with CRM linkage.
Long-term (post-initial GA horizons)
| Horizon | Capabilities |
|---|---|
| Commercial maturity | Quotation, contract e-sign integration, enterprise approval workflows |
| Portal depth | Full customer dashboard, support cases, knowledge CMS |
| Catalog expansion | Route to additional portfolio products as Approved — never invented |
| Developer surface | External read-only catalog API (post-GA architecture scope) |
| PL-004 enrichment | ZIP planning adapter swap when platform registers |
| Analytics maturity | Full funnel instrumentation and executive reporting |
Explicitly not long-term promises: Autonomous factory, multiple unapproved products, AGI positioning, or revenue figures without evidence.
11. Success criteria
Measurable business and product outcomes — tracked honestly; pre-revenue baselines apply until commercial evidence exists.
Consumer proof (engineering)
| Metric | Target | Evidence source |
|---|---|---|
| Platform attachment | PL-001 + PL-002 + PL-003 pinned in product .zaixos/platform.lock | Consumer #2 parity with PRD-001 pattern |
| Architecture integrity | Zero boundary violations in CI architecture suite | ERP validation |
| Reuse measurement | ≥ 20–33% same-shape reuse vs PRD-001 greenfield (M-25 exit) | Factory repeatability gate |
| No doc embedding | Zero copied platform constitution bodies in product repo | SSOT audit |
Commercial experience (product)
| Metric | Target | Notes |
|---|---|---|
| Discovery completion rate | Baseline → improve | % sessions reaching requirements-complete state |
| Proposal draft generation | ≥ 1 reviewable draft per qualified discovery | First production outcome |
| Time-to-proposal-draft | Baseline → improve | Hours/days from session start to sales-reviewable draft |
| A1 routing accuracy | Baseline → improve | Correct PRD-001 route when dental vertical fit |
| Human approval compliance | 100% for enterprise pricing | AD-007 — zero auto-finalized enterprise quotes |
| Fail-closed integrity | 100% fallback availability | Form path when PL-003 degraded |
Customer relationship (product)
| Metric | Target | Notes |
|---|---|---|
| Proposal share engagement | Baseline → improve | Token link opens and customer actions |
| Portal activation | Baseline → improve | Authenticated orgs viewing proposals/workspace |
| Closed-won → workspace | 100% idempotent provisioning | Saga success on approved deals |
| Support case resolution SLA | Defined when operational | Not promised pre-GA |
Company proof (strategic)
| Metric | Target | Notes |
|---|---|---|
| Live demonstration | Prospects experience Layer 2 AI in product | Credible A2 diligence surface |
| Honesty audit pass | Zero prohibited claims in product UI | Brand compliance checklist |
| M-17 coexistence | M-17 IA unchanged; PRD-000 extensions only | Workbook §10 parity |
| Portfolio truth | UI reflects Approved products only | Today: PRD-001 only |
Showcase integrity (§2 P-01)
| Metric | Target | Notes |
|---|---|---|
| Internal pipeline in product | 100% of ZAIXOS commercial opportunities tracked in PRD-000 CRM | No parallel shadow pipeline presented as showcase |
| Operational evidence linkage | Evaluate surfaces cite live platform pins and operational state where possible | Evidence over adjectives |
| Showcase debt | Zero unlabeled capabilities shown without internal operational use | Quarterly Architecture Council review post-GA |
| Fiction-free showcase | Zero fictional customers, fake success stories, or demo-only marketing as production proof | Brand prohibited claims · CP-21 |
| Today vs direction compliance | 100% of partial capabilities labeled in product UI | Brand P5 |
Admission success (governance)
| Gate | Criterion |
|---|---|
| Charter Approved | Class A decision + portfolio row amended |
| Active (engineering) | Product repo + ZEP pin + architecture tests pass |
| Active (commercial) | Named production customer or deployment evidence per OD-02 |
| M-25 exit | Second consumer registered; repeatability gap closed |
12. Authority hierarchy (product)
| Priority | Document | Role |
|---|---|---|
| 1 | COMPANY_CONSTITUTION.md | Supreme governance |
| 2 | PRODUCT_PORTFOLIO.md | Admission and lifecycle |
| 3 | PRD-000_PRODUCT_CHARTER.md | This document — product constitutional foundation |
| 4 | PRD-000_PRODUCT_ARCHITECTURE.md | Technical architecture — how, bounded contexts, platform consumption |
| 5 | PRD-000_ENGINEERING_EXECUTION_PLAN.md | Engineering execution sequencing |
| 6 | Product repository docs | Implementation evidence |
Conflict resolution: Higher layer wins. This charter does not override portfolio or constitution. Technical architecture must not contradict this charter without charter amendment.
Naming alignment: Public and product identity name is ZAIXOS Experience Platform. Planning documents referencing ZAIXOS Company Platform refer to the same PRD-000 product — update public naming on charter ratification.
13. Ratification requirements
This charter becomes product constitutional authority only when all pass:
| # | Requirement | Authority |
|---|---|---|
| 1 | Class A executive decision | CEO + executive record |
| 2 | Approved portfolio amendment — PRD-000 row in PRODUCT_PORTFOLIO.md | CPO + CEO |
| 3 | M-24 factory certification (9/9 gates) | Factory readiness |
| 4 | M-25 Product #2 authorization | EXECUTION_MASTER_ROADMAP |
| 5 | Architecture Council review — charter ↔ architecture alignment | Class B — amendment applied v1.1 |
| 6 | Brand compliance review — no prohibited claims introduced | CMO |
| 7 | M-17 integrity confirmation — no IA redesign | CMO + CIA |
Until ratification: status remains Proposed; engineering bootstrap documents are planning artifacts only.
14. Document control
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-07-01 | Initial product charter — post-M17; Experience Platform identity |
| 1.1 | 2026-07-01 | Architecture Council amendment — §2 Product principles (P-01 Living Showcase); M-17 vs PRD-000 evidence model; Internal operator tenant; Showcase integrity metrics; cross-references |
| Field | Value |
|---|---|
| Supersedes | Ad hoc PRD-000 planning references without charter |
| Superseded by | Nothing below company/portfolio/constitution |
| Does not contain | Implementation, code, sprints, module trees, API specs, database design |
| Companion documents | Architecture v1.0 · Engineering execution plan · Bootstrap plan |
| Next review | At Class A portfolio ratification or material product scope change |
Citation name for downstream documents: PRD-000 Product Charter v1.1 → file PRD-000_PRODUCT_CHARTER.md
PRD-000 Product Charter v1.1 — Constitutional product foundation. M-17 complete. Living Showcase begins here.