# Data-backed one-pager format

Use for a short argument where prose states the claim and a sibling CSV carries the evidence.

## Great instance

- Has one `h1` and no more than four `h2` sections.
- States the recommendation in the first screen.
- Ships `evidence.csv` next to the Markdown file.
- Keeps claims traceable to rows or cells in the CSV grid.

## Cut

- More than one recommendation.
- Buried caveats that change the claim.
- Inline data dumps that should be a CSV.

## Skeleton

```markdown
# <recommendation>

## Claim
<one paragraph with the point>

## Evidence
See `evidence.csv`.

## So what
<decision, change, or next action>

## Caveats
<limits that matter>
```

## Section prompts

- Put the argument in Markdown and the data in `evidence.csv`.
- Keep prose short enough for text anchors.
- Name the columns the reader should inspect.
- Do not copy every CSV row back into the page.

## Renderer moves

Catalog: ../building-artifacts.md#what-each-file-type-becomes - md doc reader sections; sibling csv grid.