Tip: select any text on this page to bring up the Ask tooltip and question the Synedrix OS assistant about it.
What Domain Pack is
The Domain Pack layer is where Synedrix OS stops being domain-agnostic. Everything below it (orchestration, agent runtime, registry, tools, memory, events, governance, observability) is reusable across any business domain. A domain pack injects the domain-specific entities, workflows, agents, tools, policies, and KPIs that make the platform do something for one business: Trading, Commerce, Ops, Finance.
A domain pack composes on the OS through defined contracts rather than extending it. It contributes agents to the shared registry using the same schema every OS agent uses, contributes workflows that satisfy the same Workflow Contract Spec, and contributes events conforming to the same shared envelope, never redefining OS principles or abstractions.
What it owns, and what it does not
Every layer in the architecture has a non-overlapping responsibility. The boundary is as much a part of the design as the capability.
Owns
- Domain-specific entities and the business logic that governs their lifecycle
- Domain events, conforming to the shared event envelope
- Specialist agents scoped to the domain
- Domain policies, approval points, and veto logic
- KPI vocabulary for the domain
- Tool mappings: domain-specific adapter implementations
Does not own
- Shared OS primitives
- → Synedrix OS
- The adapter framework itself
- → Tool Abstraction Layer
- Actual secrets and credentials
- → Business Instance Layer
- Thresholds, approver mappings, tenant-specific overrides
- → Business Instance Layer
- Memory tier taxonomy and the memory lifecycle mechanism
- → Memory & Data Layer
Interfaces with
The other layers this one exchanges work, state, or decisions with, and why.
Agent Registry
domain agents are contributed to the shared registry using the same schema OS agents use.
Orchestration
domain workflows execute through the same Workflow Contract Spec as every other workflow.
Governance & Controls
every domain agent's escalation path must terminate at an OS control agent.
Business Instance
a domain pack declares what an instance may configure; the instance supplies the actual values.
How Synedrix OS implements it
The Synedrix OS - Domain Pack Template is the concrete authoring spec. It requires a domain pack to define, in order: domain purpose and scope; domain entities; external systems and adapters (OS owns the framework, the pack owns the implementation, the instance owns credentials); domain agents on the OS agent model; domain workflows using the full Workflow Contract Spec; a domain event catalog; domain policy and approvals; KPIs and evaluation; data and memory usage; and an instance configuration boundary.
Domain-pack agents carry real, enforced invariants: agent_id prefixed with the domain pack's own code (com-agt-001, trd-ctl-master-orchestrator-001), owner set to the pack rather than synedrix-os, family: domain or customer only, an escalation_path terminating at an OS control agent, and approval_required.policy: true for financial, regulated-messaging, or irreversible-write actions.
The Trading domain pack is a concrete, real example with a published v2.0 specification: it owns its own signal generation pipeline, multi-phase consensus voting, and risk-veto enforcement, while still escalating into the same OS control agents as any other pack.
OS agents at this layer
Layer principles that apply
- Rule of inclusion: anything genuinely reusable across domains does not belong in a domain pack, no matter how convenient; anything that's only a threshold, credential, or tenant value belongs one layer down, in Business Instance.
Domain Pack questions, answered
Short, citable answers drawn from this page.
What is the Domain Pack layer in Synedrix OS?
Domain Pack is layer 11 of the twelve-layer Synedrix OS architecture, in the "Domain and runtime config" group. Where the OS stops being domain-agnostic, and one business's logic begins.
What does the Domain Pack layer own?
The Domain Pack layer owns: Domain-specific entities and the business logic that governs their lifecycle; Domain events, conforming to the shared event envelope; Specialist agents scoped to the domain; Domain policies, approval points, and veto logic; KPI vocabulary for the domain; Tool mappings: domain-specific adapter implementations.
What does the Domain Pack layer not own?
The Domain Pack layer does not own: Shared OS primitives (owned by Synedrix OS); The adapter framework itself (owned by Tool Abstraction Layer); Actual secrets and credentials (owned by Business Instance Layer); Thresholds, approver mappings, tenant-specific overrides (owned by Business Instance Layer); Memory tier taxonomy and the memory lifecycle mechanism (owned by Memory & Data Layer).
The full reference page, with every canonical specification this layer touches, lives in the documentation repository, which is private while the platform is being built.