{
  "schema": "vedokrok.public-item.v1",
  "release_id": "MHC-RPUB-20260920-75ad787a",
  "url": "/knowledge/let-the-change-bake-before-stacking-the-next-one",
  "id": "MHC-D-RESEARCH-0353",
  "version": "0.1.0",
  "title": "Let the change bake before stacking the next one",
  "summary": "If you change the experiment before the result arrives, you inherit an explanation problem.",
  "kind": "heuristic",
  "body": "Choose an observation window long enough to expose the failure modes you care about before adding another unrelated change. Watch leading and delayed signals during that time. The point is not idle waiting; it is preserving causal visibility long enough to know whether the current state is healthy.",
  "limits": [
    "Do not delay urgent remediation just to preserve a clean experiment; incident response can justify immediate follow-on action."
  ],
  "topics": [
    "union-safe-change-operations"
  ],
  "intents": [],
  "source_ids": [
    "RS-948FC7FCF8F1FE56"
  ],
  "evidence": [
    {
      "claim": "AWS identifies rapid follow-on deployments without sufficient bake time as a deployment anti-pattern.",
      "source_id": "RS-948FC7FCF8F1FE56",
      "role": "supports",
      "note": "Required observation time depends on traffic, delayed jobs and the failure modes that matter.",
      "locator": "Common anti-patterns"
    }
  ],
  "use_when": [
    "A first change has completed technically but important effects may appear with traffic, queues or delayed jobs."
  ],
  "avoid_when": [
    "Do not delay urgent remediation just to preserve a clean experiment; incident response can justify immediate follow-on action."
  ],
  "example": "After changing replication parallelism, observe at least one full processing cycle before also changing retry settings.",
  "check": "When a metric moves, the team still has a reasonably interpretable set of recent changes rather than a stack of simultaneous experiments.",
  "sources": [
    {
      "id": "RS-948FC7FCF8F1FE56",
      "title": "REL08-BP05 Deploy changes with automation",
      "url": "https://docs.aws.amazon.com/wellarchitected/latest/reliability-pillar/rel_tracking_change_management_automated_changemgmt.html"
    }
  ],
  "relations": [
    {
      "from": "MHC-D-RESEARCH-0353",
      "to": "MHC-D-RESEARCH-0344",
      "type": "useful_with",
      "url": "/knowledge/canary-the-batch-before-scaling-it"
    }
  ],
  "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"
    }
  ]
}