# Investigate before you explain

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

Build an explanation from observations, timelines and evidence gaps before committing to a story about cause or motive.
Collection kind: collection
Source: https://vedokrok.com/collections/investigate-before-you-explain
Version: 1.0.0

---

## Reconstruct a timeline from artifacts

ID: MHC-D-BRALI-0120 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/reconstruct-a-timeline-from-artifacts

Memory is useful for leads, not timestamps. When sequence matters, rebuild the event from logs, messages, files and other artifacts, then mark gaps instead of unconsciously filling them.

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

### Use when

- You need to understand what happened in an incident, process failure or disputed sequence of events.

### Avoid when

- Artifacts can be incomplete, clocks can differ and logs can be wrong. A reconstructed timeline is evidence organization, not automatic proof of motive or causality.

### Explanation

Memory is useful for leads, not timestamps. When sequence matters, rebuild the event from logs, messages, files and other artifacts, then mark gaps instead of unconsciously filling them.

### Steps

1. Define the start and end of the event you are reconstructing.
2. Collect timestamped artifacts from the relevant systems and people.
3. Place observed events in order and keep source links or identifiers with each one.
4. Mark inferred events and gaps separately from observed events.
5. Use the timeline to generate specific questions or tests for the remaining uncertainty.

### Check

The sequence separates observed artifacts, inference and unresolved gaps.

### Limits

- Artifacts can be incomplete, clocks can differ and logs can be wrong. A reconstructed timeline is evidence organization, not automatic proof of motive or causality.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-841bd9d3c7df43acc324. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/scenario-reconstruction-coach.json)
- FP-BRALI-SRC-841bd9d3c7df43acc324: Recreate Past Events in Your Mind to Understand What Happened and Why — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/scenario-reconstruction-coach.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (useful_with): https://vedokrok.com/knowledge/record-observation-before-explanation
Related (useful_with): https://vedokrok.com/knowledge/start-with-the-ordinary-explanation-then-check
Related (useful_with): https://vedokrok.com/knowledge/draw-the-evidence-chain-and-mark-the-gaps
Related (useful_with): https://vedokrok.com/knowledge/map-risk-before-committing
Related (useful_with): https://vedokrok.com/knowledge/consider-the-opposite-before-committing
Related (use_before): https://vedokrok.com/knowledge/draw-the-evidence-chain-and-mark-the-gaps

---

## Record observation before explanation

ID: MHC-D-BRALI-0121 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/record-observation-before-explanation

The first story you tell about a detail can become sticky. Capture what you actually observed before adding the interpretation, then write the question that would distinguish competing explanations.

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

### Use when

- A detail may matter later in debugging, research, investigation or a difficult conversation.

### Avoid when

- Not every tiny detail deserves logging. Record information only when it can change a decision, explanation or next test.

### Explanation

The first story you tell about a detail can become sticky. Capture what you actually observed before adding the interpretation, then write the question that would distinguish competing explanations.

### Template

Observed: ___.
Context: ___.
Possible explanations: ___.
What would distinguish them: ___.

### Check

The note makes it possible to recover the observation without inheriting the first interpretation as fact.

### Limits

- Not every tiny detail deserves logging. Record information only when it can change a decision, explanation or next test.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-dc872b4ad5df1102b973. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/detective-observation-notebook.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-ed91c3da2eb45c005f3a. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/spot-overlooked-details.json)
- FP-BRALI-SRC-dc872b4ad5df1102b973: Keep a Dedicated Notebook Where You Record Observations, Questions, and Reflections — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/detective-observation-notebook.json
- FP-BRALI-SRC-ed91c3da2eb45c005f3a: Focus on the Smallest Details That Might Seem Insignificant but Could Be of Great — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/spot-overlooked-details.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (use_before): https://vedokrok.com/knowledge/start-with-the-ordinary-explanation-then-check

---

## 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

---

## Draw the evidence chain and mark the gaps

ID: MHC-D-BRALI-0123 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/draw-the-evidence-chain-and-mark-the-gaps

A conclusion can look inevitable because several assumptions are compressed into one sentence. Expand the chain: observation, inference, intermediate claim, conclusion. Mark which links have evidence and which are only plausible.

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

### Use when

- A complex explanation or diagnosis depends on several inferential steps.

### Avoid when

- A logical-looking sequence can still be based on false premises or omitted alternatives. Structure does not establish truth by itself.

### Explanation

A conclusion can look inevitable because several assumptions are compressed into one sentence. Expand the chain: observation, inference, intermediate claim, conclusion. Mark which links have evidence and which are only plausible.

### Steps

1. Write the final conclusion.
2. Work backward to the observations or premises it depends on.
3. Draw each inferential link explicitly.
4. Mark links as observed, sourced, inferred or unknown.
5. Choose the weakest important link for the next verification step.

### Check

The argument exposes its weakest important link and the next check needed there.

### Limits

- A logical-looking sequence can still be based on false premises or omitted alternatives. Structure does not establish truth by itself.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-a8b55a8982e01c03671d. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/logical-chain-builder.json)
- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-94fa6ed8d5e9b2731784. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/sherlock-holmes-analysis-method.json)
- FP-BRALI-SRC-a8b55a8982e01c03671d: Create a Logical Sequence of Events or Thoughts to See How They Are Connected — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/logical-chain-builder.json
- FP-BRALI-SRC-94fa6ed8d5e9b2731784: Look at a Situation from All Angles, Consider All Evidence, and Eliminate the Impossible — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/sherlock-holmes-analysis-method.json

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

