# Build the smallest failure you can reproduce

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

---

## Build the smallest failure you can reproduce

ID: MHC-D-RESEARCH-0293 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/build-the-smallest-failure-you-can-reproduce

A bug you can summon is easier to interrogate than a bug you can only describe.

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

### Use when

- A defect is real but every retest changes several conditions at once.

### Avoid when

- Do not strip away timing, authorization or state when those conditions may be part of the failure.

### Explanation

Reduce the failing case until it still breaks with as little unrelated setup as practical. Preserve the condition that triggers the problem, the exact input, the observed output and the smallest environment facts that matter. The goal is not an elegant demo; it is a repeatable question you can ask the system again after each hypothesis.

### Steps

1. Capture one failing input and its observable result.
2. Remove unrelated steps or data one at a time while the failure still occurs.
3. Freeze the reduced case so another person can run it without reconstructing your memory.

### Example

Instead of rerunning an entire customer migration, keep one anonymized record that still produces the wrong partner role.

### Check

A colleague can run the reduced case and observe the same relevant failure or explicitly record that it remains intermittent.

### Limits

- Do not strip away timing, authorization or state when those conditions may be part of the failure.

### Evidence and sources

- supports: Google SRE recommends a solid reproducible test case because it speeds debugging and can enable safer investigation outside production. — RS-A4A16C807A94C9D8. Some intermittent or environment-specific failures cannot be reproduced on demand; the card does not require manufacturing a false reproducer. (Simplify and reduce)
- 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
