Attestation
What a reviewer sign-off records, what it covers, and how to verify it.
An attestation is a reviewer's recorded decision that a flagged file is acceptable to merge as it is.
What is recorded
- The reviewer's identity (a named account, not a shared token), the time, and the file and scan it applies to.
- A payload hash over the scan, file, reviewer and timestamp.
- The file's risk context at the moment of review.
- An entry in the organisation's hash-chained audit log.
What it covers
An attestation is bound to the file's content hash. A later scan of byte-identical content — a new push that did not touch the file, or the same file in another pull request of the repository — inherits the attestation. If the file changes, the hash changes and the old attestation does not cover it: the file must be attested again. Attestations cannot be edited or deleted.
Verifying records
Trust Records and audit-log exports are signed with Ed25519. The public key is at /.well-known/trustledger-export-signing-key; the signed content is the canonical JSON of the document's record (keys sorted at every level, no whitespace). scripts/verify-trust-record.mjs in the repository verifies a document offline, without trusting TrustLedger. The audit log's hash chain can be verified from the Audit page.
Next: API reference →