Agreebase separates the record itself from the artifacts used to prove it. A sealed record is a particular type, body, participant state, and version. The artifacts are the PDF or notarization payload, evidence metadata, hashes, and blockchain transaction associated with that state.
Hashes
A hash is a cryptographic fingerprint of content. If the normalized content changes, the hash changes. Agreebase uses hashes so later verification can compare a submitted artifact with the sealed record.
Signed artifacts
Agreements and declarations produce a signed PDF after sealing. Notarizations produce a typed content-hash payload and can produce a private PNG card instead of a PDF.
Blockchain anchoring
Agreebase writes a public record to the Base blockchain after sealing when the blockchain provider is configured. Hash-only records publish commitments; full-text records publish the selected text. The chain is not a private document vault.
What permanence means
Permanence means the sealed version remains checkable. It does not mean the real-world relationship can never change. Amendments and mutual cancellation records preserve the earlier record while creating a later authority.
For a fuller explanation of the blockchain publication settings and retained artifacts, see Agreebase permanence.