Consolidated Canonical Reference

Status: Unified canonical master · Date: October 2026
Bundles: Principles · Taxonomy · Layers · Responsibility Matrix · Workflow Contract · Event Taxonomy · Tech Stack · Orchestration & Runtime · Memory Fabric · Interoperability · Vision · Deployment Model · Observability Metrics · Human/Agent Organisational Model · Mini Reachy Dev Assistant Domain Pack

This document consolidates all Synedrix OS canonical artifacts into a single unified reference. Each underlying canonical file remains maintained separately and is the source of truth for its section. This master is a read-through index plus executive synthesis.

0. About this document link

0.1 Purpose link

Provide one coherent, end-to-end view of Synedrix OS for architects, engineers, governance stakeholders, and operators. Individual canonical documents remain the per-domain sources of truth.

0.2 Constituent canonical documents link

1. Positioning link

Synedrix OS is the governed operating layer for agentic business systems. It coordinates specialised agents across workflows, tools and data while preserving human control, policy enforcement and operational trust.

Synedrix OS is also a reusable operating substrate on which domain packs run. It is open source and self-hostable, capable of running entirely within a customer’s own infrastructure including with local model inference.

The platform’s durable value is orchestration quality — coordinating specialised agents across multi-turn, multi-domain business workflows while maintaining human control, policy enforcement, and operational trust.

2. Core Principles (synthesis) link

1. Bounded autonomy — explicit authority boundaries; no blank cheques.
2. Orchestration is the center of gravity — coordination quality is the durable value.
3. Specialised agents over mega-agents — narrow, testable, governable roles.
4. Governance before execution — policy, approvals, audits enforced centrally.
5. Shared context with scoped access — least-privilege by default.
6. Humans stay above the automation layer — human oversight, not exclusion.
7. Explainability and audit by design — what, why, and under whose authority.
8. Event-driven execution — events trigger workflows as first-class citizens.
9. One substrate, many domains — domain-agnostic at the core.
10. Trust is the real product — the ultimate output of the platform.
11. Open by default, sovereign by design — open source, self-hostable, three canonical deployment modes.
12. Deterministic idempotency, explicit state — every side effect is idempotent or explicitly reconciled; all state is declared and recoverable.

Principle clusters link

Full definitions in Synedrix OS - Core Principles.

3. Canonical Taxonomy link

• Synedrix OS — governed multi-agent operating system, domain-agnostic at its core; agents are its primary actor type.
• Domain pack — modular business-domain capability package (Trading, Commerce, Ops, Finance, Art, Mini Reachy Dev Assistant — all equivalent).
• Business instance — deployed runtime = OS + one or more domain packs + tenant config + deployment mode declaration.
• Agent — scoped software actor with mission, authority boundary, contracts, memory scope, escalation path.
• Workflow — orchestrated sequence producing a business outcome.
• Capability — reusable unit of business function.
• Deployment mode — cloud-connected | self-hosted-hybrid | air-gapped.
• Business Instance Extension (BIE) — customer-specific, non-reusable customization registered inside a single business instance; a governed overlay within Layer 12, not a new layer.
• Capability Module — reusable, independently versioned, licensable sub-package of a domain pack, entitled per business instance; the opposite of a BIE.

Agent families link

Memory tiers link

Memory has two orthogonal axes: the tier is what kind of memory a record is, the substrate is the store it is written to. Neither may be inferred from the other. Full model in Memory Fabric Spec §3.

Rule of inclusion: if reusable across domains → OS; if domain-specific → domain pack; if threshold/credential/env config → business instance.

Full taxonomy in Synedrix OS - Taxonomy & Platform Spec.

4. Architecture Layers link

A Business Instance Extension (BIE) is content within Layer 12, not a thirteenth layer — the layer count stays twelve. See §3 and ADR-OS-005.

Full definitions in Synedrix OS - Layer Taxonomy Table.

5. Responsibility Split (summary) link

Full capability-by-capability matrix in Synedrix OS - Responsibility Matrix.

6. OS Agent Summary (12 agents) link

OS core agents (Layers 3–10) link

Key constraints:

• os-agt-008 (Audit and Lineage) is strictly read-only — must never appear in any agent’s tools_allowed list.
• os-agt-010 (Memory Curator) is the only agent permitted to commit durable memory; every other agent proposes.
• os-agt-012 (Memory Access Broker) is on the path of every recall and every write proposal, and never sees memory content itself.

