Skip to main content

Capstone restore and readiness evidence — assessment

Score 0 absent/incorrect, 1 prompted/incomplete, 2 independently supported with explicit limits, 3 justified fresh transfer. Every category requires at least 2; a high average cannot hide a missing category.

Required evidence​

  • OR1 — SLI: Retain measured user-path SLI, collection health and an exercised actionable alert.
  • OR2 — Control: Pin review scope/version and demonstrate real positive/negative controls with unresolved gaps.
  • OR3 — Restore: Perform isolated restore with keys/config, records and functional checks; compare observed RTO/RPO to targets.
  • OR4 — Incident: Preserve the full original game-day timeline and client-visible recovery evidence.
  • OR5 — Repair: Close a discovered runbook/control gap with a fresh retest, not only an edited document.
  • OR6 — Decision: Record version-specific blockers, accepted risks, owners and independent challenge; missing restore/security evidence blocks readiness.

Calibration​

The fictional 12:00–12:18 exercise yields 18 minutes only if the declared usable outcome is verified then. A backup record ending at 11:55 implies a five-minute gap, but also report actual missing records. A blocked tenant request without an authorized positive control is insufficient. A pending severe blocker means not ready.

Delayed transfer and integrity​

After at least 48 hours, have a reviewer change one assumption or select a previously unseen failure. Predict the outcome, collect fresh evidence and explain discrepancies without the calibration text. Preserve mistakes, repairs, collaboration and generated-assistance disclosures. Record unavailable tools or reviewers as pending evidence, never fabricated completion. Author reference checks are not learner runtime experiments.