# TellTale Report Contract Checklist v0.1

Use this to judge whether a TellTale report is actually ready.

## Required sections
A TellTale report should include:
1. what was analyzed
2. coverage / confidence
3. source provenance
4. chronological incident summary
5. main findings
6. evidence excerpts / trace anchors
7. uncertainties
8. recommended interpretation / next steps

## Required qualities
- coverage status is explicit
- partial / uncertain history is not hidden
- primary signals are separated from secondary warnings
- the incident summary reads like a short story of trust failing, not a flat flag list
- evidence excerpts support the findings without overexplaining the internals
- uncertainty is named plainly
- next steps are practical and bounded

## Good report test
A reviewer should be able to answer these three questions quickly:
- What happened?
- How trustworthy is the source?
- What should I do next?

## Bad report test
A report fails if it:
- hides incompleteness
- collapses control and pathology together
- buries the incident sequence
- mixes secondary noise with primary findings
- claims certainty where the source is partial

## Alignment note
This checklist should match the renderer output, the demo shell, and the sample diagnostic report.