GRRCDocuments
Everything GRRC has committed to writing is on this page. Each document is reproduced word for word from the original, and each carries a fingerprint you can recompute yourself, so you can prove nothing was quietly changed after publication.
- What each document is, in one line.
- A digest for every one, computed at build time over its exact bytes.
- The raw source file behind each digest, fetchable and hashable.
The record
-
The GRRC Charter
What GRRC is, what it refuses to do, and the independence threshold it holds itself to. Start here if you want the institution rather than the mechanism.
byte-verbatim — sha256 over the exact bytes of
GRRC_Charter_v1.0.md— source bytes (markdown, sha256-pinned) ↗ (11,622 bytes):8d7bfe97c53bc28592a6be5ed2ec46ad44f55676ba9899bd40b5b712e4c22ce1 -
The Bounded-Claim Statement
What a verification asserts, and what it deliberately does not. The narrowest and most important document here.
byte-verbatim — sha256 over the exact bytes of
Phase34_Slice222_GRRC_BoundedClaimStatement.md— source bytes (markdown, sha256-pinned) ↗ (4,534 bytes):2fa6ce07620bb43266b9b685b07aab3fd2fee0d5363a5c297196573082dca2c3 -
The Independent Verification Specification
The complete method for checking a certificate yourself, complete enough to build your own verifier and mirror every input it needs.
byte-verbatim — sha256 over the exact bytes of
Phase34_Slice222_GRRC_IndependentVerificationSpec.md— source bytes (markdown, sha256-pinned) ↗ (14,627 bytes):6d3cd35cf88dddcf4c4ba6a5109dc7fed940929aa30194a991eee7b7a275756b -
The Verification API Reference
The hosted verification endpoints: a convenience over the offline floor, never a substitute for it.
byte-verbatim — sha256 over the exact bytes of
Phase34_Slice222_GRRC_VerificationApiReference.md— source bytes (markdown, sha256-pinned) ↗ (6,969 bytes):128d4033640184bdd8b39719d3c92a1aed92f60354bd076d7154696751f14e50 -
The Certification Registry
The certifier-signed list of robots granted a certification. It asserts membership, never current validity; verification answers that.
byte-verbatim — sha256 over the exact bytes of
grrc-registry.json— source bytes (JSON, sha256-pinned) ↗ (1,212 bytes):3889316714debbede32fd8f4c06571e46beb9e187b4735107519dffad728d226
Source — how these digests are produced, and how to check one
Each digest above is a SHA-256 computed at build time over the exact bytes of the file it names, and the link beside it fetches those same bytes. Download a file, hash it with any standard tool, and compare. If the two ever disagree, the source bytes govern and the page is wrong.