One platform underneath. A different rulebook for every industry.

Domains differ at the business level: a trading desk and a commerce catalog share almost nothing. Yet every team that builds an AI system for its own domain rebuilds the same governed stack: orchestration, governance, observability, audit. Different choices on approvals, audit trails, and escalation leave those systems incompatible. Domain packs end that rebuilding. Synedrix OS solves the shared layer once, so each pack can focus on what is genuinely specific to its industry.

Concretely: a bank's trading desk needs a policy check on every order before it reaches the market; a retailer's catalog needs price-change approvals that can run for days. Same need for governance, different shape: two rulebooks on one platform, and neither team rebuilds the governance underneath.

A domain pack contributes seven things: a domain entity model, a domain event catalog conforming to the shared event envelope, specialised agents, tool adapters, domain policies and approval thresholds, a domain workflow library and playbooks, and an analytics vocabulary of KPIs and metrics. None of it touches orchestration, governance, memory, or observability directly. Those stay in the OS, where every domain pack shares them, so a domain pack extends Synedrix OS and stays compatible with everything else that runs on it.

Business functions are enabled by reusable domain packs, not mapped to them one-to-one. Order Operations, for example, might combine capabilities from the Commerce, Ops, and Finance domain packs, plus a company-specific business instance extension for its own escalation workflow. One organisational function can draw on several domain packs at once, and no domain pack belongs exclusively to one function.

None of this touches what the OS itself already handles. An agent's authority boundary, how an approval routes to a human, how an audit trail gets written: those work the same way whether the domain pack behind them is Trading or Finance. What changes from pack to pack is the vocabulary and the workflow; the machinery underneath stays exactly the same.

Four domain packs are named in the roadmap today: Trading, Commerce, Ops, and Finance. Trading has a published v2.0.0 specification. Commerce, Ops, and Finance are registered domain scopes with defined one-line boundaries; their full pack specifications are not published yet.

Deploying Synedrix OS for a specific business means configuring a business instance: the OS, plus one or more domain packs, plus tenant configuration, with nothing forked or rewritten along the way. Secrets, approval thresholds, and any detail specific to one customer live at this level, not inside the pack itself, which is what lets the same Synedrix Trading pack run for two different trading desks without either one touching the other's configuration.

A regulated bank running Synedrix Trading air-gapped and a fast-moving retailer running Synedrix Commerce in the cloud are both business instances of the same kind of pack, configured for entirely different environments and risk appetites.