Recovery lanes
0
Sovereign LMS operations · fail closed
Backup & Restore Readiness
Public-safe mobile view of the recovery contract required before the LMS accepts real learners, grades, guardian data, teacher work, uploads, or production course state. It publishes readiness categories and blocker counts only; it does not expose private storage names, database URLs, secrets, learner records, reviewer identities, or local absolute paths.
Evidence snapshot: 2026-09-04T20:00:31.669612+00:00
Blocked lanes
0
Safe commands
0
Blocked commands
0
Recovery readiness remains blocked for live LMS data
Static Royal artifacts and the external portable work environment are mirrored, but production database backup, object storage restore, secret escrow, RPO/RTO policy, minor-data recovery controls, and clean-target restore rehearsal all require the self-hosted backend decision and owner authorization first.
production_backend_ready=false · live_lms_data_created=false · public_release=false · school_opening_ready=false
Recovery lanes
Recovery command boundary
Boundary
Backup & Restore Readiness does not create a database, create object storage, create credentials, store secrets, change DNS, import learner data, create backups, perform restores, execute incident recovery, approve public release, open classes, or prove school-opening readiness.