A release is a handoff.
Readiness, ownership and drain belong in the deployment contract.
Declare dependencies and intent
The checked-in forgezero.deploy.ts is compiled into a typed plan by the existing ForgeZero Agent SDK. Exact source revision, software, resources, credentials, database storage and rollout policy are release inputs. Plans contain references rather than private values.
bun run check:deploy
bun run compile:deploy Verify before promotion
Start the candidate with isolated installation state and no duplicate queue or scheduled-job ownership. Verify the exact release, dependencies and backend readiness. A live process or successful health request alone does not establish confidential placement or safe execution authority.
Transfer state, then execution authority
Protected memory travels directly between authenticated peers over the shared encrypted transport. The controller handles metadata. Receiving state does not authorize execution: durable checkpoints and fenced ownership must agree before the candidate can process work.
Drain real work
The stable guest proxy selects the serving slot. Retiring a release must account for HTTP requests, sockets, provider effects, queues and schedules. Keep a compatible previous release and frontend assets. An external write with an unknown result requires reconciliation, never blind replay.