Full agent contracts in Synedrix OS - Agent Registry.

7. Naming Conventions link

Layer codes link

Identifier patterns link

• Agent ID: {layer}-{archetype}-{capability-slug}-{seq} — e.g., os-ctl-orchestrator-001, trd-ctl-risk-manager-001
• Workflow ID: WF-{LAYER}-{FUNCTION-SLUG}-{SEQ} — e.g., WF-OS-ORCHESTRATION-001, WF-TRD-RISK-MANAGER-VETO-001
• n8n display name: [{LAYER}] {Layer tag} · {Business name} — e.g., [TRD] L5 · Risk Manager VETO

Full authority in Synedrix OS — Naming Convention Spec.

8. Tech Stack link

Every component is open source and self-hostable except Hookdeck (the inbound Event Gateway), a proprietary managed-cloud-only service with no self-hosted deployment — see Tech Stack §2 and the Hookdeck platform reference. Hookdeck Outpost, its egress counterpart, is a separate open-source (Apache 2.0) codebase. The Hookdeck exception is accepted (ADR-OS-013) and makes it Mode 3’s single declared external dependency. Local inference (Ollama/vLLM) is conditional — required in air-gapped mode and optional otherwise.

Full tech stack in Synedrix OS - Platform Architecture & Tech Stack. Orchestration vs runtime split in Orchestration & Runtime Strategy.

9. Workflow Contract (summary) link

Every workflow declares (16 required fields): workflow_id, name, domain, purpose, trigger_type, trigger_source, input_contract, validation_rules, agent_roles, tool_dependencies, side_effects, approval_requirements, output_contract, idempotency_strategy, retry_policy, error_policy, observability_signals, security_scope, version.

Full spec in Synedrix OS - Workflow Contract Spec.

10a. Mini Reachy Dev Assistant Domain Pack (executive summary) link

Synedrix Mini Reachy Dev Assistant is a single-owner domain pack embodied in a Mini Reachy robot: work-in-progress observability across every repository the owner tracks, an advisor over two knowledge bases, EN/IT/ES voice, and approval-gated screen/IDE action-taking. It composes on OS Layers 11 and 12 only — it does not depend on the withdrawn Layers 13/14, and it owns its own voice loop and Reachy Mini integration end to end.

What Mini Reachy Dev Assistant owns link

• Polling tracked repositories (local git + GitHub API) and delivering WIP digests and reminders
• A dual-knowledge-base advisor: recall against the existing os-agt-009 OS knowledge base (reused, not re-ingested) plus a pack-owned Agentic AI corpus
• Reachy Mini gesture/expression embodiment, gated by policy approval for any command outside the registered mapping table
• Voice session transport and turn management in English, Italian, and Spanish
• Execute-authority, HITL-gated screen/IDE action-taking on the owner’s behalf — no action executes without a recorded approval

Mini Reachy Dev Assistant agents (8 agents, 4 swarms) link

Mini Reachy Dev Assistant canonical workflows (7 contracts) link

Full contracts in Synedrix Mini Reachy Dev Assistant Workflow Contracts.

11. Invariants link

• Synedrix OS remains domain-agnostic at its core.
• Domain packs cannot bypass OS governance or observability layers.
• No agent writes to production systems without policy-aware orchestration.
• Every workflow is observable end-to-end.
• Every agent has explicit authority boundaries and at least one escalation path.
• No MCP or A2A protocol interaction bypasses governance.
• os-agt-008 (Audit and Lineage) is strictly read-only — must never appear in any agent’s tools_allowed.
• The agent registry is append-only at runtime.
• No memory record crosses a tier boundary without a governed memory.record.promoted event carrying its correlation_id and causation_id. Session-scoped working memory is TTL-bound and is never promoted to a durable tier without one.
• Memory recall is an authorized tool call, never ambient context injection.
• Only os-agt-010 (Memory Curator) commits durable memory; every other agent proposes.
• Erasure leaves a tombstone; lineage in graph memory survives the erasure of content.
• Supabase PG17 is write-authoritative for every audit-bearing memory tier; Qdrant, Neo4j and the LangGraph store are projections.
• All three deployment modes are first-class — no mode reduces platform capability.
• Air-gapped business instances must not contain cloud model URIs (platform validation error).
• Every component in the stack is open source and self-hostable.

