What this module owns
The verdict on a deploy already exists — it is just made informally. Someone merges, watches a dashboard for two minutes, sees nothing obviously red, and moves on. The judgement is real work being done with no baseline, no idea which of forty panels sits inside the change’s blast radius, and no record of the decision. The failures that slip through are specific: the regression that only appears under the traffic pattern arriving at 4pm, the change that is fine at p50 and doubles p99, the deploy that is correct on its own and interacts badly with a migration from an hour earlier. Change Intelligence & Risk Control makes the verdict explicit — a stated comparison against a baseline, on the signals that belong to this change, producing a decision you can audit and a rollback you can approve. Good looks like a trustworthy verdict within minutes of a deploy, most rollbacks starting from that verdict rather than from an incident, and a false-rollback rate low enough that nobody overrides the module by week two.The workflows inside it
This module contains 3 workflows.Post-deploy verdict
Starts when your delivery system reports that something shipped. It identifies the blast radius of the change, watches the signals inside it over a soak window, and returns ship, hold, or roll back with the comparison that produced the answer.Canary judgement
Starts at a canary step in a progressive rollout. It compares the canary against its baseline on latency, errors, and cost together, then promotes or aborts — so a canary that is marginally faster and substantially more expensive does not pass unnoticed.Change blast-radius brief
Runs before the change ships. It states what this change can break, who owns those services, and which signals to watch — the pre-flight brief nobody writes by hand.Because a verdict is a watch-and-compare loop over a soak window rather than a single request, each
of these workflows spans several steps and several runs. The whole sequence is durable: it survives
a restart mid-soak.
What it needs connected
Enabling it
1
Open Modules → Overview
Change Intelligence & Risk Control appears in the AI Software Operations family with the three workflows it contains.
2
Turn it on
Enabling the module adds Change Intelligence & Risk Control to your sidebar.
3
Point your delivery system at it
Create the endpoint your CD system posts deploy events to, then bind an agent to each step you
expect to run.
What you see when it runs
The module lists every change it has judged. Each record carries the change that triggered it, the blast radius it derived, the signals it compared and over what window, and the verdict — with the runs behind each stage available to open. A roll back verdict is a proposed production action, so it arrives as a decision for a human rather than something already done. You approve or reject it with the comparison in front of you.Next steps
CI/CD Health & Remediation
Keep the delivery path healthy before and after a change merges.
Incident management & troubleshooting
Where a missed verdict ends up.
Approvals
How a rollback waits for a human decision.
Triggers & schedules
How a workflow starts, on a schedule or from an endpoint.