What is MARS?
The registry contract and its implementation boundaries.
MARS stores complete, signed records and provides bounded discovery, version history, lineage, attestations, lifecycle operations, federation, and event notifications.
What an entry proves
A valid entry binds its publisher to canonical payload bytes. Registry presence alone does not prove that a human ceremony occurred, a tool is safe, an endpoint is available, a model meets a benchmark, or an external chain finalized the record. Those claims require the relevant independent evidence.
Current implementation
mars-protocol defines the wire and cryptographic contracts. mars-server implements the HTTP server, authorization, storage, search, and federation. PostgreSQL is the durable reference store. mars-shard contains the feature-gated MARS-S prototype.
Choose a path
Start with HTTP discovery, then use the entry format and publishing workflow. Operators should begin with production configuration.
Source authority
This page describes the checked-in implementation, not the availability of a public registry.
Cargo.tomlmars-protocol/src/lib.rsmars-server/src/lib.rs