ZAIXOS Engineering Platform — Product Scope
Document type: Product Definition
Version: 1.0 · Phase: 12-2
Status: Permanent product authority
Rule: If an item is not listed in Included, assume Not Included unless explicitly in Future Candidate.
Included (Inside ZEP Product Boundary)
Platform Core & Governance
- Platform Constitution, Boundaries, Public API, Extension Model, Versioning Policy
- Platform ADRs and Platform Index
- EOS-derived methodology (phases, freeze policy references, context rules)
- RESPONSE_TEMPLATE and phase report templates
- Product definition documents (this set)
Runtime Abstraction
- Runtime specification (abstract ERP semantics)
- Runtime Contract definitions and JSON schemas (
contracts@1) - Manifest schemas and default manifest inventories
- Runtime component specifications (Constraints, Procedures, Workflows, Delegation, Enforcement, Context, Execution)
Adapters
- Adapter profiles, workspace templates, metadata manifests
- Capability gap registers
- Certification criteria (documentation-level in v1)
Validation
- Platform integrity test suite (PHPUnit or equivalent)
- Contract conformance checks against materialized adapter workspace
- Validation documentation (checklists, runtime validation guides)
Knowledge & Templates
- Platform developer guide
- Implementation report templates (Format A/B)
- Phase prompt templates
- Extension registry specification
Product Integration Surfaces
.zaixos/canonical namespace specification.zaixos/platform.lockpin semantics.zaixos/extensions/manifest.ymlextension registry- Materialization rules (
.zaixos/→.cursor/for Cursor Adapter v1)
Not Included (Outside ZEP — Product or Other Systems Own)
| Item | Owner |
|---|---|
Application business modules (app/Modules/*) | Product (D-R) |
| Product architecture constitution | Product (D-R) |
| Filament resources, Blade views, domain models | Product (D-R) |
| Product-specific PHPUnit/feature tests (domain) | Product (D-R) |
| PostgreSQL schema for clinic/marketing/leads etc. | Product (D-R) |
| CI/CD pipeline hosting (GitHub Actions runners, etc.) | Product / org infra |
| Production deployment, hosting, DNS | Product / ops |
| IDE vendor binaries and licenses | IDE vendor (D-T) |
| Company Constitution content | Company |
| Healthcare compliance domain rules (jurisdiction packs) | Product Compliance module |
Never Included (Permanent Non-Goals)
ZEP will never become:
| Non-goal | Rationale |
|---|---|
| Application runtime or ORM | Use Laravel/Symfony/etc. |
| Business domain modules | Product scope |
| Customer-facing SaaS for clinic operations | Revenue product, not engineering platform |
| Replacement for Git or GitHub | VCS remains external |
| General-purpose low-code builder (core product) | Violates platform/product separation |
| IDE vendor | Adapter consumer only |
| Hosting platform / PaaS | Out of scope permanently |
| Secret store or credential manager | Org infra |
| Authoritative copy of product data | Clinic-scoped data stays in product DB |
Future Candidate (May Enter Scope Later — Not v1 GA Commitment)
| Candidate | Classification when adopted | Notes |
|---|---|---|
| Platform CLI | Public (Experimental → Public) | Install, validate, materialize commands |
| Platform SDK | Public (Experimental) | Programmatic integration for tooling |
| Git repository template | Secondary bootstrap | One-time scaffold only |
| Git submodule distribution | Secondary/transitional | ADR-005 already notes transitional path |
| Additional certified adapters (Claude Code, etc.) | Adapter layer | Requires certification process |
| SaaS product generator | Major product line | Not v1; separate ADR required |
| Extension marketplace | Platform services | curation, signing, discovery |
| Hosted validation service | Optional enterprise | Runs same tests remotely |
| Non-PHP product bootstrap | Platform expansion | Requires non-Composer primary strategy |
| Team / org policy bundles | Extension or edition feature | Central rule packs |
Future Candidate ≠ committed roadmap item. See PRODUCT_ROADMAP.md.
Scope Boundary Diagram
┌────────────────────────────────────────── ZEP INCLUDED ──────────────────────────────────────────┐
│ Constitution · Methodology · Contracts · Adapters · Validation · Templates · Developer docs │
└──────────────────────────────────────────────────────────────────────────────────────────────────┘
│
consumes │ never owns
▼
┌──────────────────────── PRODUCT NOT INCLUDED ────────────────────────┐
│ Domain modules · Product constitution · App UI · Product CI wiring │
└──────────────────────────────────────────────────────────────────────┘
┌──────────────────────── NEVER INCLUDED ──────────────────────────────┐
│ App runtime · Business SaaS · Hosting · Git replacement · IDE vendor │
└──────────────────────────────────────────────────────────────────────┘Ambiguity Resolution
| Question | Answer |
|---|---|
| Is ERP part of ZEP? | Yes — as Platform Runtime semantics; ERP name is legacy |
Is .cursor/ part of ZEP? | Adapter materialization — owned by adapter maintainer, generated from platform |
| Is Dental Clinic repo part of ZEP? | No — product; embeds platform until migration complete |
| Are architecture tests in product repo part of ZEP? | Platform owns test definitions; product invokes them in CI |
| Can products patch platform files in vendor? | No — extensions only; patch = fork or extension ADR |
Product Scope v1.0 — Phase 12-2.