# Move quality checks upstream of the bottleneck

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

---

## Move quality checks upstream of the bottleneck

ID: MHC-D-RESEARCH-9134 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/move-quality-checks-upstream-of-the-bottleneck

Do not spend the constraint on defects that cheaper checks can catch.

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

### Use when

- When scarce capacity repeatedly rejects preventable bad inputs.

### Avoid when

- Queueing equations have specific assumptions. Use them for directional reasoning and measurement design, not as exact forecasts for arbitrary multi-stage knowledge work.

### Explanation

Add lightweight validation before the bottleneck for recurring failure modes, while retaining the bottleneck's judgment on risks only it can assess.

### Example

Before specialist review, an automated schema check catches missing fields so expert time goes to semantic exceptions.

### Check

The constraint receives fewer preventable defects without merely moving hidden error downstream.

### Limits

- Queueing equations have specific assumptions. Use them for directional reasoning and measurement design, not as exact forecasts for arbitrary multi-stage knowledge work.

### Evidence and sources

- contextualizes: Kingman's heavy-traffic result underlies a queueing approximation in which waiting increases sharply with utilization and with variability in arrivals and service. — RS-94487D1BD4A53CF9. It is a single-server heavy-traffic approximation and should be used as directional intuition, not as an exact prediction for arbitrary multi-stage work. (Research note metadata and established heavy-traffic formulation)
- RS-94487D1BD4A53CF9: The Single Server Queue in Heavy Traffic — https://doi.org/10.1017/S0305004100036094

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/separate-touch-time-from-queue-time
