# Make queue overtaking an explicit exception

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: MHC-RPUB-20261011-9e4b62c5
Snapshot SHA-256: b97dfd5520e2cf31744978d7e824b94e55bd12d9a2bdef759b5bc69a963375e5
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Make queue overtaking an explicit exception

ID: MHC-D-RESEARCH-0173 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/make-queue-overtaking-an-explicit-exception

A queue with invisible shortcuts is not the queue people think they joined.

### Use when

- New easy requests continually jump ahead of older work.

### Avoid when

- FIFO is not appropriate for every clinical, safety or business priority. Use an explicit suitable policy rather than a mechanical universal rule.

### Explanation

People need an ordering rule they can understand. If comparable work normally follows arrival order, make each legitimate exception visible and give displaced work another review point.

### Checklist

- Define the normal ordering rule for comparable work.
- State which conditions legitimately override that order and who decides.
- Record why an item was overtaken and when it will be reconsidered, so exceptions do not become permanent neglect.

### Example

A support queue normally follows arrival order within a service class, while genuine outages use a visible urgent route. Personal familiarity is not a secret third route.

### Check

Could a waiting person understand why another item went first?

### Limits

- FIFO is not appropriate for every clinical, safety or business priority. Use an explicit suitable policy rather than a mechanical universal rule.

### Evidence and sources

- supports: FIFO preserves order through a defined queue instead of allowing arbitrary overtaking. — lei-fifo. Claim basis: professional_convention. Claim limit: Urgent or safety-critical exceptions require an explicit appropriate policy.
Source access: selected_html_passages; accessed on: 2026-09-17; inspected sections: ["Definition and controlled queue"].
Agent scope review, 2026-10-11: LEI FIFO describes a queue ordering convention. Transparent urgent exceptions are editorial design, not evidence that arrival order fits every safety or clinical task. (Definition)
- lei-fifo: First In, First Out (FIFO) — https://www.lean.org/lexicon-terms/first-in-first-out-fifo/

Review: agent · Agent editorial and scoped evidence review · 2026-10-11T18:12:50Z
Published: 2026-10-11T18:15:00Z
Related (useful_with): https://vedokrok.com/knowledge/which-unfinished-item-is-getting-older-without-moving