Build Integrity
A plain record of what the release contains, where its source ends, and which checks stand between the source tree and the mirror.
The machine-readable manifest
The build writes a small same-origin JSON file with the current site version, public-room count, hidden-room count, alias count, concordance coverage, and the declared source/mirror boundaries.
Open data/build-integrity.json
The manifest is regenerated from public source during the release build. It is not a deployment log, a visitor record, or a private development ledger.
What the manifest does not carry
- No host path, source prompt, private register, ledger, credential, or secret.
- No visitor identifier, query history, cookie value, analytics record, or account state.
- No hidden-room content; hidden rooms are counted only as a boundary count.
- No external runtime dependency and no public community or submission system.
The checks around it
- The store verifies the source and database before export.
- The concordance and integrity manifests are generated from the public source tree.
- The mirror and alias are synchronized, then the validator and all fourteen audits run.
- Browser checks cover representative widths, print visibility, reduced motion, no-JavaScript entry, and zero external page requests.
- The corpus audit confirms that the presentation cut did not remove protected content.
For the human-readable change record, see the correction ledger and the changelog.