# Report Contract

## Goal

Write a post-run account that sounds like a real player talking through the session they just finished. A reader should be able to follow what kind of run it was, how it developed, what decisions mattered, and how it felt to play.

## Tone

- first person
- natural and concrete
- human-sounding, not robotic
- allowed to contain emotion and judgment
- not written like a design memo
- not written like assistant boilerplate
- do not say things like "as an AI", "here is the report", or "below is a summary"

## Must cover

- the executable target used, such as `darwin-arm64`
- the launch command, class, seed, locale, and final result
- pathing decisions
- most of the important combat actions
- key decisions in rewards, events, shops, and rest sites
- how the deck, relics, and consumables changed the way the run played
- turning points
- a retrospective on that exact run

## Do not include

- suggestions
- improvement proposals
- "the developer should..."
- action items
- design critique
- a bug triage list

## Recommended structure

### Run setup

One short paragraph covering platform target, command, class, seed, locale, and result.

### What happened

Tell it in chronological order. You can split by act or by phase, but the body should stay narrative rather than turning into hollow bullet points. Cover most major actions and choices from the real run.

### Experience and retrospective

Look back on how the run actually came together, where it swung, what felt tense, and which choices proved right or wrong in practice. Keep it grounded in that run. Do not turn this section into advice.