ZAIXOS Engineering Platform — Execution Pipeline

Document type: Technical Specification
Version: 1.0 · Phase: 12-3
Status: Permanent technical authority
Related: EXECUTION_ARCHITECTURE.md · VALIDATION_ARCHITECTURE.md

---

Purpose

Describe every runtime pipeline with control flow, data flow, error handling, failure propagation, recovery, and stop conditions.

---

Pipeline catalog

ID	Pipeline	Trigger
PL-1	Developer Session	IDE open
PL-2	Phase Implementation	Architect prompt
PL-3	Validation	Pre-report / CI
PL-4	Architecture Review	Runtime Report submitted
PL-5	Freeze Decision	Post-acceptance
PL-6	Release Decision	Product release phase
PL-7	Platform Upgrade	Lock bump

---

PL-1 — Developer Session Pipeline

Control flow

IDE Start
  → Load .cursor/ mount (adapter)
  → Inject Constraints (rules)
  → Register Hooks (enforcement)
  → Load Context Providers (MCP templates)
  → Load Execution config (cli/environment.json)
  → Session Ready
  → [User/agent activity loop]
  → IDE End

Data flow

Stage	Input	Output
Mount load	platform.lock paths	Workspace file tree in IDE
Constraints	rules/*.mdc	Agent system context
Hooks	enforcement manifest	Allow/deny decisions
Context	MCP configs	External doc access
Execution	cli.json	Shell policy

Error handling

Error	Behavior
Missing mount	Session warn; validation fail on next run
Hook script error	Fail closed — block action
MCP unavailable	Degraded context; procedure must cite local docs

Stop conditions

• User closes IDE
• Critical hook failure on protected action

---

PL-2 — Phase Implementation Pipeline

Control flow

Architect Phase Prompt
  ↓
Workflow Resolution (EXECUTION_ARCHITECTURE)
  ↓
FOR each workflow step:
    Procedure Resolution
        ↓
    [Optional] Delegate Resolution
        ↓
    Execute in IDE (Constraints active)
        ↓
    Hook checks on mutations
  ↓
Scope Complete signal (Developer)
  ↓
Validation Pipeline (PL-3)
  ↓
Runtime Report Generation
  ↓
Submit to Architect

Data flow

Stage	Data
Prompt	Phase ID, scope, constraints, workflow ID
Workflow	Ordered procedure IDs
Procedure	SKILL.md instructions, inputs from prompt
Delegate	Agent markdown, readonly flags
Output	Code/docs changes, Format A/B report

Error handling

Failure	Propagation	Recovery
Procedure ambiguity	Stop step; Developer asks Architect	Clarify prompt
Hook block	Stop action; message to Developer	Fix approach or request exception (Architect)
Validation fail	Stop pipeline before report	Fix artifacts
Delegate overrun	Hook or manual stop	Re-scope delegate

Stop conditions

• Validation fail (hard)
• Architect rejects mid-phase (return to Procedure)
• Developer marks phase blocked

---

PL-3 — Validation Pipeline

See VALIDATION_ARCHITECTURE.md.

Control flow (condensed)

Trigger → Layer 0 → … → Layer 5 → [Layer 6 product] → Report

Failure propagation

• Any layer FAIL → pipeline status FAIL → block merge/release
• WARN → block release branch only

Recovery

• Fix root cause → re-run from failed layer
• Never disable failClosed on release

Stop conditions

• First FAIL when failClosed true
• All layers PASS → continue to Report

---

PL-4 — Architecture Review Pipeline

Control flow

Runtime Report received
  ↓
Architect loads RESPONSE_TEMPLATE
  ↓
Section 1 Architecture Review
  ↓
Section 2 ERP Runtime Validation (verify PL-3 evidence)
  ↓
Section 3 Acceptance Status
  ↓
Section 4 Decision (Accept | Reject | Conditional)
  ↓
Sections 5–9 Actions, Workflow, Freeze, Release, Git
  ↓
Publish review to Developer

Data flow

Input	Output
Format A/B report	Nine-section review
ValidationReport	Section 2 citation
Product architecture docs	Section 1 findings

Error handling

Issue	Behavior
Missing report section	Reject — request resubmit
Validation not green	Reject until PL-3 pass
Scope creep detected	Conditional or Reject

Stop conditions

• Decision = Reject → return to PL-2
• Decision = Accept → PL-5 eligible

---

PL-5 — Freeze Decision Pipeline

Control flow

Acceptance = Accept
  ↓
Architect sets Freeze Status in review
  ↓
Developer reads GIT_FREEZE_PROCEDURE
  ↓
Developer executes Git operations (only human Developer)
  ↓
Product baseline tag (product repo)

Stop conditions

• Acceptance not Accept → freeze forbidden
• Validation regression → freeze blocked

Platform note

Product freeze ≠ Platform v1.0 GA (Phase 12-9).

---

PL-6 — Release Decision Pipeline

Control flow

Freeze complete (if required)
  ↓
Product release checklist
  ↓
Deploy/tag product semver
  ↓
Update product release docs

Platform involvement: verify platform.lock unchanged or intentionally bumped with validation.

---

PL-7 — Platform Upgrade Pipeline

Control flow

Architect approves upgrade target
  ↓
Read CHANGELOG + migration guide
  ↓
composer update platform package
  ↓
Rematerialize adapter
  ↓
Update platform.lock
  ↓
PL-3 Validation full
  ↓
Architect review (MAJOR mandatory)
  ↓
Merge

Rollback

Revert lock + composer → rematerialize → PL-3

---

Master pipeline (end-to-end)

Developer Session (PL-1)
    ↓
Phase Implementation (PL-2)
    ↓
Validation (PL-3)
    ↓
Runtime Report
    ↓
Architecture Review (PL-4)
    ↓
Acceptance
    ↓
Freeze Decision (PL-5)
    ↓
Release Decision (PL-6)
    ↓
[Scheduled] Platform Upgrade (PL-7)

---

Cross-pipeline data artifacts

Artifact	Producer	Consumer
Materialized workspace	Materialization	PL-1, PL-2
ValidationReport	PL-3	PL-4, Format B
Runtime Report	Developer	PL-4
RESPONSE_TEMPLATE	Architect	Developer, PL-5
platform.lock	Install/upgrade	All pipelines

---

Execution Pipeline v1.0 — Phase 12-3.