Architecture

Status: Canonical section
Last updated: 2026-07-05

---

Purpose

System design for the ZAIXOS ecosystem — structure, boundaries, dependencies, and lifecycles. Implementation detail remains in platform/product repos; this section is the navigable map.

---

Section map

Document	Topic
overall-architecture.md	Ecosystem overview
repository-map.md	All repositories
dependency-graph.md	Platform ↔ product dependencies
platform-architecture.md	Platform layer model
product-architecture.md	Product composition
module-architecture.md	Bounded contexts
ddd-boundaries.md	Context boundaries
package-relationships.md	Composer packages
contracts-flow.md	Contract invocation flow
dto-flow.md	DTO movement
events-architecture.md	Event-driven integration
closed-loop-architecture.md	AI quality loop
lifecycle-diagrams.md	State and lifecycle
decision-flow.md	When to write an ADR

---

Master diagram

flowchart TB
    subgraph L0["Governance"]
        ADR[ADR / Constitution]
    end
    subgraph L1["PL-001 Engineering Platform"]
        ZEP[ZEP Core + Contracts]
    end
    subgraph L2["Platforms"]
        PL002[PL-002 Design]
        PL003[PL-003 AI Runtime]
        PL004[PL-004 Intelligence]
        PL005[PL-005 Knowledge]
        PL006[PL-006 Observability]
    end
    subgraph L3["Products"]
        PRD000[PRD-000]
        PRD001[PRD-001]
    end
    subgraph L4["Registry"]
        REG[RP-002 Registry]
    end
    L0 --> L1 --> L2 --> L3
    REG -.-> L1
    REG -.-> L2
    REG -.-> L3

---

Deep technical authority

Document	Path
Technical Architecture	technical/TECHNICAL_ARCHITECTURE.md
Dependency Model	technical/DEPENDENCY_MODEL.md
Package Architecture	technical/PACKAGE_ARCHITECTURE.md
Execution Pipeline	technical/EXECUTION_PIPELINE.md

---

Related

• ENGINEERING/README.md
• PLATFORMS/README.md
• ADR/README.md

Breadcrumbs: Home → Architecture