Anchor intents and activation
A durable adapter boundary with governed external activation.
Gated integration — source implementation does not establish live activation.
Implementation boundary
The server has a provider-neutral AnchorPort, a Sigil adapter, and durable intent/outbox/receipt state. Current entry lifecycle active is distinct from anchor confirmation. A registry write does not prove that a live Sigil transaction was admitted or finalized.
Safe staged rollout
Keep shadow/private-canary work within the operator's approved configuration and activation gates. MARS-S and production anchor authority must not be inferred from type definitions, a compiled adapter, or a status badge. Public docs do not grant activation authority.
Inspect and recover
Read anchors for an entry. The generated contract distinguishes outbox and receipt state. Admin retry and abandon operate on intent IDs and require capability plus idempotency.
Before retrying an uncertain external action, reconcile receipts and chain state. Abandoning a local intent does not undo an already finalized external transaction. Preserve immutable audit evidence.
Source authority
This page describes the checked-in implementation, not the availability of a public registry.
mars-server/src/anchor/mod.rsmars-server/src/anchor/sigil.rsmars-server/src/anchor/config.rsmars-protocol/src/anchoring.rsmars-server/src/production.rs