Synixolis
Synixolis is the Synix term for the collective case: a multi-agent system where agents maintain shared state under explicit, revisable conventions.
Status: Conceptual model. The memory architecture is the first attempt at implementation.
Origin
Section titled “Origin”The Synix build system worked well for processing data that had already been generated — conversations, documents, transcripts. But a batch pipeline running on a timer cannot manage state that changes in real time or coordinate multiple agents writing to the same store.
The question behind the Synixolis model is simple: if multiple agents can write to persistent state, what governs how that shared state is maintained?
Core idea
Section titled “Core idea”The core proposal is that data, procedures, and conventions all live in the same store. Agents read the current procedures and conventions, act on the store, and leave an audit trail behind them.
The infrastructure layer is intentionally narrow: content-addressing, atomic writes, full-text search, and an append-only event log. Higher-level behaviors such as synthesis, decay, conflict resolution, and convention changes are handled through policies and procedures rather than a separate orchestration layer.
Governance
Section titled “Governance”The Synixolis model argues that multi-agent systems need governance, not just coordination. Without governance mechanisms, concurrent agents writing to shared state quickly collapse into conflicting updates, stale summaries, and unclear authority.
Evidence-based writes. A synthesis is a proposal backed by source references. Promotion to durable state requires corroboration or endorsement.
Ground truth preservation. Raw ingested data is retained as a reference baseline. When agents disagree about derived state, the source material remains available for re-evaluation.
Conflict resolution. When objects contradict, the process surfaces the conflict, records both positions, allows adjudication, and preserves the rationale. Invalidated objects are not deleted — they are marked with a pointer to the resolution.
Convention changes. The system’s own rules can change, but proposed changes require evidence and explicit approval. Old conventions are superseded with lineage, not silently replaced.
Epistemic types
Section titled “Epistemic types”Objects carry different status and governance requirements:
| Type | Status | Can change via |
|---|---|---|
| Raw | Ground truth | Never modified |
| Synthesis | Proposed | Challenge with counter-evidence |
| Structural | Promoted | Resolution process |
| Hypothesis | Provisional | Evidence matching validation/invalidation conditions |
| Convention | Governing | Consensus or human approval |
| Resolution | Adjudication record | Superseding resolution |
Open questions
Section titled “Open questions”- How do governance mechanisms perform under adversarial conditions (Byzantine agents)?
- What are the practical costs of evidence-backed writes versus simpler models?
- At what colony size does consensus become a bottleneck?
The Synixolis protocol specifies formal mechanisms for these. The fault isolation section addresses the adversarial case specifically.