The seal

Corpus version 2026-08-14.4 · 1,512 files hashed

Terralore is a record, and a record you cannot check is a claim. Every state of this corpus — the authored histories, the baked data files, and the published claims bundles and markdown twins a reader actually fetches — is sealed: one SHA-256 per file, one root hash over the whole set, published at /integrity.json and archived under a new version every time the corpus changes.

Current root

sha256:f67a28346cbd8fe99ea5cc01c93b0e7b43e01f4bfdcd8277ddac429a9c23c413

Sealed
2026-08-14
Served files
1,314
Repo files
198

Data vintages in this version

  • economy 2026-08-14
  • education 2026-08-14
  • geography 2026-08-14
  • governance 2026-08-14
  • health 2026-08-14
  • military 2026-08-14
  • resources 2026-08-14
  • society 2026-08-14
  • technology 2026-08-14
  • commodities 2026-08-14
  • histories 2026-08-11

How to verify

No special tooling — the constructions are deliberately boring. To check a file you fetched (say France’s claims bundle) against the seal:

curl -s https://terralore.co/country/FRA.claims.json | sha256sum # compare to files["public/country/FRA.claims.json"] in /integrity.json

To check that the manifest itself is internally consistent, rebuild the root from its own file list: one line per file as <sha256>␣␣<path>, sorted by path, joined with newlines, one trailing newline — then hash that text:

curl -s https://terralore.co/integrity.json | \ python3 -c 'import json,sys,hashlib; m=json.load(sys.stdin); \ t="".join(f"{h} {p}\n" for p,h in sorted(m["files"].items())); \ print(hashlib.sha256(t.encode()).hexdigest())' # must equal the manifest's "root"

Paths under public/ are fetchable at the same path on this site (drop the prefix). Repo paths — the authored history files and baked data — are verifiable in the public git history, where every past manifest is also committed.

What this proves, and what it does not

The seal is tamper-evidence, not tamper-proofing. Nothing stops the operators of this site from changing a figure; what the seal removes is the ability to do it silently. Every version of the manifest is archived append-only below, committed to the public git history, and held in whatever caches and crawls have already fetched it — so a rewritten past would hash differently than the record everyone else already has. The claim is exactly that large and no larger: no blockchain, no external timestamping service, no cryptographic theater. Legitimate changes are the point of a living record — and they are published, with what changed and why, in the ledger.

Every seal cut

Append-only. Each version is the corpus as it stood; none is ever edited or removed.