The deployment as recorded by the deployment tool: release identifier, target, and status.
Workflows · Production deployments
Hold a production deployment until its owner reviews the release.
CC8.1 evidence for a production release: the target, the change evidence, the named approver and reason, and the read-back result, kept in one receipt.
Example workflow. Execution requires a configured tool with provider permissions for this action; see the connection’s operation reference or bring your company tool to the demo.
Agent request
Deploy the current release candidate to production
The release changes customer-facing production behavior.
- Identity
- release-agent · Engineering
- Target
- production
- Cost
- Recorded agent cost
- Evidence
- Release diff, checks, and rollback steps
SOC 2 CC8.1
Sensitive: waits for a named approver.
The release diff, the checks, the Service owner's reason, the deployment result, and the CC8.1 test it supports.
Policy decision
Customer-facing production releases require the Service owner.
Service owner
The action waits until this owner approves or denies it.
Tool call resumes
Deixic resumes the deployment call and records the deployment result.
Tool call stays blocked
The deployment stays blocked and the release remains unchanged.
Execution order
The agent request stops before the connected tool runs.
- 01Release agent requests production deployment
- 02Deixic checks release, target, evidence, and policy
- 03Service owner decides
- 04Connected deployment tool returns the result
- 05Deixic reads the result back and attaches the receipt to the test
Activity history keeps the request, decision, cost, and result.
Keep the procedure for the next request.
Keep the policy and decision history, save the steps and evidence as a skill, and test changes on real sessions; an approval stays specific to its request.