# Shrink the example until the same failure is hard to hide

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

---

## Shrink the example until the same failure is hard to hide

ID: MHC-D-RESEARCH-0970 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/shrink-the-example-until-the-same-failure-is-hard-to-hide

A thousand-line attachment is evidence. A six-line reproducer is an invitation to solve the problem.

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

### Use when

- A large file, message or sequence fails, but nobody knows which part matters.

### Avoid when

- Do this in an isolated test environment. Intermittent failures need repeatability work first; smallest-looking is not the same as globally minimal.

### Explanation

Reduce the input without changing the failure you are investigating. Remove a chunk, rerun the same check and keep the smaller input only when the original failure remains. When large cuts stop working, try smaller ones.

### Steps

1. Freeze a safe copy, the environment and an exact failure signature.
2. Remove one chunk; distinguish the original failure from an unrelated validation error.
3. Save the reduced failing case and a nearby passing case.

### Example

A text import fails with hundreds of lines. Reduction leaves two lines and a separator; deleting that separator makes the same test pass.

### Check

Another person can reproduce the specified failure with the reduced input.

### Limits

- Do this in an isolated test environment. Intermittent failures need repeatability work first; smallest-looking is not the same as globally minimal.

### Evidence and sources

- supports: Delta debugging removes parts of an input while preserving a specified failure; a 1-minimal result need not be globally smallest. — RS-DAF12B69E9E3B42E. The practical reduction loop assumes a meaningful, sufficiently repeatable test and preserves the original failure signature. (Delta Debugging; 1-minimality discussion)
- RS-DAF12B69E9E3B42E: Reducing Failure-Inducing Inputs — https://www.debuggingbook.org/html/DeltaDebugger.html

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/bisect-the-version-history-instead-of-inspecting-every-change