12. Versioning policy link

• Canonical documents carry their own vX.Y versions.
• Breaking taxonomy or envelope changes → major version bump.
• Additive changes (new events, new fields, new rules) → minor version bump.
• This master consolidated reference is re-issued whenever two or more canonical documents change concurrently.
• Agent and workflow identifiers are stable — once registered, they never change. Deprecated items are marked; their sequence numbers are permanently retired.

13. Document map link

14. Versioning link

• Master document version: 3.9
• Status: Consolidated canonical reference
• Supersedes: v3.8
• Date: October 2026

Related Documents link

Core Principles and Vision link

• Synedrix OS - Core Principles — The 12 governing principles.
• Synedrix OS - Agentic Enterprise Manifesto Outline — Platform vision.
• Synedrix OS - Technical Platform Thesis — Architectural thesis.

Architecture and Taxonomy link

• Synedrix OS - Taxonomy & Platform Spec — Canonical taxonomy and packaging model.
• Synedrix OS - Layer Taxonomy Table — Authoritative definitions for the twelve canonical layers.
• Synedrix OS — Naming Convention Spec — Single authoritative reference for all machine identifiers; runtime-engine vocabulary.
• Synedrix OS - Responsibility Matrix — Capability-by-capability ownership split.
• Synedrix OS ADR-OS-005 — Business Instance Extension and Capability Module — Decision to extend Layer 12 with a governed overlay rather than add a thirteenth layer, and to adopt explicit domain_pack_version pinning.

Agent Specifications link

• Synedrix OS - Agent Spec — Full agent anatomy; adds the runtime_engine field.
• Synedrix OS - Agent Registry Spec — Registry schema.
• Synedrix OS - Agent Registry — 13 OS agent definitions.
• Synedrix OS - Agent Runtime Policy Spec — Runtime policy; runtime_engine and the governance bridge.
• Synedrix OS - Agent Evaluation Spec — Evaluation dimensions and promotion gates.

Orchestration and Runtime link

• Synedrix OS ADR-OS-001 — Agent Runtime Split — Decision to adopt LangGraph (Layer 4) and reject LangSmith.
• Synedrix OS Orchestration & Runtime Strategy — n8n↔LangGraph boundary and governance bridge.
• Synedrix OS n8n Implementation Guide — n8n orchestration + simple agents (Layer 3); invocation audit writes.
• Synedrix OS LangGraph Runtime Implementation Guide — LangGraph agent runtime (Layer 4).

Platform Telemetry and Observability link

• Synedrix OS Observability Metrics Spec — OS-canonical metric families.

Workflow and Event Standards link

• Synedrix OS - Workflow Contract Spec — Workflow contract standard.
• Synedrix OS - Event Taxonomy Standard — 15-field event envelope.

Tech Stack and Deployment link

• Synedrix OS - Platform Architecture & Tech Stack — Platform stack including LangGraph (Layer 4).
• Synedrix OS - Deployment Model Spec — Three deployment modes.
• Synedrix OS - Interoperability & Protocol Strategy — MCP and A2A; n8n↔LangGraph boundary.

Responsibility and Human/Agent Organisational Model link

• Synedrix OS — AI-Native Org Chart — Maps the twelve OS agents to a domain-agnostic business-function archetype, derives six OS-level human control roles from declared escalation paths, and traces five governed flows.
• Synedrix OS ADR-OS-015 — AI-Native Organisational Model — Decision (Accepted) behind the org-chart document: the accountability/execution separation, the four-plane projection, and the deferred os-agt-009 interface role.

Art Domain Pack link

• Synedrix Art Domain Pack — Art domain pack (Creative Storytelling Studio).

Mini Reachy Dev Assistant Domain Pack link

• Synedrix Mini Reachy Dev Assistant Domain Pack — Domain pack contract.
• Synedrix Mini Reachy Dev Assistant Agent Registry — 8 agent contracts.
• Synedrix Mini Reachy Dev Assistant Workflow Contracts — 7 workflow contracts.
• Synedrix Mini Reachy Dev Assistant Event Catalog — 14 events.

Domain Pack Template and Vocabulary link

• Synedrix OS - Domain Pack Template — Domain pack authoring template.
• Synedrix OS — Vocabulary — Canonical glossary.
• DOCS.md — Index of all documents in this repository.

Synedrix OS · September 2026