Machine-Readable Records
Every record below is generated at build time from the same release facts rendered across this site — release versions, artifact checksums, verification receipts, and proof links. Nothing here is hand-maintained.
What this is
These JSON documents exist so a human, script, or verifier can ask "what does Proof Foundry currently claim publicly about this product?" and receive one deterministic, versioned, sanitized answer — the same answer the HTML pages render.
The published canonical record is /truth/v2/index.json, with one record per product under /truth/v2/products/. Its schema is schema-v2.json, and it carries a SHA-256 digest of the authored release model (modelSha256).
That model is the build input release-truth.json, which is kept in source custody and is not published. /truth/index.json (v1) and /site-manifest.json are derived compatibility views.
Every visible product, its current public version and state, and the link to its full record.
Release status, publication date, artifact filenames and SHA-256 digests, verification receipts, and public proof links.
/truth/schema-v1.json — the versioned v1 contract for these records.
Truth records carry source commit and tree identity, not a build timestamp. The same source produces the same bytes.
Products
Status and version come from the release facts at build time — never from copy pasted into this page.
Public release · v0.3.1 · 2 public artifacts
Public release · v0.4.0 · 1 public artifact
Public release · v11.2.0 · 2 public artifacts
Public release · v1.0.7 · 1 public artifact
Public release · v2.0.0 · 1 public artifact
Public release · v0.3.5 · 1 public artifact
Withdrawn · no public download · Withdrawn v1.1.0 · 1 recorded artifact
Stability
Every v1 record carries schemaVersion: 1 and is defined by schema-v1.json, with one inherited exception: the withdrawn Reality Gate record lists an artifact with no download URL, which schema-v1 does not accept. Every v2 record carries schemaVersion: 2 and is defined by schema-v2.json.
Versions, dates, checksums, availability and links update as products release — without changing the contract version.
Any change to the contract's shape or field meaning publishes under a new schema version. v1 records keep their meaning forever.
Where to go next
The human-readable layer over these records — current release, verified facts, known limits, and proof for every product.
The doctrine and verification philosophy these records exist to serve.
Release records, checksums, test gate counts, and cryptographic evidence receipts for every product.
