# Write a bug report someone can use

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

---

## Write a bug report someone can use

ID: MHC-D-BRALI-0015 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/write-a-bug-report-someone-can-use

A symptom is an observation. Its cause is still a hypothesis.

### Use when

- You need another person to investigate a reproducible work-system problem.

### Explanation

Give the investigator a path from the conditions to what you actually saw. Separate expected behaviour, observed behaviour and your suspected explanation. If the failure happened once, say so; do not invent reliable reproduction. The acceptance check describes the behaviour a fix must restore.

### Template

Context and version: ___.
Smallest reproduction steps: ___.
Expected result: ___.
Observed result and evidence: ___.
Suspected cause, if any: ___.
Acceptance check for the fix: ___.

### Example

A browser shows an old address after saving. You record the version and one failed attempt; caching remains a suspicion.

### Check

Can another person distinguish what happened, what should happen and what still needs testing?

### Limits

- Remove credentials and unnecessary personal or customer data from screenshots, logs and examples.

### Evidence and sources

- contextualizes: This report template keeps expected behaviour, observed behaviour and suspected cause in separate fields. — FP-BRALI-0015. Editorial design and source provenance only. No causal benefit, percentage improvement or validated intervention is claimed. Access: full_structured_record; 2026-10-11. Registered first-party project text; template provenance, not an efficacy study. (Selected template fields)
- FP-BRALI-0015: Write a bug report someone can use — Brali source record — https://github.com/Brali-LifeOS/brali-lifeos.github.io/blob/63acf81e48f428c0e769ffa9d26d9421fd575e6a/data/life-os-content/qa-clear-feedback-templates.json

Review: agent · Agent editorial and scoped evidence review · 2026-10-11T19:01:14Z
Published: 2026-10-11T19:10:00Z
Related (use_before): https://vedokrok.com/knowledge/separate-severity-from-priority