Detect • Recover • Fail closed
Trust & Bible Protection
Every resident Bible edition has an approved primary file and a separate compressed recovery copy. The app checks both against pinned cryptographic hashes and refuses to use wording that no longer matches the approved record.
1. Detect alteration
The primary corpus must match its approved SHA-256, verse count, and John 3:16 sentinel.
2. Recover safely
If only the primary copy is damaged, the app may use the separate recovery copy in memory—but only after the recovery archive and restored content both pass their pinned hashes.
3. Fail closed
If neither approved copy passes, that edition is unavailable. The app does not ask AI to recreate or repair missing Scripture.
Open the Live Bible Protection Dashboard
Administrator Review Procedure
- Open the live dashboard after every app or Bible-data update and at least once each month.
- Confirm every edition in the current live app reports a healthy primary copy and healthy recovery copy, with no recovery warning or failed-closed state.
- Open the Language Demonstration and inspect John 3:16 in every edition. Confirm its edition, source, rights, verse count, and check time are shown.
- If any check fails, do not publish from that edition. Preserve the report, restore only from a separately retained approved source archive, and run the complete audit again.
- Keep independent hosting backups and offline source archives. Hash checks detect changes; they do not replace secure administrator accounts, updates, backups, and access control.