{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/make-the-rollout-stop-itself-on-a-known-bad-signal",
  "id": "MHC-D-RESEARCH-0357",
  "version": "0.1.0",
  "title": "Make the rollout stop itself on a known bad signal",
  "summary": "A safety metric is more useful when it can pull the brake.",
  "kind": "protocol",
  "body": "Connect a small set of high-confidence failure signals to automatic halt or rollback behavior. Define the condition before rollout and test that the automation acts on the intended version. Keep a human override for ambiguous cases and record every automatic intervention for review.",
  "limits": [
    "Poor thresholds can cause harmful flapping or false rollback; automate only signals whose meaning and recovery action are understood."
  ],
  "topics": [
    "union-safe-change-operations"
  ],
  "intents": [],
  "source_ids": [
    "RS-1877C4E72975A9D2"
  ],
  "evidence": [
    {
      "claim": "AWS recommends automated rollback when predefined tests or desired-outcome thresholds indicate that a deployed change is unsuccessful.",
      "source_id": "RS-1877C4E72975A9D2",
      "role": "supports",
      "note": "Automatic rollback needs carefully chosen signals; a false alarm can itself create disruption.",
      "locator": "Pre-defined conditions and automated rollback"
    }
  ],
  "use_when": [
    "A progressive deployment can be observed automatically and waiting for a human response would increase impact."
  ],
  "avoid_when": [
    "Poor thresholds can cause harmful flapping or false rollback; automate only signals whose meaning and recovery action are understood."
  ],
  "example": "Pause a configuration rollout automatically when error rate or a critical data-integrity check crosses the predefined boundary.",
  "check": "A known bad signal limits further exposure without depending on someone noticing a dashboard in time.",
  "steps": [
    "The stop signal maps to a real unacceptable outcome.",
    "The threshold is defined before deployment.",
    "The rollback or halt targets the correct change version.",
    "The automatic path has been tested safely.",
    "A human can inspect and override when the signal is ambiguous.",
    "Every automatic stop creates an auditable event."
  ],
  "sources": [
    {
      "id": "RS-1877C4E72975A9D2",
      "title": "OPS06-BP04 Automate testing and rollback",
      "url": "https://docs.aws.amazon.com/wellarchitected/latest/framework/ops_mit_deploy_risks_auto_testing_and_rollback.html"
    }
  ],
  "relations": [],
  "collections": [
    {
      "id": "RC-4F77BDBBF2481574",
      "title": "Change live systems without turning one mistake into a large one",
      "url": "/collections/change-live-systems-without-turning-one-mistake-into-a-large-one"
    }
  ]
}