Registry architecture
Durable PostgreSQL storage and clearly bounded integrations.
Request path
HTTP requests enter the Axum router. Public reads use bounded validation and query planning. Protected mutations resolve an opaque session into a MARS principal, enforce a scoped capability and idempotency, validate publisher-controlled data, and commit through the store abstraction.
Persistence
The production reference store is PostgreSQL. Entries, sessions, challenges, immutable audit/public-event ledgers, transfer offers, and anchor outbox state use durable storage. Startup verifies the ledger chains. The in-memory store is an explicit development option that loses state on restart.
External trust
Publisher and peer keys are operator-pinned. SIWS is the concrete session adapter in this release. Federation selects configured peers and verifies signed envelopes. Anchor adapters are provider-neutral, with Sigil integration subject to configuration and governed activation.
Design boundaries
MARS-S describes a proposed global-anchor/regional-shard topology; it is not the current PostgreSQL deployment. Weave is not the current durable entry store. Capacity and latency targets in design documents are not measured production performance.
See libraries, operators, and sharding status.
Source authority
This page describes the checked-in implementation, not the availability of a public registry.
mars-server/src/main.rsmars-server/src/production.rsmars-server/src/store/postgres.rsSHARDING_SPECIFICATION.md