Autopilot Release
Understand the explicit automation boundary for release execution and why governed evidence still owns the decision.
Autopilot can orchestrate a release only after the required scope, policy, and evidence boundaries are explicit. Automation does not weaken the gate.
npx workspai autopilot release --jsonThe release contract records the requested action, inputs, checks, approvals, artifacts, and terminal result. A blocked or failed prerequisite remains visible and cannot be converted into success by a model response or a later unrelated command.
Use Verified Goals when the desired release outcome must remain durable across sessions. Use Pipeline for the broader governance sequence. Use Autopilot only for the explicitly authorized automation boundary.
Release side effects require the authority and credentials of the invoking environment. Planning or documentation never implies authorization to publish.
Command reference: autopilot and
autopilot release.