# Start with the ordinary explanation, then check

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

---

## Start with the ordinary explanation, then check

ID: MHC-D-BRALI-0122 · Version: 0.1.0 · Kind: heuristic
Source: https://vedokrok.com/knowledge/start-with-the-ordinary-explanation-then-check

Unusual stories attract attention. Before adopting one, ask what usually produces the same observation in similar situations, then look for evidence that would justify moving away from that ordinary explanation.

Knowledge source release: MHC-RPUB-20261112-20287590
Source corpus commit: 20287590ddd3999b7492df232822b6a0f7d114b1
Source manifest SHA-256: 2a987660d12de0ce2bde77a421424f7762af1ff77872ef41093fecc33db74a95
Source projection SHA-256: 2807da39bbe6a3dee2db32a76675ac5185f5a33e8b0a5cdd0c22a4731f3378a0

### Use when

- An observation has both common and unusual plausible explanations.

### Avoid when

- Common explanations are not automatically correct, and rare events do happen. This is a starting-order heuristic, not permission to dismiss anomalies.

### Explanation

Unusual stories attract attention. Before adopting one, ask what usually produces the same observation in similar situations, then look for evidence that would justify moving away from that ordinary explanation.

### Steps

1. Describe the observation without interpretation.
2. List one or two ordinary explanations based on similar cases or known failure modes.
3. List the unusual explanation you are considering.
4. Ask what evidence would distinguish them.
5. Update toward the unusual explanation only when the evidence earns it.

### Check

The explanation reflects both prior plausibility and case-specific evidence.

### Limits

- Common explanations are not automatically correct, and rare events do happen. This is a starting-order heuristic, not permission to dismiss anomalies.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-e5714854ac1691a5f438. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/expect-the-ordinary-occams-razor.json)
- FP-BRALI-SRC-e5714854ac1691a5f438: Consider What Normally Happens in Similar Situations Before Assuming an Unusual Explanation — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/expect-the-ordinary-occams-razor.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