---

## Map possible causes before picking one

ID: MHC-D-BRALI-0102 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/map-possible-causes-before-picking-one

A cause diagram is useful because it delays the jump from symptom to favourite explanation. List plausible cause families, attach observations, and mark what is still only a hypothesis before you decide what to test.

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

### Use when

- A recurring problem has several plausible causes and the team is converging too quickly on one story.

### Avoid when

- A fishbone diagram is an organizing aid, not proof of causality. Complex failures can have multiple contributing causes.

### Explanation

A cause diagram is useful because it delays the jump from symptom to favourite explanation. List plausible cause families, attach observations, and mark what is still only a hypothesis before you decide what to test.

### Steps

1. Write the observed problem as specifically as possible.
2. Create cause families that fit the system, not a generic template by habit.
3. Add candidate causes under each family.
4. Mark which candidates have evidence, which are assumptions and which can be tested.
5. Choose the cheapest discriminating test before choosing a “root cause.”

### Check

At least two plausible explanations are represented and the next test can distinguish among them.

### Limits

- A fishbone diagram is an organizing aid, not proof of causality. Complex failures can have multiple contributing causes.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-b4a44f8ab33e3250d5b2. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/fishbone-diagram-root-cause.json)
- FP-BRALI-SRC-b4a44f8ab33e3250d5b2: Use a Fishbone Diagram to Identify the Root Causes of a Problem — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/fishbone-diagram-root-cause.json

Review: agent · Agent editorial and scoped source review · 2026-11-12T18:37:40Z
Published: 2026-11-12T18:37:40Z
Related (useful_with): https://vedokrok.com/knowledge/simplify-before-you-automate-or-delegate
Related (useful_with): https://vedokrok.com/knowledge/benchmark-the-mechanism-not-the-surface
Related (useful_with): https://vedokrok.com/knowledge/reverse-the-default-to-find-an-option
Related (useful_with): https://vedokrok.com/knowledge/use-the-ideal-outcome-to-reveal-costs
Related (useful_with): https://vedokrok.com/knowledge/reuse-a-proven-resource-before-adding-one
Related (useful_with): https://vedokrok.com/knowledge/put-buffer-where-variation-hurts
Related (useful_with): https://vedokrok.com/knowledge/change-one-parameter-then-observe
Related (useful_with): https://vedokrok.com/knowledge/reconstruct-a-timeline-from-artifacts

---

## Consider the opposite before committing

ID: MHC-D-BRALI-0184 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/consider-the-opposite-before-committing

When you already feel convinced, deliberately generate one plausible case that would support the other conclusion. The point is not to reverse every judgment; it is to see whether your current view survives a concrete challenge.

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

### Use when

- A meaningful judgment may be vulnerable to one-sided evidence search or biased assimilation.

### Avoid when

- Do not turn this into endless doubt about routine choices. The method is a bias check, not a guarantee of debiasing.

### Explanation

When you already feel convinced, deliberately generate one plausible case that would support the other conclusion. The point is not to reverse every judgment; it is to see whether your current view survives a concrete challenge.

### Steps

1. Write the current conclusion in one sentence.
2. Generate a plausible explanation, evidence pattern or outcome that would make the opposite conclusion reasonable.
3. Ask what evidence would distinguish the two.
4. Check whether the decision changes if that alternative is true.
5. Proceed when the challenge reveals no material missing fact, or gather the missing evidence.

### Check

You have either found a material counter-case to investigate or shown why the current conclusion still survives the challenge.

### Limits

- Do not turn this into endless doubt about routine choices. The method is a bias check, not a guarantee of debiasing.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-9776c24b4d01d339accd. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/consider-the-opposite.json)
- FP-BRALI-SRC-9776c24b4d01d339accd: Before You Commit to a Judgment, Consider the Opposite — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/consider-the-opposite.json

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

---

## Map risk before committing

ID: MHC-D-BRALI-0140 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/map-risk-before-committing

Risk thinking is useful when it changes the decision. Name plausible failure modes, likelihood only at the precision you can justify, impact, detectability and what would reduce exposure.

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

### Use when

- A meaningful decision has downside that should be understood before commitment.

### Avoid when

- Do not manufacture precise probabilities when evidence does not support them. High-stakes risk assessment may need domain specialists.

### Explanation

Risk thinking is useful when it changes the decision. Name plausible failure modes, likelihood only at the precision you can justify, impact, detectability and what would reduce exposure.

### Template

Failure mode: ___.
Why plausible: ___.
Impact if it happens: ___.
Early signal: ___.
Mitigation or fallback: ___.
Residual risk I am accepting: ___.

### Check

The important downside, signal and response are explicit enough to affect the choice.

### Limits

- Do not manufacture precise probabilities when evidence does not support them. High-stakes risk assessment may need domain specialists.

### Evidence and sources

- contextualizes: First-party source of this practical exercise. — FP-BRALI-SRC-d1b0405edcc45d4aa06f. Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding. (data/life-os-content/decision-risk-canvas.json)
- FP-BRALI-SRC-d1b0405edcc45d4aa06f: Before Jumping into Something, Think About What Could Go Wrong and How Likely It — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/decision-risk-canvas.json

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