Knowledge Portal · engineering documentation

Skip to content

ZAIXOS Engineering Platform — Extraction Sequence

Document type: Extraction Planning Specification
Version: 1.0 · Phase: 12-4
Status: Permanent execution authority


Purpose

Define the exact extraction order — what moves first, what moves later, what never moves — and dependencies between waves.


Extraction dependency graph

Wave 0: Planning docs (12-4) ──► complete

Wave 1: Platform governance docs (docs/platform/)

Wave 2: Contracts + runtime specification prose

Wave 3: Methodology + templates (docs/development/ subset)

Wave 4: Manifests + defaults (docs/development/*-manifest.md → runtime/manifests/)

Wave 5: Adapter workspace (.cursor/ → adapters/cursor-adapter-v1/workspace/)

Wave 6: Validation suite (tests → validation/)

Wave 7: Config JSON schemas (schemas/config/)

Wave 8: Developer docs consolidation (ERP_DEVELOPER_GUIDE → docs/developer-guide.md)

Consumer: 12-7 Composer + .zaixos/ + materialization

Sunset: 12-9 remove embedded duplicates

Rule: No wave N+1 starts until wave N validation checkpoint passes (see VALIDATION_PLAN.md).


Wave 1 — Platform governance (FIRST)

Phase: 12-6 (first extraction commit)

Source (Dental Clinic)Destination (platform repo)
docs/platform/PLATFORM_*.mdcore/constitution/, core/boundaries/ (organized)
docs/platform/adr/docs/platform/adr/
docs/platform/product/docs/product/ (platform product definition)
docs/platform/technical/docs/technical/
docs/platform/planning/docs/planning/

Why first: Establishes repo authority chain before movable runtime assets.

Validation: Doc link check; no content change vs source SHA.


Wave 2 — Contracts and runtime specification

Phase: 12-6

SourceDestination
contracts/runtime-contracts.mdcontracts/runtime-contracts.md (rename canonical)
runtime/specification/engineering-runtime-platform.mdruntime/specification/engineering-runtime-platform.md
runtime/components/phase-11-4-runtime-procedures-workflows-specification.mdruntime/components/ (split per component)
Historical phase-10/11 specsruntime/specification/archive/ (read-only reference)

Validation: ContractComplianceTest (after Wave 6); obligation text byte-compare @ contracts@1.


Wave 3 — Methodology and templates

Phase: 12-6

SourceDestination
core/methodology/DEVELOPMENT_WORKFLOW.mdcore/methodology/DEVELOPMENT_WORKFLOW.md
core/methodology/RESPONSE_TEMPLATE.mdcore/methodology/RESPONSE_TEMPLATE.md
core/methodology/GIT_FREEZE_PROCEDURE.mdcore/methodology/GIT_FREEZE_PROCEDURE.md
core/methodology/CONTEXT_FILE_POLICY.mdcore/methodology/CONTEXT_FILE_POLICY.md
templates/templates/
templates/prompts/templates/prompts/

Validation: EOS report format tests; template section counts unchanged.


Wave 4 — Manifests and defaults

Phase: 12-6

SourceDestination
runtime/manifests/defaults/procedures-manifest.mdruntime/manifests/defaults/procedures-manifest.md
runtime/manifests/defaults/workflows-catalog.mdruntime/manifests/defaults/workflows-catalog.md
runtime/manifests/defaults/delegation-manifest.mdruntime/manifests/defaults/delegation-manifest.md
runtime/manifests/defaults/enforcement-manifest.mdruntime/manifests/defaults/enforcement-manifest.md
runtime/manifests/defaults/context-providers-manifest.mdruntime/manifests/defaults/context-providers-manifest.md
runtime/manifests/defaults/execution-manifest.mdruntime/manifests/defaults/execution-manifest.md
Manifest schemas (derived from specs)runtime/manifests/schemas/

Validation: ManifestParityTest counts match ErpIntegritySupport constants.


Wave 5 — Adapter workspace (LATE — after manifests)

Phase: 12-6

SourceDestination
.cursor/ (entire tree)adapters/cursor-adapter-v1/workspace/
adapters/cursor-adapter-v1/profile.mdadapters/cursor-adapter-v1/profile.md
adapters/cursor-adapter-v1/manifest.jsonadapters/cursor-adapter-v1/manifest.json

Why after manifests: Adapter metadata references manifest paths — must exist in platform repo first.

Validation: AdapterWorkspaceTest; checksum recorded for 1.0.0.


Wave 6 — Validation suite

Phase: 12-6

SourceDestination
tests/Architecture/EngineeringRuntimePlatformIntegrityTest.phpvalidation/tests/
tests/Architecture/EngineeringOperatingSystemIntegrityTest.phpvalidation/tests/ (merge or split per scaffold)
tests/Architecture/Support/ErpIntegritySupport.phpvalidation/src/Support/
tests/Architecture/Support/EosIntegritySupport.phpvalidation/src/Support/ (path constants updated)
tests/Architecture/GovernanceDocumentationTest.phpSplit: platform-owned portions → validation; product portions stay

Validation: Full suite green in platform repo CI with fixture product layout.


Wave 7 — Config schemas

Phase: 12-6

SourceDestination
PLATFORM_CONFIGURATION_REFERENCE.mdschemas/config/*.json (generated from spec in 12-5 scaffold)
Example configsschemas/config/examples/

Validation: ConfigSchemaTest against examples.


Wave 8 — Developer guide consolidation

Phase: 12-6

SourceDestination
docs/developer-guide.mddocs/developer-guide.md (merged + updated paths)
docs/runtime-validation.mddocs/runtime-validation.md
docs/acceptance-checklist.mddocs/acceptance-checklist.md
docs/development/ENGINEERING_INDEX.mdRedirect content in developer-guide; index deprecated at 12-9

What moves LATER (Phase 12-7 — consumer, not extraction)

AssetAction
.zaixos/platform.ymlCreated in product repo (not extracted)
.zaixos/platform.lockCreated at consumer pin
.zaixos/extensions/manifest.ymlCreated empty registry
composer.json requireAdded to product

What NEVER moves

AssetReasonOwner
app/Modules/**Product domainD-R
docs/architecture/**Product constitutionD-R
docs/company/**Company governanceCompany
tests/Architecture/ModuleBoundaryTest.phpProduct modulesD-R
Domain feature testsProductD-R
Filament / Blade / routesApplicationD-R
AGENTS.md body (product modules)Product contextD-R
PostgreSQL migrations (clinic)Product dataD-R
.envEnvironmentD-R

What is REMOVED (Phase 12-9 — not moved)

AssetAction
Embedded docs/development/ ERP authority (post-cutover)Delete after parity; keep stub README.md pointer
Duplicate .cursor/ authoritative copyReplace with materialized mount only
Product-hosted EosIntegritySupport path to docs/development/Replaced by vendor validation paths

Forbidden extraction shortcuts

ShortcutWhy forbidden
Extract adapter before contractsMetadata dependency
Extract validation before adapterParity tests need workspace
Skip dual-runRollback risk
Move product modules "temporarily"Boundary violation
Edit contract text during copycontracts@1 freeze

Extraction Sequence v1.0 — Phase 12-4.

ZAIXOS Knowledge Portal — public engineering docs at /docs · Staff operations at /admin