# Start with what changed, not with certainty about it

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Start with what changed, not with certainty about it

ID: MHC-D-RESEARCH-0296 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/start-with-what-changed-not-with-certainty-about-it

The last change deserves an interview, not an automatic conviction.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- A previously stable system suddenly changes behavior.

### Avoid when

- Failures can emerge without a local deployment when dependencies, data, capacity or external conditions change.

### Explanation

Build a short list of deployments, configuration changes, dependency changes, data-shape shifts and load changes near the onset of the symptom. Compare their timing with the first observable deviation. Use the list to prioritize tests, but require evidence that connects a change to the failure before calling it the cause.

### Example

A job starts timing out after a transport import; compare the failure window and behavior before assuming the transport is responsible.

### Check

At least one recent-change hypothesis becomes stronger or weaker because of a test, not because of chronology alone.

### Limits

- Failures can emerge without a local deployment when dependencies, data, capacity or external conditions change.

### Evidence and sources

- supports: Google SRE identifies recent deployments, configuration changes and environmental shifts as productive leads when troubleshooting sudden changes in behavior. — RS-A4A16C807A94C9D8. Temporal proximity is a lead, not proof of causation; an unchanged component can still fail because its inputs or dependencies changed. (What touched it last)
- RS-A4A16C807A94C9D8: Effective Troubleshooting — https://sre.google/sre-book/effective-troubleshooting/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/prefer-a-test-that-kills-hypotheses
