fixed detour stacking and improper option gating

2026-08-16 14:50:38 +02:00
parent bea880a999
commit 1ef1720bae
7 changed files with 427 additions and 37 deletions
@@ -32,9 +32,20 @@ title: Declarations
 <<declare $previous_winner = "" as string>>

 // Candidate lean. Three permanently-live readings of who the PC is; they are
-// not mutually exclusive and never resolve. Writers <<set>> these; no code
-// reads them. There is deliberately NO derived "winning candidate" variable —
-// see docs/candidate-system-implementation-plan.md §6.
+// not mutually exclusive and never resolve into a canonical identity.
+//
+// DESIGN DECISION 2026-08-16 — amends the "no code ever reads lean" guardrail in
+// docs/candidate-system-implementation-plan.md §6.1: scenes are meant to tilt
+// toward one reading and NPCs are meant to act on the current tilt, so that a
+// player who thinks they have settled on a path gets challenged on it in the
+// next scene. Reading lean through top_skill(...) is therefore sanctioned, as in
+// SC101_Asks_Candidate_Chevalier_Cassian_Thal_Talk. top_skill returns its FIRST
+// argument on a tie, which is why made_asset is passed first — the Made Asset
+// bias on an even score is deliberate, not an accident of argument order.
+//
+// What the amendment does NOT license: a stored winner. There is still no
+// $dominant_candidate, no ground-truth identity field, and nothing in save data
+// beyond these three integers. $winner above is scratch, recomputed per use.
 <<declare $self_lean_made_asset = 0 as number>>
 <<declare $self_lean_journalist = 0 as number>>
 <<declare $self_lean_inheritor  = 0 as number>>
@@ -102,5 +113,5 @@ title: Declarations
 <<declare $spoke_to_chevalier_cassian_thal = false as bool>>
 <<declare $spoke_to_bradford_kane = false as bool>>
 <<declare $inquired_about_cyprus = false as bool>>
-<<declare $declared_candidate_to_chevalier_cassian_thal = true as bool>>
+<<declare $declared_candidate_to_chevalier_cassian_thal = false as bool>>
 ===