Self-hosted backend · runtime contract · fail closed

Runtime Security Readiness

Public-safe mobile view of the production runtime contract for the sovereign LMS. It lists required runtime categories, launch gates, and blocked states without publishing credentials, private resource names, learner records, staff identities, or backend secrets.

Internal deployment health endpoint: /api/runtime-health. It returns readiness booleans only and must remain blocked until owner-approved runtime values exist.

production_backend_ready=false · provisioning_authorized=false · public_release=false · school_opening_ready=false

Required fields

Blocked fields

Secret/private fields

Gates blocked

Production runtime remains blocked

The app has a production security contract, but the real backend is not live until the owner authorizes provisioning and private runtime values are supplied outside public files. Required launch evidence includes identity provider configuration, persistent database, private storage, RBAC negative tests, append-only audit logging, backup and restore drill, and fail-closed release flags.

Runtime environment contract

Runtime security launch gates

Backend Decision Security Operations Post-Fill Validation

Boundary

Runtime Security Readiness does not provision hosting, create secrets, connect identity, create a database, create private storage, change DNS, import learner data, open classes, approve public release, or prove school-opening readiness.