Adds design/debrief.md, a design note for the post-mission debrief and scoring, a sibling to the objectives note (#289), and links it from contracts-and-raids §7.
What it settles:
- A mission record: structured events emitted where log lines are. They cover objective steps and methods, resources spent, damage taken, props destroyed with value and owner, people harmed, systems hacked, alarms, sightings and claims, each with its witnesses.
- Four layers: objectives, resources and collateral are facts, never graded. Reputation is interpretation by pluggable, data-driven scorers, each emitting several axes, none good or bad in itself.
- Collateral scales with value, and site wealth decides prop value. "Smash things" can be a major. Being seen and identified is a first-class goal, and claims such as taunts feed attribution.
- Perception: scorers judge only what their audience could know: seen versus identified, surviving records, and claims.
- Flow: endings and debts to settlement, tallies to lifetime counters, scorer output to standing facts per audience (the existing
standingcrate), and the flake mark from backing out. - The debrief screen, plus determinism, hidden state, and a first slice on the facility.
Builds on:
🤖 Generated with Claude Code