diff --git a/docs/scenarios/CLEAN_GROUND.md b/docs/scenarios/CLEAN_GROUND.md index ca9ab58..29184b6 100644 --- a/docs/scenarios/CLEAN_GROUND.md +++ b/docs/scenarios/CLEAN_GROUND.md @@ -9,7 +9,7 @@ | | | |---|---| -| **Version** | **v0.9**, 13 September 2026 | +| **Version** | **v0.10**, 13 September 2026 | | **Can it be run?** | **Yes, from this document alone.** A GM with this file and the compendium can run it end to end. | | **Is it convention-ready?** | **No.** It has never been played by human beings, and there is no print pack. | | **Playtesting** | Three desk passes, all fixes applied: `CLEAN_GROUND_PLAYTEST_1.md` (GM chair, seed 4271), `_2.md` (Act Four stress, seed 9314), `_3.md` (player chair, contrarian, seed 5580). Twenty-three fixes plus one post-pass. | @@ -724,11 +724,26 @@ losing. Both of the first two are live in this scenario. something. This row is not, and a GM who reads "2.31" as "a bruising fight" is reading the one outcome the table is least likely to deliver. - **It is decided by round five.** If the party puts even one of the three down in the - first five rounds the wipe rate falls from **58.5% to 19.7%**; if they put down two it is - **zero wipes in the 84 fights that got there**. They usually cannot — 68% of fights reach - round five with none of the three down. A dead one stops attacking and a half-dead one - does not, so the fight either tips early or grinds them flat. + **It is decided by the first disabling blow, and that lands in round two.** Both sides + go down at half their maximum hit points — the same rule in both directions — so every + disable removes an attacker, thins the return fire, and makes the next disable likelier. + Nothing pulls the fight back toward the middle once it has tipped. **Round five is where + that becomes legible; round two is where it happens.** + + | Measured | Party strikes first | Then wipes | If it does not | + |---|---|---|---| + | **Three of the column vs the cut** | 50.3% (mean round 1.8) | **25.5%** | **65.5%** — a swing of **40** | + | Six of the column vs the full six | 54.1% (mean round 1.3) | 7.8% | 23.2% — a swing of 15.4 | + + First blood is very nearly a coin toss, and in the cut it is worth **forty points of wipe + rate**. Against the full six it is worth a third of that, because one fighter is a sixth + of that line and a quarter of the cut. **This is a property of the cut, not of the + column.** + + *Recorded in `tools/first-blood-baseline.json` and re-checked on every build by + `check-firstblood`; read it with `node tools/first-blood.mjs`. Earlier drafts of this + paragraph carried a swing of 43 from a single seed, which was high by more than its own + seed-to-seed noise — the figures above are three seeds and are the ones of record.* At four players, **any** violence against the column is a party-ending decision. **Say the shape aloud, not the average:** "nearly half of all parties die" is the honest @@ -845,6 +860,18 @@ not a second definition of the sheet. Not the "(before)" sheets. This is the job, and it wants people who have been inducted. +> ⚠ **THE DECLARED CAST IS LOAD-BEARING ON THE BUILD.** The `` comment above +> is read by two guards. **`check-rollable`** holds every skill the acts name to these six, +> and **`check-firstblood`** holds a recorded measurement of this scenario's own encounter +> against them. **EXPOSURE's whole table is measured against these six as well.** +> +> So changing who is cast is not a cosmetic edit. It invalidates the exposure figures and it +> will fail the build. **The fix is to re-record, not to revert** — `node tools/first-blood.mjs +> --update`, and re-run EXPOSURE's own published command — and then to re-read the prose +> around both, because the sentences quote ratios that move with the numbers. That coupling +> is deliberate: it converts a table that would otherwise go quietly stale into one that +> announces it. + | | Agent | Lane | The one thing they are for | |---|---|---|---| | 1 | **Dominic Ashcroft** `pc_ashcroft` | Coherence | He has been thin before and knows what it costs |