# Verify this site

> Recompute the SHA-256 of any page on this site in your own browser and compare it to the hash we published. Tamper-evidence you can check yourself, with its limits stated plainly.

Check us

# Verify this site.
We argue that a reactor should be checkable rather than taken on trust. It would be strange to ask that of a reactor and not of our own website. Every page here publishes a hash. This is where you check one.
Content integrity check
Page path Recompute hash and compare Ready.
Published - Recomputed - Build -
This proves the text you were served matches the hash published for this build. It is
tamper-evidence, not a signature and not an independent witness, and we do not present it as one.
The manifest is at [/transparency.json](https://rankshieldenergy.com/transparency.json).

## What this checks
Every build writes a clean Markdown twin of every page, hashes each one with SHA-256, and publishes the result at [/transparency.json](https://rankshieldenergy.com/transparency.json). The tool above refetches a twin in your browser, recomputes the hash with WebCrypto, and compares. Nothing is sent anywhere; the computation happens on your machine.

## What this does not check
This is tamper-evidence, not a signature and not an independent witness. The manifest and the page are served from the same origin, so an operator able to change one could change both. What it rules out is a page being altered after publication without the published hash moving with it. That is a real and narrow guarantee, and it is the only one we claim here.
The module-level attestation described on the [technology](https://rankshieldenergy.com/technology/) and [safety](https://rankshieldenergy.com/safety/) pages is a different and far stronger construction: post-quantum signed telemetry, an append-only log, independent off-site co-signers. It is a design target for the reactor, not something running on this website today, and we label it that way everywhere it appears.

## Do it yourself
The tool is a convenience, not the mechanism. Any page path with a.md extension returns its twin, and /transparency.json lists the expected hash for each route:
curl -s https://rankshieldenergy.com/technology.md | shasum -a 256
curl -s https://rankshieldenergy.com/transparency.json | grep -A2 '"/technology/"' If those two agree, the page you read is the page we published.

## The other machine surfaces
The same discipline applies to what we hand to AI systems. Each of these is generated from one configuration file at build time, so none of them can quietly disagree with the pages:

- [/llms.txt](https://rankshieldenergy.com/llms.txt), a ranked index with the key facts and the honesty rails.
- [/llms-full.txt](https://rankshieldenergy.com/llms-full.txt), the full text of every page in a single fetch.
- [/AGENTS.md](https://rankshieldenergy.com/AGENTS.md), how to cite us accurately and what not to claim on our behalf.
- [/ai-content-index.json](https://rankshieldenergy.com/ai-content-index.json), the same map as JSON.