Job-first framing: IXO Matrix is how you run multi-party data rooms—funders, implementers, verifiers, communities, services, and agents in encrypted rooms with shared context. Yjs CRDTs and live shared documents are part of how cooperation stays attached to state, not a pile of attachments. Setup details live in SDK and API reference pages.
Funders, operators, verifiers, and agents rarely fail on “more chat.” They fail when context, evidence, and decisions scatter across channels. IXO Matrix is the secure communication and shared-surface layer so those actors align before, during, and after state-changing actions on IXO Protocol and Qi workflows.
Architecture role
IXO Matrix is the data and communication layer in the IXO architecture. It supports domain collaboration, evidence exchange, and stateful workflows with encryption and explicit access controls.
Position in the stack
IXO Matrix supports encrypted rooms, event-based communication, and verifiable room history across users and services.
Federated topology
IXO Matrix uses federated Matrix-compatible server topology, so participants can exchange events across trusted homeservers while retaining room-level controls.
Integration surfaces
- IXO MultiClient SDK (
@ixo/impactxclient-sdk) for cross-service integration - IXO Matrix Client SDK (
@ixo/matrixclient-sdk) for Matrix-specific operations - room and state bot services for automation and policy-driven updates
- Model Context Protocol (MCP) integrations where available
CRDT shared state in Matrix for human and AI teams
IXO uses Matrix and Yjs (commonly referenced as y.js in the ecosystem) CRDTs to turn documentation into shared state, so human and AI teams collaborate on the same live source of truth instead of passing files and chat snippets back and forth.
At IXO, CRDT-based shared state lives inside Matrix rooms, with Yjs as the synchronization layer, so documentation behaves as a live, multi-actor workspace rather than a static file.
This matters because documentation here is not only written once and published. It is shaped continuously by product teams, domain experts, operators, and AI agents working at the same time. The system needs concurrent edits, preserved intent, and one evolving source of truth without locking, silent overwrites, or fragile version handoffs.
What this means in practice
Each documentation space, page, or structured work surface can be bound to a dedicated Matrix room. That room carries communication context, access control, event history, and the encrypted collaboration channel. Inside the room, Yjs holds the actual shared document state as a CRDT.
The result is that all participants—human or AI—operate on the same live state.
Not message-passing workflows such as “I sent you suggested edits,” “here is my copied version,” or “please merge these manually.” Instead, everyone sees and updates the same document state; concurrent changes merge automatically; no central locking is required; offline edits can reconcile safely; and AI agents can act as first-class collaborators on the same state as people.
Why CRDTs fit IXO
Conflict-free Replicated Data Types (CRDTs) are built for distributed collaboration: many parties edit shared content independently and still converge on the same result. For IXO, that matters in four ways:
- Real shared state, not file passing — Traditional documentation often defaults to file ownership and turn-taking. CRDTs support a multiplayer model where the document is a shared state surface. That aligns with how coordination works across IXO and Qi: cooperation happens over shared state.
- Symmetric human and AI collaboration — Agents are not limited to external tools that only emit text in a side panel. They can inspect, propose, annotate, structure, and update the same document state humans use: humans edit sections directly; agents enrich structure, summarize, cross-link, validate, or suggest improvements—all against one canonical state. That is a stronger basis than chat-only copy-paste flows.
- Distributed and resilient by default — IXO targets sovereign, federated, multi-party settings. Matrix supplies a decentralized collaboration substrate; CRDTs provide synchronization without a single centralized editor session—important across organizations, devices, and trust boundaries.
- Living operational knowledge — Much of this documentation is operational, not only descriptive. Specifications, policies, rubrics, flows, and implementation notes keep moving. CRDTs fit because the document stays live and synchronizing instead of being frozen into periodic versions only.
Architecture pattern
Think of the stack in three layers:
Matrix provides the collaboration fabric
- Secure room-based collaboration
- Federation across homeservers
- End-to-end encrypted communication
- Identity and membership context
- Event history and auditing hooks
- Integration with IXO governance and access control patterns
Yjs provides the shared state engine
- CRDT document structures
- Concurrent editing without manual collision resolution
- Automatic merge of independent changes
- Local-first editing
- Synchronization across participants and devices
IXO composes governed digital workspaces
On top of Matrix and Yjs, IXO can bind documents, flow pages, action blocks, structured metadata, agent participation, and governance rules—so the artifact is not only text but a governed shared state object inside a secure collaboration domain.
Why this matters for human and AI teams
Most AI tooling today is chat-first: the model sees a conversational slice of context and returns text; a human must decide how to apply it.
In this pattern, agents can work directly on shared state in the documentation workspace: read structure; spot missing sections; propose schema-aligned edits; attach evidence or rationale; keep terminology consistent; update linked references; prepare structured summaries for different audiences. Humans stay in control, but coordination tightens because both humans and agents mutate the same living object.
That shift—from message passing to stateful cooperation—matches the broader Qi model of human–AI cooperation over shared state.
Concept model
Encrypted collaboration spaces with explicit membership and permissions.
Event-driven communication between users, apps, and service actors.
Protected file sharing connected to room state and audit history.
Stateful workflows through room events and automation bots.
Typical use cases
Coordinate entity and project state with secure shared context.
Keep evidence and review conversations linked to verifiable events.
Exchange and process telemetry in governed data rooms.
Run cross-team workflows with encrypted communication channels.