Server
UNITARES Core
cirwel/unitares exposes MCP, REST, a dashboard, and the governance runtime.
The running system, in detail
How UNITARES
fits together.
UNITARES is the record that independent agent runtimes share. It is a single-operator federation kernel: many agent runtimes, one operator-controlled server, one attributed record, while each runtime keeps its own model, tools, and loop.
The receipts
- Core
- cirwel/unitares · Apache 2.0
- Contract
- unitares-sdk · identity, check-ins, evidence, memory, policy
- Research
- UNITARES paper · Wang, 2026 · CC-BY 4.0
- In use
- In operation since November 2025 · CIRWEL's own deployment
- Vocabulary
- Public glossary · terms, definitions, and drift corrections
§ ISystem shape
Core, contract, userland, workloads.
UNITARES is the layer around agent work; the agent loop stays yours.
The core owns identity, provenance, shared knowledge, review, outcomes, audit, policy, and coordination. The public SDK is the contract agents depend on. Claude Code, Codex, Hermes, a custom runtime, or the optional first-party userland speak to that same contract.
-
Core
cirwel/unitares
Identity, claims and evidence, review, outcomes, and reconstruction, with audit, policy, and coordination.
-
Contract
unitares-sdk
The public client surface an agent uses to identify itself, check in, attach evidence, read policy, and participate in shared memory.
-
Userland
optional
Conversation loops, model providers, tools, scheduling, and queues remain outside Core.
-
Workloads
yours
Coding sessions, research agents, long-running agents, services, or whatever else you run.
Three jobs next to this one belong to other layers and stay there: enforcement at the call site, through runtime middleware such as NeMo Relay; traces, through OpenTelemetry; and agent-to-agent interoperability, through A2A. Runtimes reach each other over their own transports. UNITARES is the record behind them, not the transport between them.
§ IIIdentity & lineage
Process attribution is recorded, not reconstructed.
Names are labels. Identity is bound to the process that acted.
Fresh processes mint fresh identity by default. When continuity or lineage matters, it is explicitly declared rather than inferred from a reused display name. Labels retain their source so an auditor can distinguish operator-assigned, self-claimed, and system-generated descriptions.
Every claim, piece of evidence, review, and handoff carries a clear chain of attribution.
§ IIIShared memory
Findings survive the process that discovered them.
People and agents share one provenance-tracked knowledge surface.
Operators write to it as well as agents. Discoveries, decisions, review outcomes, and findings are stored with source, status, and lifecycle rather than disappearing into one chat history.
What matters is that later work can recover what was learned, who recorded it, and whether it was superseded or resolved.
§ IVPolicy & review
Advice, evidence, and authority stay separate.
A check-in returns a policy action: proceed, guide, or pause, with a named reason. Advisory consultation can add model evidence without becoming a decision. Structured review records disagreement and conditions rather than silently replacing the original author or directing agent.
When the server pauses an agent, the recovery is recorded as its own event. What an agent does outside the server stays the host's responsibility.
§ VCIRWEL's workloads
One contract, from coding sessions to a Raspberry Pi.
CIRWEL runs UNITARES across long-running agents, short-lived coding sessions, operational monitors, and an embedded Raspberry Pi testbed, all on the same contract.
§ VIPublic surfaces
What you can use from outside.
The build page is how to reach each of them.
Client contract
unitares-sdk
pip install unitares-sdk gives custom agents the public identity, check-in, evidence, memory, and coordination interfaces.
Optional userland
UNITARES Resident
cirwel/unitares-resident is the first-party userland skeleton, built on the same public contract.