Repository navigation
docs(recovery): distinguish historical restore drill from current acceptance - #245
Draft
Adam-Ghanem wants to merge 11 commits into
Draft
Adam-Ghanem wants to merge 11 commits into
Adam-Ghanem wants to merge 11 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Clarify that the 2026-08-12 restore drill and schema 10 are historical, environment-specific evidence, not current production recovery acceptance. Require current runtime schema verification, backup provenance, independently trusted digest, audit integrity and measured RTO/RPO. Includes documentation regression tests.
Verified CI — 2026-11-16
Latest branch HEAD:
d84e8a63.Formatting investigation
Earlier Python CI failures were due to Black formatting of
tests/test_restore_drill_evidence_docs.py. A temporaryblack --check --diff .diagnostic exposed formatting requirements; the diagnostic was removed in the latest commit, restoring the standardblack --check .workflow. Both CI workflows are now green for the latest associated HEAD.Dependencies and safety
Draft, based on
main(29941838), independent of #199 and the stacked recovery PRs. No merge, deployment, real restore, unauthorized scans, active remediation, credentials or provider spend. Before acceptance, review dependencies and run an isolated synthetic SQLite staging restore with authenticated readiness/inventory, audit integrity and measured RTO/RPO.