Skip to content

docs(recovery): distinguish historical restore drill from current acceptance - #245

Draft
Adam-Ghanem wants to merge 11 commits into
mainfrom
docs/restore-drill-historical-evidence-20261116
Draft

Adam-Ghanem wants to merge 11 commits into
mainfrom
docs/restore-drill-historical-evidence-20261116

Conversation

@Adam-Ghanem

@Adam-Ghanem Adam-Ghanem commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

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.

  • Python CI #43902620816: completed/success, including Black/isort, lint/type-check, compilation and tests with coverage.
  • Security CI #43902620852: completed/success, including dependency audit, secret boundaries, static analysis, frontend validation, container build and test suite.
  • These are commit-associated PR workflow runs; GitHub can check out a generated merge ref rather than the raw feature-branch commit. No local pytest or isolated restore performed.

Formatting investigation

Earlier Python CI failures were due to Black formatting of tests/test_restore_drill_evidence_docs.py. A temporary black --check --diff . diagnostic exposed formatting requirements; the diagnostic was removed in the latest commit, restoring the standard black --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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant