Releases and environments
DirectionMove a reviewed Company Runtime change from an isolated branch to production with confidence.
A release is a reviewed version of the Company Runtime made available to an environment. It includes source, schema changes, configuration, and the evidence that the change is safe to operate.
A release is a decision
Changes should move through an explicit path: propose, inspect, test, approve, deploy, observe, and roll back or keep. A release is not just the latest commit or a successful build.
Keep environments honest
project/one customer-owned systemcompany-os/objects, tools, loops, and knowledgeapps/purpose-built interfacesmigrations/database historycontinual.config.tsproject configurationDevelopment, preview, and production may have different credentials and data. They should run the same contracts and make differences explicit rather than relying on local-only behavior.
One source of truth
Use projects and branches to isolate work. Use deploying to make an environment available. Keep the path from source to running system inspectable.