Skip to content
Engineering workbench — a technical surface, not a school lesson. Go to the lessons

CubeSTEM MissionLab Twin · M4-D D-A

Institution readiness console

Privacy-minimized deployment diagnostics for institution administrators. This console reports state only; it cannot deploy, migrate, license, activate official rounds, operate hardware or clear an ESTOP.

2

Passing

1

Attention

5

Blocked

4

Human gates

Verdict

local demo only

Automated output is advisory. The release contract and named human approvers retain authority.

Institution administrator scope

attention

Local demo mode contains no live tenant or privileged configuration.

Supabase browser configuration

blocked

Supabase is intentionally absent in local Twin/demo mode.

Current publishable-key name

pass

The stale browser-key variable is not present.

Privileged Supabase key remains server-side

blocked

No privileged key is present in this local/demo process.

Immutable release commit recorded

blocked

A full release commit must be recorded before a release rehearsal.

HTTPS public origin

blocked

HTTPS is required for a production-facing origin; localhost remains valid for development.

Portal loopback binding

blocked

Production service binding must be 127.0.0.1 or localhost.

Official and hardware activation gates

pass

Official rounds, public hardware and paid hardware flags are disabled.

Backup and restore evidence

human gate

A release operator must record a verified backup and restore rehearsal before production migration.

Retention and deletion workflow

human gate

M4-B2 B2-C provides a bounded evidence lifecycle locally; hosted review, account/backup scope and a verified backup/restore policy remain separate gates.

Licensing and commerce

human gate

Licensing is a future hook only. No plan, entitlement or payment activation exists in D-A.

Hosted release validation

human gate

Hosted CI and designated human approval remain mandatory before readiness, merge or deployment.

Authority boundary

  • This report exposes configuration state only; it never returns credential values.
  • A passing automated check does not authorize deployment, migration, licensing, official rounds or hardware.
  • Digital Twin physics, evidence hashes and provenance contracts are outside this readiness slice and remain unchanged.