What does the content check on this page actually prove?

That the text you were served for a given page is byte-for-byte the text published in this build. Your browser refetches that page's Markdown twin, recomputes its SHA-256, and compares it against the hash we published in /transparency.json. If a word changed after publication, the hashes stop matching.

What does it NOT prove?

It is not a signature and not an independent witness. The manifest and the page come from the same origin, so an operator who could alter one could alter both. It is tamper-evidence, which is narrower and honest, and we will not describe it as more than that. The module-level attestation layer described elsewhere on this site is a separate and much stronger construction, and it is a design target, not something running today.

Why publish a check that has limits?

Because a check with stated limits is worth more than a badge with none. If we shipped a green tick and called it proof, we would be doing exactly what we argue the industry should stop doing. Stating the boundary is the point.

How do I check a page without using this tool?

Fetch the page's Markdown twin (any page path with a .md extension, for example /technology.md), run SHA-256 over the bytes, and compare it to the entry for that route in /transparency.json. The tool on this page does nothing you cannot do yourself with curl and shasum, which is the intent.

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

Ready.

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.

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. 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 and 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, a ranked index with the key facts and the honesty rails.
/llms-full.txt, the full text of every page in a single fetch.
/AGENTS.md, how to cite us accurately and what not to claim on our behalf.
/ai-content-index.json, the same map as JSON.

Every question, answered directly.

The questions a regulator, a partner, or an engineer asks about HELIX, answered by the founder. No forms, no sales pitch.

Jamie KlonczFounder · RankShield Energy

ONLINE

Pick a question on the left, or search above, and you'll get the direct answer, the way an answer engine would give it.

- / 4

Talk to the founder →