> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/trust.md).

# Trust, transparency and compliance

Every artifact Seal ships is accompanied by mechanisms that let you, your auditors, and your customers verify what was changed, who built it, and whether it has been tampered with. This section is the canonical home for those mechanisms — what the artifacts are, how to read them, and what compliance frameworks they support.

## What's in this section

* [Why this matters](/trust/why-this-matters.md): the trust model — what you can verify and why.
* [Code diff](/trust/code-diff.md): the source-level diff between a sealed version and its origin.
* [Attestations](/trust/attestations.md): per-package PDF attestations and machine-readable VEX records.
* [Patch validation prompt](/trust/patch-validation-prompt.md): an LLM-driven scope check for sealed patches.
* [Cryptographic signing and hash verification](/trust/signing.md): ECDSA signing and SHA-512 hashes.
* [SLAs and compliance frameworks](/trust/compliance.md): the 72-hour SLA, Seal's own certifications, and the frameworks Seal helps you meet.