The MARS whitepaper
Software that acts.A registry that understands it.
The research behind MARS explores a shared registry for autonomous capabilities: their identities, provenance, ownership, and discovery across independently operated infrastructure.
- Research edition · June 26, 2026
- Open architecture
- Protocol and scale targets
The paper explains the registry model, the proposed scale architecture, and the boundaries of the shipped v1 profile.
- 01Read the model
- 02Follow the architecture
- 03Inspect the assumptions
01 / idea
Beyond the package name.
Finding autonomous software raises questions a package name cannot answer: who published it, what it can do, which version is current, and what evidence accompanies it.
A federated registry protocol for autonomous entities.
MARS — the Multi-Agentic Registry Service — develops a common model for registering, resolving, discovering, and managing agents and the software they depend on within the Open Agent Specification ecosystem.
The research considers signed records, content anchoring, distributed storage, publisher bonds, federation, and MARS-S sharding. Its central proposition is that useful software should be discoverable together with the identity and context needed to evaluate it.
Research overview. The linked PDF is the June 26, 2026 edition; its query-language and distributed-architecture descriptions are historical research, not the current executable contract.
02 / questions
Three questions worth asking.
What is this capability?
A shared record can carry the payload, schema, version, endpoints, and relationships needed to understand what was published.
Where did it come from?
Publisher identity, signatures, lineage, and attestations provide distinct pieces of evidence for a reader to inspect.
Who controls the catalog?
Independent registries and explicit federation explore how a shared protocol can coexist with local infrastructure and policy.
03 / research and runtime
Read the ambition. Build on the contract.
The June 26, 2026 research edition includes historical language and proposed features that differ from the current reference service. Use the canonical implementation guide for integrations today.
Current reference profile
mars-server with PostgreSQL, Rust-derived v1 contracts, public local discovery and resolution, SIWS authentication, and configured peer federation.
Staged and proposed architecture
Sigil authority is staged. Distributed Weave persistence, MARS-S topology, and planetary-scale latency and capacity figures are architecture targets, not measured production results.
Explore the MARS-S draft →