# Do not discipline away a system defect

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

---

## Do not discipline away a system defect

ID: MHC-D-RESEARCH-0492 · Version: 0.1.0 · Kind: principle
Source: https://vedokrok.com/knowledge/do-not-discipline-away-a-system-defect

Accountability and redesign are different questions; answering one does not remove the other.

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

### Use when

- An incident review focuses on who clicked the wrong thing while the same interface can mislead the next person.

### Avoid when

- This is not legal or HR advice; serious misconduct and regulated incidents require the relevant formal process.

### Explanation

Separate behavioral accountability from system learning. Determine whether the action was inadvertent error, an at-risk shortcut, or reckless conduct under the organization's policy. Independently ask what design allowed one action to produce the harm and what would protect the next user. Even when accountability is appropriate, fix the repeatable system trap.

### Example

A user may violate a known rule and still reveal that the destructive button lacks any environment distinction or validation.

### Check

The incident review can name both any justified accountability response and the system improvement needed for recurrence prevention.

### Limits

- This is not legal or HR advice; serious misconduct and regulated incidents require the relevant formal process.

### Evidence and sources

- supports: AHRQ just-culture guidance separates inadvertent human error from at-risk or reckless behavioral choices and recommends system design rather than blame as the default response to ordinary error. — RS-071174D15DDE671E. Serious misconduct, policy violations and legal obligations require their own accountability process. (System design, behavioral choices and accountability)
- RS-071174D15DDE671E: Staff Empowerment: System design, behavioral choices, learning systems and accountability — https://www.ahrq.gov/hai/quality/tools/cauti-ltc/modules/implementation/long-term-modules/module3/mod3-facguide.html

No review details supplied.
