SERVICE STATUS · RELEASE 01

Built to recover, verify and protect progress.

STEM Nodes treats reliability as part of learning quality. This public record separates safeguards that are implemented from human checks that must continue.

OPERATIONAL RELEASE GATES IMPLEMENTED

LIVE HEALTH

A small endpoint with a narrow job.

It confirms that the application can reach its production learning database and that the complete curriculum index is loaded. It exposes no learner records.

Open current health checkMachine-readable JSON · never cached

ACTIVE SAFEGUARDS

What protects the public release

Each control is testable, repeatable and intentionally limited so it does not create a new privacy risk.

01

Privacy-safe health probe

The application and database connection are checked without publishing learner counts, identifiers or records.

✓
02

Graceful recovery

Unexpected page failures provide a safe retry, learning-path return and service-status route instead of a blank screen.

✓
03

Learner-controlled copies

Learners can export their own progress and review data, or delete it, from the learner-data controls.

✓
04

Release smoke gate

Every publication checks core journeys, the curriculum totals, the database probe, a real lesson, the 404 recovery page and the main social asset.

✓
05

Backup integrity

Operator exports receive a SHA-256 manifest and must pass verification before they count as usable backups.

✓
06

Conservative rollback

Application releases can return to a prior deployed version; database restoration is reserved for confirmed corruption and follows a restore drill.

✓

CONTROLLED RELEASE

Every deployment follows the same four stages.

The full incident, backup, restore, retention and ownership procedure is maintained with the application source so a release does not depend on memory.

  1. 01
    Validate

    Run curriculum, scientific-integrity, accessibility, performance and operations gates.

  2. 02
    Protect

    Create and verify an encrypted database export before schema changes or major releases.

  3. 03
    Publish

    Deploy the exact tested commit and keep the previous healthy version available for rollback.

  4. 04
    Observe

    Run production smoke checks and inspect the privacy-safe health response before promotion.