Seal a policy
Define who may attest, where evidence may originate, and how fresh it must be.
Evidence-bound canonical memory
MemorySeal binds evidence authority, provenance, freshness, corroboration and exact consensus outcomes before a claim can advance canonical subject history.
0x3f11F1…6f9f640xd5f0B4…95bd8BCanonical reads never depend on provisional Accepted state.
Bradbury / latest final
Reading finalized state…The protocol
Define who may attest, where evidence may originate, and how fresh it must be.
Bind immutable digests to stable identities and strictly increasing evidence versions.
Attach policy-bound evidence to a subject without weakening provenance.
Consensus resolves the claim; supported outcomes advance canonical subject memory.
Trust model
Approved issuers, approved HTTPS origins, corroboration thresholds, freshness windows and claim lifetime are sealed into a policy fingerprint.
Every evidence record carries a stable record ID, monotonic version, issuer, publisher origin, content digest, issue time and expiry.
Review resolves the actual consequential claim state. Repair remains explicit instead of hiding evidence failure behind a binary outcome.
Supported claims become subject history and a canonical head, while recorded and currently effective heads remain separately observable.
State is meaning
Repairable evidence failure is not rejection. Supersession is not cancellation. Expiry is not an adverse review. The UI keeps every protocol state distinct.
Inspect, don’t assume
Search known policy, evidence, claim and subject identifiers directly against the frozen Bradbury deployment.