# Follow the why-chain until the cause becomes changeable

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

---

## Follow the why-chain until the cause becomes changeable

ID: MHC-D-RESEARCH-0730 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/follow-the-why-chain-until-the-cause-becomes-changeable

Do not stop at a label that merely renames the event.

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

### Use when

- The immediate explanation is a label such as human error, missed step, bad data or process deviation.

### Avoid when

- Five Whys is a prompt for inquiry, not a guarantee of one root cause. Complex failures commonly have interacting causes.

### Explanation

Ask why the observed event was possible, then ask why about the answer while the chain remains evidence-based. Stop when you reach a factor the system can change, when the chain branches, or when evidence runs out. Record branches instead of forcing one linear root cause.

### Steps

1. Is this answer more than a label?
2. What evidence supports the next link?
3. Did the chain split into multiple contributors?
4. Is the current factor changeable?
5. Are we now guessing?

### Example

Wrong field mapped → template used an old label → template had no version check → add a version gate at upload.

### Check

The final factor suggests a concrete control and each causal link has evidence or is marked as a hypothesis.

### Limits

- Five Whys is a prompt for inquiry, not a guarantee of one root cause. Complex failures commonly have interacting causes.

### Evidence and sources

- supports: Modern RCA guidance emphasizes system-level contributing factors and sustainable corrective actions rather than stopping at individual blame or documentation. — RS-C63447C9710D56FD. AHRQ discusses healthcare safety. The corpus transfers the system-design logic cautiously to ordinary work. (Introduction; RCA2; action hierarchy discussion)
- supports: Five Whys is used in RCA2 to extend a causal chain beyond an immediate event description. — RS-C63447C9710D56FD. Repeated 'why' questions can oversimplify branching causes; answers still need evidence. (Discussion of event mapping and Five Whys)
- RS-C63447C9710D56FD: The Evolution of Root Cause Analysis — https://psnet.ahrq.gov/perspective/evolution-root-cause-analysis

No review details supplied.
Related (alternative): https://vedokrok.com/knowledge/fan-possible-causes-out-before-narrowing-them
