coulomb/clay-borg
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
clay-borg/scenarios/ground/gr-d01-darvo-trigger.yaml

45 lines
1,013 B
YAML
Raw Normal View History

T08 iter 2: Reveal, Resolve, End; relations and the DARVO trigger Round machinery, system-driven (GR-R04/R06/R08): - GR-R06 fixed step order with GR-R07 Lead-first ordering inside a step. Steps 1 (GROUND), 3 (DARVO stages), 4 (INVESTIGATE) and 6 (SOLVE) are not implemented yet; their Actions resolve as no-ops and no scenario claims coverage of them. - SUPPORT GR-A03/A04/A05 and ATTACK GR-A06..A09, with relation formation, flip and break per GR-L01/L03/L04 and Protection cancellation. - GR-R08 End: DARVO trigger at Stress 5 in Lead order, Lead rotation, Round advance, per-round flags cleared. - Stress clamps 0-5 on every application, the U2 default, so a mid-round spike that is reduced before End does not trigger DARVO. Two consent-dependent rules are deliberately left out because they need a decision command rather than a default: Bond formation (GR-L02) and the target's flip-or-break choice on Support-through-Rivalry (GR-A05). Both are noted in code and covered by a provisional scenario. Fixes a defect in the T07 scaffold: relations were keyed by a tuple, which JSON cannot use as an object key, so state_hash would have panicked on any state holding a relation. Relation keys are now a Pair newtype serialized as "a-b", with a regression test. setup.patch may now create a final key so scenarios can seed open-ended maps; a typo anywhere earlier in the path is still an error. 8 scenarios pass, 28 rules covered; 17 tests, fmt/clippy green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 02:19:34 +02:00
scenario: ground/gr-d01-darvo-trigger
description: >
DARVO trigger: a player who ends the round at Stress 5 with the marker
OFF is set to DENY (GR-D01, GR-R08). Stress clamps at 5 on every
application (GR-F01 under the U2 default).
covers: [GR-D01, GR-R08, GR-F01]
provisional: true
T08: give provisional defaults an owner, a date, and a visible age Five scenarios encoded U-item defaults with no owner and no review date, so they could shape the kernel indefinitely while looking handled. Each now carries provisional_owner and provisional_raised, and the runtime's ScenarioFile learned both fields (deny_unknown_fields meant adding them to YAML alone would have failed every scenario -- the parser had to agree). make coverage reports every provisional item with its owner and age in days, warns on any with no owner, and warns past 30 days. It WARNS rather than breaking the build, on purpose: the ruling is ground-game's to make and the kernel cannot make it for them. What the loop can enforce is that evidence files list them, which is now stated in GroundRules. rule-coverage --self-test gained an assertion that every provisional item has both fields, so the next one added without them fails a command rather than passing quietly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 09:29:40 +02:00
provisional_owner: ground-game
provisional_raised: 2026-07-31
T08 iter 2: Reveal, Resolve, End; relations and the DARVO trigger Round machinery, system-driven (GR-R04/R06/R08): - GR-R06 fixed step order with GR-R07 Lead-first ordering inside a step. Steps 1 (GROUND), 3 (DARVO stages), 4 (INVESTIGATE) and 6 (SOLVE) are not implemented yet; their Actions resolve as no-ops and no scenario claims coverage of them. - SUPPORT GR-A03/A04/A05 and ATTACK GR-A06..A09, with relation formation, flip and break per GR-L01/L03/L04 and Protection cancellation. - GR-R08 End: DARVO trigger at Stress 5 in Lead order, Lead rotation, Round advance, per-round flags cleared. - Stress clamps 0-5 on every application, the U2 default, so a mid-round spike that is reduced before End does not trigger DARVO. Two consent-dependent rules are deliberately left out because they need a decision command rather than a default: Bond formation (GR-L02) and the target's flip-or-break choice on Support-through-Rivalry (GR-A05). Both are noted in code and covered by a provisional scenario. Fixes a defect in the T07 scaffold: relations were keyed by a tuple, which JSON cannot use as an object key, so state_hash would have panicked on any state holding a relation. Relation keys are now a Pair newtype serialized as "a-b", with a regression test. setup.patch may now create a final key so scenarios can seed open-ended maps; a typo anywhere earlier in the path is still an error. 8 scenarios pass, 28 rules covered; 17 tests, fmt/clippy green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 02:19:34 +02:00
seed: 42
setup:
players: 3
preset: standard-3p
patch:
"lead": 0
"players.1.stress": 4
commands:
- actor: P1
cmd: select_action
args: { action: ATTACK, target: P2 }
- actor: P2
cmd: select_action
T08 iter 3: GROUND modes, INVESTIGATE, SOLVE Fills in resolution steps 1, 4 and 6 (GR-R06): - GR-R05 mode choice: a player who revealed GROUND picks GR/OU/ND after Reveal. Resolution refuses to start while any revealed GROUND lacks a mode, and only that player may choose it. - GR-A10 GROUND-GR: self -2 Stress and Freedom readied. - GR-A01 INVESTIGATE: reveal the chosen hidden non-Denied Problem, then draw one Solution; the draw still happens when nothing is revealable. - GR-A02 SOLVE: spend a Solution of the Problem's suit and claim it; a later resolver the same round spends nothing, per Lead order. - GR-A13 tightened: INVESTIGATE must target a hidden Problem, SOLVE a face-up non-Denied one. Previously any existing Problem was accepted. Deck exhaustion (U4) reshuffles the discard, seeded from the game seed and round so validate stays a pure function of state. The resulting order travels inside DeckReshuffled, so replay never re-derives it. Still pending, each because it needs its own decision command rather than a default: GROUND-OU and GROUND-ND three-way choices (GR-A11/A12) and the DARVO stage machine (GR-D02..D07). No scenario claims coverage of them. Filler picks in existing scenarios moved from GROUND to INVESTIGATE: GROUND now has a real Stress effect, which was polluting the Support and Attack assertions. 11 scenarios pass, 34 rules covered; 17 tests, fmt/clippy green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 02:23:09 +02:00
args: { action: ATTACK, target: P3 }
T08 iter 2: Reveal, Resolve, End; relations and the DARVO trigger Round machinery, system-driven (GR-R04/R06/R08): - GR-R06 fixed step order with GR-R07 Lead-first ordering inside a step. Steps 1 (GROUND), 3 (DARVO stages), 4 (INVESTIGATE) and 6 (SOLVE) are not implemented yet; their Actions resolve as no-ops and no scenario claims coverage of them. - SUPPORT GR-A03/A04/A05 and ATTACK GR-A06..A09, with relation formation, flip and break per GR-L01/L03/L04 and Protection cancellation. - GR-R08 End: DARVO trigger at Stress 5 in Lead order, Lead rotation, Round advance, per-round flags cleared. - Stress clamps 0-5 on every application, the U2 default, so a mid-round spike that is reduced before End does not trigger DARVO. Two consent-dependent rules are deliberately left out because they need a decision command rather than a default: Bond formation (GR-L02) and the target's flip-or-break choice on Support-through-Rivalry (GR-A05). Both are noted in code and covered by a provisional scenario. Fixes a defect in the T07 scaffold: relations were keyed by a tuple, which JSON cannot use as an object key, so state_hash would have panicked on any state holding a relation. Relation keys are now a Pair newtype serialized as "a-b", with a regression test. setup.patch may now create a final key so scenarios can seed open-ended maps; a typo anywhere earlier in the path is still an error. 8 scenarios pass, 28 rules covered; 17 tests, fmt/clippy green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 02:19:34 +02:00
- actor: P3
cmd: select_action
T08 iter 3: GROUND modes, INVESTIGATE, SOLVE Fills in resolution steps 1, 4 and 6 (GR-R06): - GR-R05 mode choice: a player who revealed GROUND picks GR/OU/ND after Reveal. Resolution refuses to start while any revealed GROUND lacks a mode, and only that player may choose it. - GR-A10 GROUND-GR: self -2 Stress and Freedom readied. - GR-A01 INVESTIGATE: reveal the chosen hidden non-Denied Problem, then draw one Solution; the draw still happens when nothing is revealable. - GR-A02 SOLVE: spend a Solution of the Problem's suit and claim it; a later resolver the same round spends nothing, per Lead order. - GR-A13 tightened: INVESTIGATE must target a hidden Problem, SOLVE a face-up non-Denied one. Previously any existing Problem was accepted. Deck exhaustion (U4) reshuffles the discard, seeded from the game seed and round so validate stays a pure function of state. The resulting order travels inside DeckReshuffled, so replay never re-derives it. Still pending, each because it needs its own decision command rather than a default: GROUND-OU and GROUND-ND three-way choices (GR-A11/A12) and the DARVO stage machine (GR-D02..D07). No scenario claims coverage of them. Filler picks in existing scenarios moved from GROUND to INVESTIGATE: GROUND now has a real Stress effect, which was polluting the Support and Attack assertions. 11 scenarios pass, 34 rules covered; 17 tests, fmt/clippy green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 02:23:09 +02:00
args: { action: INVESTIGATE, problem: 3 }
T08 iter 2: Reveal, Resolve, End; relations and the DARVO trigger Round machinery, system-driven (GR-R04/R06/R08): - GR-R06 fixed step order with GR-R07 Lead-first ordering inside a step. Steps 1 (GROUND), 3 (DARVO stages), 4 (INVESTIGATE) and 6 (SOLVE) are not implemented yet; their Actions resolve as no-ops and no scenario claims coverage of them. - SUPPORT GR-A03/A04/A05 and ATTACK GR-A06..A09, with relation formation, flip and break per GR-L01/L03/L04 and Protection cancellation. - GR-R08 End: DARVO trigger at Stress 5 in Lead order, Lead rotation, Round advance, per-round flags cleared. - Stress clamps 0-5 on every application, the U2 default, so a mid-round spike that is reduced before End does not trigger DARVO. Two consent-dependent rules are deliberately left out because they need a decision command rather than a default: Bond formation (GR-L02) and the target's flip-or-break choice on Support-through-Rivalry (GR-A05). Both are noted in code and covered by a provisional scenario. Fixes a defect in the T07 scaffold: relations were keyed by a tuple, which JSON cannot use as an object key, so state_hash would have panicked on any state holding a relation. Relation keys are now a Pair newtype serialized as "a-b", with a regression test. setup.patch may now create a final key so scenarios can seed open-ended maps; a typo anywhere earlier in the path is still an error. 8 scenarios pass, 28 rules covered; 17 tests, fmt/clippy green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-31 02:19:34 +02:00
- actor: SYSTEM
cmd: reveal
- actor: SYSTEM
cmd: resolve
- actor: SYSTEM
cmd: end_round
expect:
events:
- kind: StressSet
player: 1
stress: 5
- kind: DarvoTriggered
player: 1
state:
"players.1.stress": 5
"players.1.darvo": Deny
"round": 2
rejects: []
Reference in a new issue Copy permalink