Sigil Anchoring
External commitment references are metadata, not an implemented chain transaction.
ArtifactMetadata.mars_asset_id and sigil_commitment_cid are optional strings. Setting them does not register an asset, submit a transaction, resolve a commitment, or prove inclusion. The Weft core exposes no ChainClient, read_commitment or automatic Sigil anchoring operation.
For a separately implemented registry/chain integration, define the exact commitment payload and verify its inclusion using that system’s authoritative APIs. Decide whether the commitment covers the ordered-chunk root, canonical manifest bytes, or another digest: a payload Merkle root alone does not bind producer identity or all artifact metadata.
A consumer must separately check the external commitment, the producer’s authority/signature, and payload integrity. A timestamp or commitment is not proof that chunks remain available. This page does not assert that a particular network/contract or MARS workflow is deployed.
Changing sigil_commitment_cid after signing changes the manifest’s signing payload. Re-sign any changed manifest. Also avoid circular schemes where a commitment ID is required inside the exact manifest bytes that the same transaction must commit; specify an external receipt or an explicitly staged protocol instead.
