# Check whether the tool, proxy or story is answering the real question

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

Expose substituted questions, familiar tools, automated recommendations and causal stories before they become the explanation by default.
Collection kind: collection
Source: https://vedokrok.com/collections/check-whether-the-tool-proxy-or-story-is-answering-the-real-question
Version: 1.0.0

---

## Illusion of explanatory depth

ID: MHC-D-99DBC1003BAB · Version: 0.2.0 · Kind: concept
Source: https://vedokrok.com/knowledge/illusion-of-explanatory-depth

Understanding often survives until the second sentence of the explanation.

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

### Avoid when

- Useful understanding does not require expert-level detail. The required depth depends on the decision or task.

### Explanation

People can believe they understand how a familiar system works in more detail than they can actually explain. Familiar use, labels and visible outcomes can create a sense of knowledge without a causal model.

### Steps

1. Explain the mechanism step by step without looking it up.
2. Mark the first step where you replace a mechanism with a label such as 'the system handles it'.

### Example

You say you understand how a Wi-Fi connection is established. Explaining what the device, access point, authentication and network each do reveals exactly where the model becomes vague.

### Check

Can I predict what would happen if one component changed or failed?

### Limits

- Useful understanding does not require expert-level detail. The required depth depends on the decision or task.

### Evidence and sources

- supports: People can rate their understanding of a familiar mechanism higher before attempting a detailed explanation than after. — FP-CB-SRC-83. Selected methods and results address explanations of mechanisms. The Wi-Fi case is an authored example. The required explanation depth depends on the task. (Introduction and Studies 1–4)
- FP-CB-SRC-83: Rozenblit and Keil, The misunderstood limits of folk science — https://pmc.ncbi.nlm.nih.gov/articles/PMC3062901/

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

---

## Additive bias

ID: MHC-D-7D374C8F3DE7 · Version: 0.2.0 · Kind: concept
Source: https://vedokrok.com/knowledge/additive-bias

When something is wrong, our first design instinct often arrives carrying an extra feature.

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

### Avoid when

- Subtraction is not inherently elegant or correct. Some problems genuinely require new capacity, safeguards or information.

### Explanation

When improving an object or process, people often generate additive changes more readily than subtractive ones. Useful solutions can therefore remain hidden behind an assumption that improvement means adding something.

### Steps

1. For every add-option, generate one remove, combine or simplify option.
2. Ask which component exists because it is necessary now rather than because it was inherited.

### Example

A settings page feels confusing, so the team proposes another explanation panel. Removing two obsolete choices solves the actual problem with less interface to maintain.

### Check

What could I remove while preserving the outcome I care about?

### Limits

- Subtraction is not inherently elegant or correct. Some problems genuinely require new capacity, safeguards or information.

### Evidence and sources

- supports: Across the reported tasks, participants were more likely to overlook useful subtractive changes under particular search conditions. — FP-CB-SRC-91. Selected methods and results on design choices. The settings example illustrates a case where subtraction might help and gives no default recommendation to remove safeguards. (Study overview and experiments on additive and subtractive transformations)
- FP-CB-SRC-91: Adams et al., People systematically overlook subtractive changes — https://www.nature.com/articles/s41586-021-03380-y

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