Operate federation
Configure peers, signing, agreements, and bounded synchronization.
Before enabling
Federation starts disabled. Select peers explicitly, pin their verification keys, configure local signing identity and protected key source, and define agreements/scopes. Invalid signing or trust configuration fails startup before HTTP serving.
Observe convergence
Monitor peer status, breaker state, last successful exchange, lag, and partial discovery metadata. Transport errors must remain visible. Bounded sync/discovery is not a promise that every registry has all records.
Authentication
Peer envelopes bind sender, recipient, nonce, kind, and time. Local client federated discovery uses session capability. Peer administrative updates use federation_sync; operator diagnostics use admin. Keep these interfaces separate.
Conflict rules
Verify signatures first. Prefer matching locally confirmed anchor evidence, then greater sequence, then lexically smaller canonical digest. Never promote an unsigned or merely claimed anchored record. See federation API for exact wire operations.
Source authority
This page describes the checked-in implementation, not the availability of a public registry.
mars-server/src/config.rsmars-server/src/federation/envelope.rsmars-server/src/federation/worker.rsmars-server/src/federation/policy.rs