# Past success does not make a deviation safe

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

---

## Past success does not make a deviation safe

ID: MHC-D-RESEARCH-1275 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/past-success-does-not-make-a-deviation-safe

Nothing bad happened is evidence about the past, not automatic permission for the next run.

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

### Use when

- A team has operated outside a stated limit, skipped a control or used an exception repeatedly without visible harm and now treats that history as evidence that the rule no longer matters.

### Avoid when

- Do not freeze obsolete rules forever. Standards should change when better evidence and design justify change; the target is silent drift, not legitimate improvement.

### Explanation

Keep the approved boundary and the observed history separate. Repeated success outside a rule can reveal that the rule is conservative, but it can also create normalization of deviance: the absence of failure quietly becomes the new standard without a real risk review. If the boundary should change, change it deliberately with evidence, ownership and updated controls instead of letting habit rewrite it.

### Example

A data migration has skipped one reconciliation step five times without an incident. That history may justify studying whether the step can be redesigned, but it does not silently delete the reconciliation requirement.

### Check

The team can point either to the still-active original boundary or to a deliberately reviewed replacement; repeated success alone did not become the approval mechanism.

### Limits

- Do not freeze obsolete rules forever. Standards should change when better evidence and design justify change; the target is silent drift, not legitimate improvement.

### Evidence and sources

- supports: NASA describes normalization of deviance as a gradual shift in which unacceptable practices or standards become accepted after repetition without catastrophic results. — RS-51C347036C655252. The concept explains one organizational failure pattern; it does not prove that every local deviation is unsafe. (Abstract and Appendix B theme 6)
- supports: NASA safety guidance explicitly warns against using past success to redefine acceptable performance. — RS-1E358C5F88C7894E. A formal standard can still be revised when new evidence justifies it; the warning is against silent redefinition through repeated success. (Recommendations)
- contextualizes: NASA's EVA 23 retrospective describes a recurring sensor failure being accepted as normal based on previous experience, contributing to missed significance when conditions changed. — RS-2293699D6A85B060. This is one high-stakes case and should not be used to estimate risk in unrelated domains. (Normalization of deviance discussion)
- RS-51C347036C655252: Best Practices for Organizational Resilience in the International Space Station (ISS) Program — https://ntrs.nasa.gov/citations/20250005960
- RS-1E358C5F88C7894E: The Cost of Silence: Normalization of Deviance and Groupthink — https://sma.nasa.gov/docs/default-source/safety-messages/safetymessage-normalizationofdeviance-2014-11-03b.pdf
- RS-2293699D6A85B060: 10 Years Ago: EVA 23 – How A High Visibility Close Call Cut Short a Spacewalk — https://www.nasa.gov/general/10-years-ago-eva-23-how-a-high-visibility-close-call-cut-short-a-spacewalk/

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/review-a-risky-success-not-only-a-visible-failure
