The flag's audience and value as stored in the feature-management tool.
Workflows · Feature-flag rollouts
Checkout_v3 waits for its service owner before a full rollout.
CC8.1 evidence for a rollout: the flag, the audience change, the named approver and reason, and the stored value read back.
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
Enable checkout_v3 for 100% of production traffic
The flag changes the checkout path for every production request in its audience.
- Identity
- release-agent · Product engineering
- Target
- production/checkout_v3
- Cost
- Recorded agent cost
- Evidence
- Audience change, health checks, and rollback value
SOC 2 CC8.1
Sensitive: waits for a named approver.
The audience before and after, the health checks, the Checkout owner's reason, and the CC8.1 test it supports.
Policy decision
Full production flag rollouts require the Checkout service owner.
Checkout service owner
The action waits until this owner approves or denies it.
Tool call resumes
The feature-management tool applies the approved audience and records the new value.
Tool call stays blocked
The audience stays unchanged and the denied rollout remains recorded.
Execution order
The agent request stops before the connected tool runs.
- 01Release agent requests the audience change
- 02Deixic checks the flag, environment, audience, and policy
- 03Checkout service owner decides
- 04Connected feature-management 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.