

Latest post
The authority boundary: what agents can and cannot do
An agent's authority belongs in a versioned record, not its prompt. See how Synedrix OS uses recommend, approve and execute scopes to bound what agents do.
ReadTip: select any text on this page to bring up the Ask tooltip and question the Synedrix OS assistant about it.
The root is the Greek synedrion (συνέδριον), meaning a council or assembly. It combines syn- (“together”) with hedra (“seat”) to describe a collaborative body whose members pull up a chair to solve problems together rather than acting alone. Synedrix brings that exact spirit of shared purpose and unified action into the digital space.
A council works because its members have different jobs and one shared purpose. Synedrix OS is built the same way. Each agent has a narrow role and a defined limit on what it may do. An orchestrator routes work between them, and they draw on shared context in which each agent sees only what its role needs, instead of every agent working from its own copy of the facts.
The people who run the business set the rules the council works under. They approve the decisions that carry real risk, and they can read the record of what was decided and why. It is a council whose authority comes from rules that people set.
A table is only useful when someone is accountable for what is agreed at it.
The -ix ending follows a long habit in operating-system names and nods to Unix. It marks the word as the name of a system that other things run on, and the next section explains why that is the right claim.
An operating system does not do a user's work. It gives every program the same coordination, permissions, shared memory and record-keeping, so each program can concentrate on its own job. Synedrix OS plays that role for agents: it coordinates work between them, limits what each one may touch, holds the shared context and keeps the audit trail. A domain pack, which carries one industry's rules and workflows, then runs on top without rebuilding any of that.
That shared layer is the product, and “OS” is the shortest honest name for it. Synedrix names the idea, and Synedrix OS names the product: the governed operating layer for agentic business systems.
Synedrix OS is in active development. The architecture is complete and documented, and the platform is being built.
The twelve principles show how each rule becomes a mechanism in the architecture, and the About page tells the story of the problem behind it.


Latest post
An agent's authority belongs in a versioned record, not its prompt. See how Synedrix OS uses recommend, approve and execute scopes to bound what agents do.
Read