Document integrity

Verified

Every document in this register carries a SHA-256 stamp. Paste the short form printed in a document footer, or the full 64-character digest, and this page tells you exactly which artefact it is: title, version, the date it was last modified, and its classification.

Hash submitted

0C20A76C14B0

12-character short form, as printed in a document footer.

This hash is a document we published

Cutover Runbook: T-7 Days to T+1 Day

RBK-GL-012v1.0.0ClientRunbookGL1234InfrastructureS8 Deployment & Integration

Version: v1.0.0
Last Modified On: 31 July 2026
Classification: Client credential requiredyou have not cleared this tier
Full digest: 0c20a76c14b03d8c4b73811622c7747c81e2b954208d0ed5d331b0d0b668b61d

If the copy in your hand carries this document ID, this version and this stamp, its text is byte-for-byte the text published here on 31 July 2026.

What this hash covers

SHA-256 computed over the UTF-8 source text of the document exactly as published in this register: before tokens are substituted, before the letterhead is applied and before any conversion to PDF.

It therefore identifies the text, not one particular file. Two hospitals reading the same standard agreement see the same hash, because until values bind at signature it is the same instrument.

An executed document is different. At issue, its render, its resolved token values and its own hash are frozen and stored against the instance; that hash is verified inside the workspace against the stored record, not against this register.

The short form is the first twelve hexadecimal characters of the digest, upper-cased. Every revision of a document changes it, which is the point: a stamp that survived an edit would prove nothing.

491 artefacts are hashed on every check. Nothing about your query leaves this origin.