ZAIXOS Engineering Platform — Value Proposition
Document type: Product Definition
Version: 1.0 · Phase: 12-2
Status: Permanent product authority
Nature: Engineering benefits — not marketing claims
Core Question
Why adopt ZEP instead of building an internal engineering workflow?
Because building and maintaining a cross-product, cross-IDE, AI-governed engineering system is a platform product, not a side project. ZEP amortizes that cost across products and encodes lessons from ERP v1.0 / EOS already proven in Dental Clinic ROS.
Primary Value
Deterministic, portable AI-assisted engineering with versioned authority.
| Benefit | Mechanism | Measurable indicator |
|---|---|---|
| No governance drift | Single platform source; products pin version | Identical contract schemas across repos at same pin |
| IDE portability | Runtime Contracts + adapters | Adapter swap without rewriting product architecture |
| Architectural enforcement | Platform + product integrity tests | % passing validation before merge |
| Onboarding repeatability | Developer guide + lock file + materialized adapter | Time to first green validation (see SUCCESS_METRICS.md) |
| Phase traceability | Format A/B reports + RESPONSE_TEMPLATE | Every merged phase has linked acceptance artifact |
Secondary Value
| Benefit | Description |
|---|---|
| Reduced duplicate documentation | ERP/EOS not copied per product repo |
| Clear escalation paths | Platform defect vs product defect vs adapter gap |
| Extension model | Customize without forking core |
| Semver clarity | Public API changes explicit; Internal/experimental labeled |
| Historical continuity | ERP v1.0 baseline preserved in platform 1.x semantics |
Long-Term Value
| Benefit | Horizon |
|---|---|
| Multi-adapter ecosystem | Same product pin, different IDE adapters |
| Org-scale extensions | Shared ZAIXOS extensions across products |
| Faster new product bootstrap | New vertical inherits engineering discipline day one |
| Lower architect cognitive load | Standard phase prompts and validation vocabulary |
| Audit-ready engineering evidence | Phase reports + validation logs (enterprise future) |
Build vs Adopt Analysis
| Build internally | Adopt ZEP |
|---|---|
| Reinvent phase model, reports, templates | Inherit EOS-derived methodology |
| Ad-hoc Cursor rules per repo | Certified adapter + contracts |
| Unclear ownership when AI misbehaves | Boundary matrix + enforcement hooks |
| Each product forks "ERP folder" | .zaixos/platform.lock |
| No semver for "engineering API" | PLATFORM_PUBLIC_API.md |
| Validation tests duplicated | Shared platform integrity suite |
Break-even heuristic: If a team would spend >2 engineer-months maintaining AI governance artifacts per product per year, ZEP adoption reduces net cost for multi-product or long-lived products.
Value by Persona
| Persona | Primary value received |
|---|---|
| Solo / startup developer | Skip building governance; focus on domain |
| Product architect | Standard acceptance workflow; fewer ambiguous AI outcomes |
| Platform team | One release train; not N embedded ERP copies |
| AI-native team | Contracts + enforcement without reinventing hooks/skills |
| Enterprise (future) | Version policy + metrics across portfolio |
Intentionally Not Promised (Honest Scope)
ZEP does not guarantee:
- Faster feature delivery (only more predictable engineering process)
- Fewer bugs in business logic (platform validates engineering structure, not domain correctness)
- Replacement of code review or QA
- Automatic compliance with jurisdiction healthcare or other product regulations (product Compliance module remains separate)
Measurable Engineering Benefits (Summary)
| Metric category | Expected direction after adoption |
|---|---|
| Onboarding time | Decrease vs bespoke ERP copy |
| Validation pass rate | Increase after initial migration |
| Platform upgrade duration | Bounded by semver migration guide |
| Architecture test failures caught pre-merge | Increase (fail closed) |
| Duplicate governance doc lines across repos | Decrease toward zero |
| Adapter migration effort | Bounded by contract stability (contracts@1 frozen) |
See SUCCESS_METRICS.md for KPI definitions.
Value Proposition v1.0 — Phase 12-2.