change_id: CHG-2026-014902
risk_class: R2
autonomy_tier: A2
controls: ['CHG-04', 'TRC-01']
data_classification: internal
originator: svc-agent-platform@example.com
agent_identity: svc-agent-platform
model_route: gateway/tier-balanced
supersedes: None
incident_id: None
Raised by the deterministic detector in
scripts/detect_anomaly.py. No human was in the invocation path. A human triages this: fix now, schedule, or dismiss. Dismissals tune the bands.
Problem
post_deploy_error_rate reached 0.0271, which is 6.926 standard deviations from its
30-day rolling baseline of 0.011627 (sd 0.002234).
Rules fired:
- rule_1: one point beyond 3 sigma
Who is affected
Determined at triage. The metric is a service-level signal; the population behind it is not known to the detector and the detector does not guess.
Success criteria
post_deploy_error_ratereturns to within one sigma of its baseline and stays there for 48 hours.- The cause is identified and either fixed or explicitly accepted with a named owner.
- If this class of anomaly can recur, a permanent eval is added to
.agent/evals/cases/by the team that owns it (Stage 4.6).
Out of scope
Changing the detection bands to stop this firing. If the band is wrong, that is a
separate change to ops/response-tiers.yaml with its own record.
Constraints
The agent holds no production write access. Any resulting change goes through the normal PR gate at the autonomy the matrix permits.
Open questions
- Is this a real regression or a change in traffic mix?
- Which deploy correlates with the onset?
- Does an existing eval cover this, and if not, what would it have caught?
Detection evidence
{
"control_id": "OPS-01",
"gate": "anomaly_detection",
"result": "pass",
"findings": [],
"timestamp": "2026-08-28T08:46:46.776005+00:00",
"commit": "b38126e4365166c6035b334372b16ffb6a4e0c0c",
"run_id": "33156675567",
"actor": "Olaf-KrasickiFreund_syne",
"tier": "3sigma",
"rules_fired": [
"rule_1: one point beyond 3 sigma"
],
"mean": 0.011627,
"stdev": 0.002234,
"latest": 0.0271,
"latest_sigma": 6.926,
"action": "propose",
"metric": "post_deploy_error_rate",
"autonomy_tier": "A2"
}