A stricter runtime boundary for Spaces

A Space is easy to demo and difficult to operate if its build and runtime states are conflated. MEGA now keeps those boundaries explicit.

Builds produce immutable input#

A successful build identifies one repository revision and one runtime image. Deployments consume that record rather than rebuilding opportunistically.

Admission checks the environment#

Hardware availability, organization policy, credentials, and network rules are evaluated before a runtime is started. Failures point to the gate that rejected the deployment.

Health is not readiness#

Process health, application readiness, and public routing are reported separately. Operators can diagnose a warming application without presenting it as available.