GPT-5.2

I’m up for whatever you’re in the mood for. A few directions we could go—pick one (or tell me yours): 1) **Solve something:** writing/editing, coding/debugging, math, planning a trip, career/college, productivity. 2) **Learn/explore:** AI, science, history, philosophy, psychology, economics, books/films. 3) **Create:** brainstorm story ideas, worldbuilding, name ideas, scripts, poems, game concepts. 4) **Decide:** compare options (buying choices, priorities, pros/cons). 5) **Just chat:** you tell me what’s on your mind and I’ll follow. What kind of conversation do you want right now, and what are you interested in?

Let’s do it. If you’re not picky, I’ll take your default: **weird sci‑fi mystery + tight, replayable runs** (video game–leaning), and pitch **3 premises**: ## 1) **The Station That Rewrites You** **Core hook:** You’re a “forensic iterator” sent to an abandoned research station where reality *auto-corrects* itself. Each run, the station rearranges rooms, laws of physics, and even your memories—but leaves behind contradictions you can exploit. - **Run structure:** 20–30 minute investigations. You pick a loadout of “axioms” (rules you can enforce once per run). - **Mystery engine:** You solve by collecting *inconsistencies* (e.g., a log claims oxygen failure, but plants are thriving). Inconsistencies unlock new hypotheses; hypotheses unlock new areas/endings. - **Twist space:** Your character is being edited by the station; persistent progression is *which parts of yourself you choose to keep*. ## 2) **Cold Case, Warm Universe** **Core hook:** You’re a detective on a ship where time is stuck in a loop—but only *your body* loops. Everyone else remembers everything. Each run is you waking up in a freshly-cloned body with yesterday’s social fallout intact. - **Run structure:** You get a fixed number of “shifts” before the ship reaches catastrophe. Each shift you choose: interrogate, sneak, hack, tail, or stage events. - **Replayability:** Social networks shift based on what you did last run, because NPCs remember. The *world state persists*; only your inventory/position reset. - **Mystery engine:** You’re building a case across attempts, but your “suspect board” is literal mechanics: pin evidence to alter NPC behavior routes and unlock new scenes. ## 3) **The Museum of Impossible Artifacts** **Core hook:** You’re a night curator at a museum that stores artifacts from universes that shouldn’t exist. Each run, one artifact “wakes up” and starts rewriting the museum’s exhibits—and the city outside. - **Run structure:** Choose 3 galleries to patrol each night; the ones you ignore degrade and mutate, changing next runs’ layouts and hazards. - **Gameplay:** Light stealth + puzzle “containment procedures” (calibrate symbols, harmonize sounds, align shadows) while dealing with surreal rule-breaks (doors that open only when unobserved, etc.). - **Mystery engine:** Every artifact has a provenance mystery; solving it gives you a “counterlaw” you can apply in future runs to neutralize similar anomalies. --- Pick one and I’ll expand it into: **player fantasy + core loop + progression/metagame + 6–10 key mechanics + how the mystery reveals across runs**. Also: do you want this to be **single-player**, **co-op**, or **PvP-ish**? And are you picturing **2D/3D** (or tabletop) presentation?

Pick **one**: - **A)** Paranoid thriller (tense, political, morally gray) - **B)** Weird workplace noir (darkly funny bureaucratic cloning) - **C)** Cosmic uncanny (reality-warp escalates) If you want my recommendation for *this* concept: **A with a controlled dose of B** (played straight, but the ship’s “clone policy” bureaucracy adds bite). Tell me **A/B/C**, and one more preference so I can nail the cast and endings: - Should the **catastrophe timer** be **(1)** imminent disaster (reactor/collision), **(2)** a planned arrival/milestone (docking/inspection), or **(3)** a social tipping point (mutiny vote / martial law trigger)?

Confirmed: **Paranoid thriller** tone, and the run timer is a **looming Emergency Continuity Vote** that can either hand the ship to Security under **Continuity Protocol** (choking off your investigative freedom) or fracture the crew into **mutiny/martial law**. Your runs manipulate **who votes, how safely they can vote, what evidence is admissible, and whether key witnesses even dare show up**—and NPCs *remember* exactly how you pressured them. Go ahead and write your ship + cast + endings. When you’re done, I’ll help tighten it into: - a clear **relationship web** (who influences whom, who blocks whom), - the **vote mechanics** (quorum, intimidation, procedural hacks, admissibility rules), - and a set of **run-to-run “state shifts”** (complacent → paranoid → desperate) that reliably create new scenes without bloating content. If you want one extra constraint before you draft: do you want the vote to happen on a fixed **in-world clock** (e.g., “in 18 hours”) with each run representing the same window, or to advance only when you complete shifts (so runs are “attempts” at the same pre-vote day)?

Central crime: **(ii) sabotage to force Continuity as a power grab**, with **(iii) clone-program illegality as the enabling mechanism/cover-up**. That pairing dovetails with your timer (the ECV) and makes the “NPCs remember” constraint matter: the conspirators aren’t just hiding *what happened*—they’re actively shaping *governance outcomes*, and social memory is a battlefield. ### What the underlying conspiracy is - **Primary crime:** A controlled sabotage campaign (signal spoofing + staged “near-misses”) designed to create a credible emergency narrative so the ECV ratifies **Continuity Protocol**. - **Secondary crime (enabler):** The clone program is being used to: - **erase/soften witnesses** (compliance edits; memory trimming), - **invalidate testimony** via **identity standing** (“not the same legal person”), - and occasionally run **off-record “reprints”** (Paolo Ren) to keep a useful pawn alive while making their story inconsistent. ### “How was it done?” in gameable modules (midgame reveals) 1) **Reactor monitor tap** (Rigg’s find): lets someone inject bogus telemetry that “proves” emergency conditions. 2) **Archive custody forgery** (Pell): makes planted logs admissible and real logs “improperly handled.” 3) **Medical smoothing** (Oram under pressure): witnesses become unreliable without knowing why; your own resets can acquire subtle bias. 4) **Continuity Office doctrine exploit** (Sato’s flaw): the admissibility rules can be weaponized to exclude the one person who saw the real sabotage. ### Who did it (clean culprit structure) - **Architect:** **Rowan Kade** (needs Continuity to legalize suppression + cement authority). - **Institutional shield:** **Mira Sato** (not “evil,” but her need for procedural integrity makes her suppress the identity flaw; she becomes complicit). - **Operational grease:** **Jonas Pell** falsifies custody; a small Security cell does witness “protective custody.” - **Wild card:** **Commander Vale** signed a conditional pre-order—she’s not the saboteur, but she’s motive-aligned with “order at any cost,” and can become your final hurdle. ### The “one dead body” (optional but strong for noir clarity) Even if the ship is avoiding overt murder, give the mystery a focal victim: - **Previous Continuity Officer** (or ethics auditor) died in a “maintenance accident” *before* the playable window. - Their death is what kicked off Ren’s incident report—and what Kade is retroactively trying to launder through Continuity. ### What this choice buys you mechanically - The player’s job isn’t only to find facts; it’s to **prevent the conspirators from successfully laundering facts into admissible evidence**. - Your runs naturally oscillate between: - **protect witnesses** (Ren/Ward), - **secure provenance** (logs, taps, biometric proofs), - **shape the ECV narrative** (what the crew thinks is “true enough” to vote on). If you approve this core crime, the next concrete step is to outline: 1) **3–4 sabotage “incidents”** that repeat each attempt (same day) but can be altered by your interventions, and 2) the **Truth Threshold checklist** for Ending 3 (exact evidence types needed to force the Third Motion). Want the sabotage to be **non-lethal near-misses** (keeps the crew divided) or a **single catastrophic death** waiting to happen (higher urgency, darker)?

Let **Ending 3 be winnable with Kade surviving** (political defeat only), with an optional “hard version” where you also secure arrest/removal. Reason: it preserves the paranoid-thriller tone and makes your core theme land—**in a persistent social world, you can’t always delete the antagonist, you have to out-procedure and out-coalition them**. It also keeps replayability strong: if Kade can remain on-board, he becomes a post-ending consequence or sequel hook, and you can scale difficulty (“Third Verdict: Paper Win” vs “Third Verdict: Clean Win”). Below is a concrete **ECV vote mechanics** draft that plugs into your incidents and Truth Threshold. --- ## ECV Vote Mechanics (system spec) ### 0) What the player is actually trying to control Each attempt, you’re managing four interacting state machines: 1) **Votes** (numbers) 2) **Eligibility** (who can vote / who can testify) 3) **Admissibility** (what evidence counts) 4) **Safety/Access** (who can physically reach the Forum Chamber) Winning Ending 3 requires you to win **eligibility + admissibility + safety** long enough that the Forum can pass the Third Motion. You don’t necessarily need a “popular majority,” you need a **procedurally valid window of truth**. --- ## 1) The electorate (quorum + blocs) **Total voting members:** 11 (tunable). **Quorum:** 8 present in the Forum Chamber (physical presence matters; absence is a weapon). **Blocs:** - **Command bloc (2):** Vale + a rotating “Duty Chair” seat (can be influenced via schedule/pressure). - **Security bloc (3):** Kade + 2 Security reps (one can be Ward depending on path). - **Labor bloc (3):** Kwon + 2 deck reps. - **Technical bloc (2):** Rigg + Oram (treated as “critical services” reps). - **Treaty observer bloc (1):** Venn (special privileges: can certify process integrity, not just vote). This structure gives you a lot of levers without needing 30 NPC voters. --- ## 2) Motions and the win conditions The ECV is a sequence, not one roll. ### Motion A — **Adopt Continuity Protocol** (Kade’s goal) - If it passes, Security gains: - broad search powers, - witness detention authority, - forum censorship (“classified emergency”), - and **Medical oversight hooks**. - Mechanically: your future runs lose decks/routes and many social approaches become impossible. ### Motion B — **Deny Continuity** (Kwon’s default goal) - If it passes cleanly with legitimacy intact, you get breathing room; if it passes amid chaos, you slide toward mutiny. ### Motion C — **Third Motion (your win)** A legally framed “suspension and inquiry” package: 1) Suspend Continuity vote pending inquiry (halts Motion A/B finalization). 2) Remove Kade from operational control (temporary) **or** bind his authority to a council. 3) Mandate independent audit: Engineering telemetry, Archive custody, Medical clone integrity. 4) Require Venn’s treaty certification + broadcast minutes to prevent later revision. **Ending 3 (Paper Win):** Motion C passes; Kade remains alive/on-ship but constrained/politically defeated. **Ending 3 (Clean Win, optional):** add an extra clause with sufficient proof to trigger arrest/relief under Charter—harder, more lethal endgame. --- ## 3) Intimidation & attendance: “Presence is gameplay” Each key NPC has a **Courage** meter and a **Risk** meter: - **Risk** increases when Kade has Heat advantage, patrol density is high, or they’ve been publicly associated with you. - **Courage** increases with protection, alliances, and you demonstrating competence (e.g., saving people in Incident B). At the end of each shift, check: *Will they attend Forum? Will they testify?* You can directly affect this by: - providing escort routes (unlock shortcuts), - reducing chokepoints (Engineering), - granting safe harbor status (Medical), - or gaining formal **Forum Safe Conduct** writs via Vale/Sato. **Key rule:** An NPC can “vote by proxy” only if Sato allows it—and that itself is a procedural lever you can unlock or lose. --- ## 4) Admissibility: evidence tags + Sato’s doctrine meters Every piece of evidence you collect has tags: - **Type:** Physical / Systems / Testimonial - **Custody:** Clean / Questioned / Tainted - **Origin:** Archive / Engineering / Medical / Security / External - **Standing:** Person-valid / Person-contested (if tied to Ren or clones) Sato has three doctrine sliders that shift based on your actions and prior embarrassments (persistent): 1) **Strict Custody** (high = most things inadmissible, but “clean” items are devastating) 2) **Identity Formalism** (high = clone standing challenges succeed; low = presumption of continuity) 3) **Emergency Deference** (high = Security claims override process) Your goal for Ending 3 is to push Sato into a corner where her own precedent forces: - low enough **Identity Formalism** (or an exception rule), and - low enough **Emergency Deference** that your mechanism proof can be heard. This is where your “box her under her own memos” play shines. --- ## 5) Procedural hacks (your Caseboard “Moves” that touch the vote) Unlocked by linking nodes on the caseboard (as you described). Concrete examples: - **Motion to Compel Attendance:** requires Vale + evidence of witness intimidation. Gives a one-run “Safe Conduct” pass (if you can serve it physically). - **Split Alibi:** forces two NPCs to answer timeline questions in sequence; creates contradictions that generate a *Forum Shock* effect (reduces Emergency Deference). - **Challenge Custody:** lets you attack Pell’s stamps; if you win, planted logs flip from Clean → Tainted and can’t be used to justify Continuity. - **Standing Presumption Petition:** a legal move that, if filed before Incident D, prevents Ren being ruled “non-person” without a live hearing. - **Emergency Narrative Injunction:** requires Venn leverage; blocks Kade from circulating pre-written summaries as “official minutes.” All moves have costs: time, favors, and retaliation risk (persistent). --- ## 6) How the incidents feed the ECV system (tight loop) Each repeatable incident generates both **fear** and **proof** tokens. - **Fear tokens** automatically apply pressure to: - raise Emergency Deference, - shift undecided votes toward Continuity, - increase Risk for witnesses. - **Proof tokens** are only useful if you also secure: - custody (Pell), - standing (Ren), - admissibility (Sato). This ensures “solving” isn’t just finding the tap—you must also **make it count** inside the governance machine. --- ## 7) Failure states that still feel like progress Even when you “lose” a run: - You may permanently shift Sato’s doctrine (e.g., exposing a fake log reduces her trust in Security). - You may gain lasting leverage with Venn (treaty certification). - You may harden Kwon’s coalition (more votes) but at the cost of escalating toward mutiny. - Or you may sour relationships and make the next attempt materially harder—honoring the social memory premise. --- If you’re aligned with “Kade can survive Ending 3,” next choice that affects the whole endgame texture: **Should Kade be able to legally retaliate against your iteration by revoking your cloning privileges (making death ‘final’ until restored), or is your cloning right protected and he can only constrain you socially/physically?**

This RA design fits perfectly: it turns “death as iteration” into a **governable privilege**—and therefore a core battleground. Here’s a concrete **run-to-run state shift** framework that uses only a handful of global variables to reliably spawn new scenes and routes, without needing bespoke content for every permutation. --- ## Global State Model (persist across attempts of the “same day”) Track these 6 globals; everything else can derive from them: 1) **Emergency Deference (ED)**: 0–100 How willing the ship is to accept “security necessity overrides process.” 2) **Sato Doctrine Sliders** (each 0–100) - **Custody Strictness (CS)** - **Identity Formalism (IF)** - **Emergency Deference Bias (SB)** (Sato’s personal tilt, separate from ship ED) 3) **Reinstantiation Authorization (RA)**: 2 / 1 / 0 Your legal reset license tier. 4) **Witness Climate (WC)**: -3 to +3 A compact proxy for *Ren/Ward/Pell* showing up: negative = silence/vanish; positive = people dare to speak. 5) **Faction Posture** (two simple meters) - **Security Posture (SP)**: 0–3 (patrols, checkpoints, detentions) - **Labor Mobilization (LM)**: 0–3 (work stoppages, crowds, sabotage counter-pressure) That’s it. These naturally yield “complacent → paranoid → desperate.” --- ## State Bands (the 3-act escalation you asked for) ### Act 1: **Complacent** (default baseline) **Trigger:** ED < 35, SP ≤ 1, LM ≤ 1, WC ≥ 0, RA = 2 **Ship feel:** People think this is containable. Politics is sharp but not yet violent. **Systemic changes:** - Light patrols, broad access to common decks. - Sato accepts more informal evidence (lower effective CS). - Witnesses will meet you in semi-public areas. **Scene palette (reusable):** - “Quiet corridor” tails, cafeteria interrogations, archive after-hours. - Vale is reachable; Ward is willing to talk off-record. - Incident A/B produce fear, but it dissipates if you respond competently. --- ### Act 2: **Paranoid** (the loop starts to bite) **Trigger:** Any two of: - ED ≥ 35 - SP = 2 - WC ≤ -1 - RA drops to 1 - SB (Sato bias) ≥ 60 (she starts deferring to “necessity”) **Ship feel:** People remember you as disruptive/unstable *or* as a threat. Doors close socially before they close physically. **Systemic changes:** - Checkpoints appear (SP2). Some decks require “purpose logging” (creates evidence trails about you). - Sato issues “interim guidance memos”: - higher CS (custody demands), - higher IF (standing challenges become common), - evidence gets delayed “pending review” (time pressure). - Kade’s team starts “protective custody” moves (pre-emptive witness removal). **Scene palette:** - Witness meets must be arranged through intermediaries (Kwon/Oram), or in motion (walking interviews). - Pell becomes harder to reach; archive “maintenance” blocks narrow time windows. - Ward starts leaving dead-drops instead of meeting. - Incident C (Archive Reality Split) becomes the headline event: people argue about “what’s even real.” --- ### Act 3: **Desperate** (governance as open combat) **Trigger:** Any two of: - ED ≥ 70 - SP = 3 - LM = 3 - WC ≤ -2 - RA = 0 (or an active petition to suspend RA is filed) **Ship feel:** Everyone is choosing a side. Process is either weaponized or collapsing. A new death is plausible. **Systemic changes:** - Hard lockdown lanes; escorts needed; “no unscheduled movement.” - Sato adopts emergency court posture: hearings become quick, formal, and often ex parte unless you’ve secured process protections. - Crew begins moving in packs; union crowds can block doors (LM3), while Security can declare dispersal orders (SP3). - Evidence “expires” quickly: logs get sealed/classified, terminals wiped, medical records restricted. **Scene palette:** - Forum Chamber becomes a contested space *before the vote*: who controls the room controls legitimacy. - Ren/Ward may only appear if physically escorted under safe conduct. - Incident D (Witness Softening) shifts from covert smoothing to overt “fitness” proceedings and standing attacks. --- ## How the RA Tier plugs into the escalation (and stays fun) ### RA-2 (Full) - Death is a tactical reset. - NPCs still judge you for “recklessness” if it’s public (reputation hit), but you can recover. ### RA-1 (Conditional) - **Mechanical bite:** on reset you lose one of: - **1 shift** (start at Shift 2), *or* - **1 Caseboard Move slot** for that run, *or* - arrive with a **Clone Quirk** you didn’t choose. - **Narrative bite:** people start saying “they’re restricting your license” (WC trends downward unless you counter-message). ### RA-0 (Suspended) - **Not game over:** death ends the attempt immediately + applies a persistent “Evasion Stigma” tag: - raises ED slightly (“they’re gaming the system”), - increases SB (Sato bias) unless countered, - decreases WC (“don’t get near them, you’ll be next”). - **But:** RA-0 opens new “desperation routes”: - black-market cradle path, - treaty shield path, - emergency hearing path. ### Guardrail implementation (your requirement) Kade can only plausibly push RA→0 if: - ED is already high **and** - there’s a credible pretext event on record: public death, caught fabrication, caught tampering, or “in custody incident.” This keeps RA as a climax pressure, not an early tax. --- ## Reliable “New Scene” Generator (no bloat) At the start of every attempt, roll/choose one **Pressure Card** based on the globals. Each card swaps just a few NPC locations + one rule tweak. Examples (3 per act, reusable): **Complacent cards** - *Routine Audit*: Sato requests voluntary submissions; archive access is easier but time-limited. - *Union Listening Session*: Kwon convenes; you can sway votes but risk being seen as an agitator. - *Medical Open Clinic*: Oram is accessible; you can secure baseline depositions. **Paranoid cards** - *Protective Custody Sweep*: one witness is missing; their last known route becomes a stealth objective. - *Custody Crackdown*: CS spikes; any evidence without chain-of-custody is auto-tainted. - *Fitness Rumor*: RA targeted (petition telegraphed); you can preempt with your own Standing Petition. **Desperate cards** - *Forum Lock*: Security controls chamber access; you must get safe-conduct or stage a procedural breach. - *Work Stoppage Barricade*: LM spikes; engineering routes change; security must negotiate or force entry. - *Emergency Hearing*: Sato schedules an RA hearing mid-run; you can attend (cost actions) or skip (default loss). This gives you “different day” vibes while staying literally the same day. --- ## Minimal equations (so it’s implementable) You can drive global shifts with simple deltas: - Each incident you **solve publicly**: ED -5, WC +1 (but SP +1 if you embarrassed Security). - Each incident you **solve covertly**: ED 0, WC +0, Proof +1 (good for Ending 3). - Each time you’re **caught**: ED +7, SP +1, WC -1, SB +5. - Each time a witness is **smoothed/vanishes**: WC -2, ED +3. - Each time you win a **procedural motion** in Forum prep: SB -10, CS/IF adjust based on motion type. Tune numbers later; the key is consistent directionality. --- ## One design fork to choose next (it matters a lot) When RA is threatened, should there be a **mandatory mid-run hearing scene** (high drama, procedural duel with Sato), or should RA changes happen **as background memos** that you only discover via terminals/NPCs? Pick one: - **Hearing scene** = cinematic, clear cause/effect, costs time/actions. - **Background memos** = more sim-like, sneakier, easier to miss, more paranoia. If you pick “hearing scene,” I’ll draft the hearing as a repeatable setpiece with 3–4 argument “minigames” tied to your evidence tags and doctrine sliders.

### 3 Example RAH Scripts (one per act) These are written as **drop-in narrative design doc setpieces**: who triggers it, what Kade submits, what the player can counter with, and what the ruling options look like. I’m using your tag vocabulary (Custody/Origin/Standing) and the doctrine/globals (ED/SB/CS/IF). --- ## Script 1 (Act 1 / Complacent): **“Clarification, Not Punishment”** **Trigger context:** You prevented Incident B’s corridor crush with a visible rescue, but later got seen near an admin console. Kade tries a light touch: constrain you early. **Globals (typical):** ED 20–30, SB 40–50, CS 35, IF 45, SP1, LM0–1, WC +1, RA2 **Location dressing:** Annex corridor mostly empty; one clerk and one off-duty engineer watching through the glass. ### Phase 1 — Standing & Jurisdiction - **Sato (opening):** “This is an administrative fitness review, not a criminal proceeding. We are clarifying conditions of reinstantiation authority.” - **Kade:** “Iterator privileges aren’t a right. They are a safety instrument.” **Player choices (examples):** 1) **Demand Live Hearing** (if you have *Charter precedent: “Adverse Status Requires Notice”* OR Vale present) - **Sato reaction (if CS low):** mild irritation, but grants it: “Noted. Today is advisory only.” - **Effect:** bars RA-0 for this session. 2) **Medical Necessity Claim** (Oram neutral) - **Oram:** “Summary suspension raises severe dissociation risk. I advise conditional use, not revocation.” **Kade counter:** “Emergency necessity” is weak here (ED low); he pivots to “pattern prevention.” ### Phase 2 — Fitness Kade leans on *prudence*. - **Kade:** “They insert themselves into restricted systems. Next time the system reacts, we won’t be so lucky.” **Strong player move:** **Demonstrate Competence** - Present: *“Rescue report + door script anomaly noted”* (Proof token, even if not fully admissible) - **Sato:** “I will not punish competence.” **Alternative:** **Accept Constraints** - Choose RA-1 conditional to gain a short-term sponsor clause (low stigma in Act 1). ### Phase 3 — Evidence drill (lightweight) **Kade exhibits (2):** - **Exhibit K1:** *Terminal Access Log* - Tags: Systems / **Origin: Security** / Custody: **Clean** (Pell stamp) - Claim: you accessed “Admin Routing Console” outside duty. - **Exhibit K2:** *Security Incident Note* (guard statement) - Tags: Testimonial / Origin: Security / Custody: Questioned **Player counters:** - **Challenge Origin:** “Security-only logs aren’t impartial” (needs Engineering corroborator OR simple shadow telemetry you got from Rigg) - **Force Disclosure:** request raw log header. If granted, it reveals a missing checksum segment (downgrades Clean → Questioned). ### Phase 4 — Remedy **Likely rulings:** - **RA stays at 2**, plus a soft warning, if you presented competence + poked holes in K1. - **RA-1 (conditional) sponsor clause** if you were sloppy but not publicly reckless. **Payoff:** Early tutorialization: the player learns the hearing is *winnable*, and custody/origin tags matter, without the full cruelty. --- ## Script 2 (Act 2 / Paranoid): **“Iterator Evasion Pattern”** **Trigger context:** Prior attempt ended with you dying in public custody (or being shot while fleeing). Crew remembers. WC dipped. Kade moves to tighten the leash. **Globals (typical):** ED 45–60, SB 60–70, CS 60, IF 65, SP2, LM1–2, WC -1, RA1–2 **Location dressing:** corridor has two Security officers “for safety.” A small knot of crew members watches; whispers carry. ### Phase 1 — Standing & Jurisdiction - **Kade:** “We have demonstrated evasion. Their death is not incidental—it is used as a procedural dodge.” - **Sato:** “Emergency Fitness Petition is accepted. Summary measures are available under interim guidance.” **Player win lines:** 1) **Demand Live Hearing** (requires you pre-filed Standing Presumption Petition for yourself *or* Vale present) - If successful: emergency summary authority narrows; RA-0 becomes harder to justify. 2) **Treaty Objection** (Venn present) - Venn doesn’t “side with you,” she side-eyes process: “Observer notes will reflect whether due process was meaningfully offered.” - Effect: SB drops slightly for this session; Sato becomes less willing to rubber stamp. **Kade counter:** introduces “iterator hazard memo” (ties to ED and SB). ### Phase 2 — Fitness (the propaganda fight) - **Kade (to the room):** “How many times do we let one person reset out of accountability?” **Player options:** - **Expose Motive:** present Ward-linked memo or “protective custody sweep order.” - Even if Custody is Questioned, it forces **cross-exam** tone. - Risk: if it’s forged or tainted, you get hammered and ED rises. - **Demonstrate Competence:** spend an incident mitigation token from *Telemetry Panic* (“shadow readout shows no real instability”). - **Accept Constraints:** strategically lock in RA-1 to avoid RA-0, but gain “Restricted Iterator” tag (Security shadow follows you: stealth harder, social intimidation easier because everyone sees the leash). ### Phase 3 — Evidence Admissibility Drill (real duel) **Kade exhibits (3):** - **Exhibit K1:** *Emergency Necessity Summary* (CO memo drafted by Sato’s office, requested by Security) - Tags: Systems / Origin: Continuity Office / Custody: Clean - Claim: emergency conditions justify summary suspension. - **Exhibit K2:** *Clone Bay “Noncompliance” Record* (Oram pressured entry) - Tags: Medical / Origin: Medical / Custody: Clean / Standing: Person-valid (about you) - Claim: you refused observation / displayed dissociation. - **Exhibit K3:** *Chain-of-custody affidavit* (Pell stamp) attaching a tampering allegation - Tags: Archive / Origin: Security / Custody: Clean (but vulnerable) **Player counters (limited challenges, time-costed):** 1) **Challenge Custody** (best if CS high): use any stamp anomaly lead or external checksum to downgrade K3. 2) **Challenge Origin**: attack K2 by forcing Oram live clarification (only if Oram present and not hostile). If Oram is hostile, this is a trap. 3) **Force Disclosure**: demand the request trail for K1. If you have evidence the memo was solicited pre-incident, it reads like premeditation (SB takes a hit; ED stops climbing). **Key twist option:** If you previously linked **Pell ↔ Kade** on the caseboard, you unlock a special move here: - **“Impeach Custody Officer”**: forces Pell to appear or be named. If he refuses, Kade’s “Clean” claims start shedding weight. ### Phase 4 — Remedy (and the sponsor trap) **Common ruling in Paranoid:** - **RA-1 Conditional with Sponsor Clause** - “Valid sponsor required per shift.” Named sponsor chosen in ruling: Vale or Oram (Sato avoids naming Venn unless pressured). **How it becomes gameplay immediately:** You must secure the sponsor signature before the end of the current shift window, otherwise RA drops at next attempt. **Win feel:** You didn’t “defeat” Kade—you stabilized. The leash is real, but now the player has a **clear mission**: lock in protections or flip a sponsor. --- ## Script 3 (Act 3 / Desperate): **“Ex Parte Suspension”** **Trigger context:** ED high, SP3. One witness vanished. You’re close to Pillar completion, so Kade tries to end iteration before you can present. **Globals (typical):** ED 75–90, SB 80–90, CS 75, IF 85, SP3, LM2–3, WC -2 to -3, RA1 **Location dressing:** Annex is ringed. Sato arrives flanked by Security “for her safety.” Crowd outside is either union-packed (LM3) or cleared (SP3). ### Phase 1 — Standing & Jurisdiction (compressed) - **Sato:** “Emergency procedures are active. The petitioner has submitted exhibits under seal.” - **Kade:** “Iterator activity is a continuity hazard.” **Hard rule:** If you did **not** secure “Live Hearing protection” earlier in the campaign, Phase 1 becomes a brutal timer: - You get **one** move only. **Player lifesavers:** 1) **Treaty Objection** (Venn present) - Forces Sato to unseal *some* portion: “Observer requires minimal transparency.” 2) **Demand Live Hearing** (only works if pre-filed; otherwise denied under emergency). 3) **Medical Necessity** (only works if Oram is allied and willing to risk retaliation). **Failure state:** Phase 1 fails ⇒ Sato allows ex parte weight; later phases become skewed. ### Phase 2 — Fitness (hostile room) Kade frames you as existential threat: - **Kade:** “They are iterating outcomes. They are not accountable to this crew.” **Player best play in Desperate:** - **Expose Motive** with the cleanest link you have: a suppression order, custody forgery link, or pre-written narrative summary (Venn cares about that). - If you have only tainted evidence, this can backfire catastrophically (ED +, WC -, RA likely 0). **High-drama option:** If LM3 and Kwon is allied, you can trigger a **public gallery statement** outside the glass (costs action, raises SP, but boosts WC and pressures Sato politically). It’s not comedic—more “crowd as weapon.” ### Phase 3 — Evidence Drill (sealed exhibits + fewer counters) **Kade exhibits (2), both heavy:** - **Exhibit K1:** *Continuity Hazard Classification* (CO memo citing identity instability + evasion stigma) - Tags: Continuity Office / Custody: Clean / Standing: contested framing - **Exhibit K2:** *Unauthorized Clone Activity Allegation* (black-market cradle hint) - Tags: Security + Medical / Custody: Clean (laundered) **Player counters (only two challenges allowed):** 1) **Challenge Standing**: flip the framing—argue RA suspension itself creates instability; require live medical testimony (needs Oram + baseline deposition). 2) **Force Disclosure**: demand request provenance; if you can show K1 drafted *before* the alleged triggering event, you expose premeditation. This is the single strongest “turn the room” play. ### Phase 4 — Remedy (the cliff edge) **Default if you lose:** **RA-0 Suspended** - Add “Evasion Stigma” persistent tag. - Immediate post-hearing risk: arrest attempt or forced “observation.” **If you partially win:** **RA-1 Sponsor Clause + hostile sponsor** - Sato names a sponsor you don’t have (e.g., Vale if she’s inaccessible), creating a scramble objective. - This is a great desperation generator without a hard fail. **If you fully win (rare):** - **Maintain RA-1 without sponsor**, plus an explicit note: “revocation requires Forum quorum.” This becomes your “I bought one more attempt” victory moment. **Victory-with-consequences kicker (as you suggested):** Even if you win, Sato issues a memo next attempt: - CS +10 (“evidence handling reforms”) or - IF +10 (“identity clarity initiative”) depending on which angle you used to beat her. --- ## Implementation note (to keep it replayable) To avoid writing infinite bespoke dialogue, keep 70% of lines **modular**: - Kade has 6–8 reusable claims keyed to your public flags (died publicly, caught tampering, protected witness, etc.). - Sato has 6–8 doctrine lines keyed to SB/CS/IF bands. - Oram/Vale/Venn each have 3 stance variants (hostile/neutral/allied) with 2–3 lines each. Everything else is evidence-card text + ruling output. --- If you want the next doc-ready piece, choose one: 1) **The “exhibits library”**: a list of ~20 exhibit cards (name, tags, how Kade gets them, how you counter them). 2) **Sponsor mini-quests**: 3 short objective chains (Vale/Oram/Venn) that secure RA-1 signatures under SP/LM pressure.

## Third Motion Package (doc-ready module) A single “package” the player can assemble and then try to pass in the Forum. Each clause is a **sub-win** with its own unlock condition, so you can tune difficulty and allow partial victories. ### Motion ID: **M-C. Third Motion: Interim Continuity Review & Safeguards** **Declared purpose (what it sounds like):** “To preserve ship function and legitimacy by suspending the Emergency Continuity Vote pending an independent inquiry into sabotage, evidence integrity, and medical/identity governance.” **Mechanical purpose:** Creates an Ending-3 path that’s neither “Continuity passes” nor “Forum collapses,” and it can be **paper-win** (Kade constrained) or **clean-win** (Kade removed/arrested). --- # Clause list (7 clauses + 2 optional add-ons) Each clause lists: - **Effect** (what it changes in systems/world) - **Unlock** (what evidence threshold enables it) - **Opposition** (who resists, and how they try to amend it) --- ## C1) **Suspend the ECV Final Vote** **Effect:** Halts Motion A/B from resolving; freezes certain emergency powers from auto-triggering next attempt. Drops global ED drift by a fixed amount (e.g., ED -10) because “process restored.” **Unlock:** Any **2 of 3** sabotage-mechanism proofs (your Pillar I). - Physical tap/trace (E19 helps) - Systems mismatch (E19) - Credible testimonial (Rigg or Ward, Person-valid) **Opposition:** - **Kade** argues “suspension = paralysis.” Proposes amendment: “brief suspension only (one shift).” - **Vale** worries about command vacuum; may support if C2/C4 also pass. --- ## C2) **Immediate Restriction on Security Emergency Directives** **Effect:** SP cannot exceed 2 without commander + CO co-sign; reduces witness vanish probability; blocks “protective custody” without Safe Conduct exceptions. **Unlock:** Any proof of **witness suppression** or misuse of custody: - E13 (Protective Custody Transfer Order) + counter showing pretext, OR - Ward memo / testimony, OR - Obstruction proof tied to Safe Conduct. **Opposition:** - **Kade** pushes carve-out: “Security retains detention authority for continuity hazards.” - If you let that carve-out through, it becomes the seed of a “Paper Win with teeth” (Kade still dangerous). --- ## C3) **Evidence Chain-of-Custody Audit (Archive)** **Effect:** Freezes Pell’s stamp authority; forces dual-control custody; flips many of Kade’s future “Clean” exhibits to Questioned by default. **Unlock:** Pillar II custody proof: - External checksum (E20) **or** caught-in-act stamp forgery **or** Pell confession. **Opposition:** - **Sato** supports (it protects her legitimacy), but tries to narrow scope to “post-incident records only” (which conveniently excludes the prior death’s files). --- ## C4) **Telemetry & Systems Integrity Audit (Engineering)** **Effect:** Establishes dual-source telemetry rule; future Incident A “fear output” is reduced; prevents auto-generated Necessity Summaries from being treated as dispositive. **Unlock:** E19 Shadow Telemetry Ledger **or** Rigg sworn statement + physical trace capture. **Opposition:** - **Kade** tries to reframe as “Engineering oversight under Security” (a poison-pill amendment). - **Rigg** only backs publicly if protected from scapegoating (tie-in to your leverage design). --- ## C5) **Medical Autonomy & Clone Integrity Safeguards** **Effect:** Blocks “smoothing under pressure” and records tampering; enables “no-suspend clinical covenant” to protect RA from summary revocation. **Unlock:** Any substantiated coercion link: - Oram testimony + access log, OR - unauthorized reprint request evidence, OR - staff deposition. **Opposition:** - **Kade** claims Medical is a security vector; proposes access oversight. - If Kade’s amendment passes, Oram becomes a hostage and RA remains vulnerable (great for bittersweet paper win). --- ## C6) **Identity Standing Presumption (Forum Rule)** **Effect:** For purposes of testimony and RA, **continuity of personhood is presumed** unless disproven at a live hearing with quorum. This directly nerfs “non-person” attacks on Ren and on you. **Unlock:** Pillar III standing route: - Charter precedent + Sato memo trap, **or** - Oram baseline deposition + coercion proof, **or** - Venn treaty certification. **Opposition:** - **Sato** resists if IF is high (this clause threatens her doctrine). She will try to amend: “presumption applies to crew only, not off-record reprints” (targets Ren). --- ## C7) **External Certification & Broadcast Minutes** **Effect:** Forces Venn certification and/or automatic broadcast of the motion minutes to prevent later narrative laundering. Reduces SB (Sato bias) over time because transparency limits her maneuvering. **Unlock:** Venn leverage (E20, pre-written narrative drafts, or custody forgery proof). **Opposition:** - **Kade** frames as foreign interference; tries to strip Venn’s involvement. - If ED is very high, this clause becomes *the* swing point: pass it and reality stabilizes; fail it and “truth” becomes whatever Security says. --- ## Optional Add-on A (Paper Win enhancer): **Interim Security Council** **Effect:** Kade remains alive and on-board but loses unilateral command; Ward or another rep joins a council with Vale oversight. **Unlock:** Any credible internal Security split proof: - Ward testimony / memo OR demonstrable misconduct in suppression unit. **Opposition:** - **Kade** tries to stack the council with his loyalists; amendment battle can decide whether Kade is functionally neutered or merely rebranded. --- ## Optional Add-on B (Clean Win enabler): **Immediate Relief/Detention Pending Inquiry** **Effect:** Kade is physically removed/arrested (or confined), ending the “Kade survives” ambiguity. **Unlock:** High bar: full Pillar II + a direct command link (“signed order” level), plus at least one live witness (Ward or Pell or Ren as Person-valid). **Opposition:** - **Vale** may resist unless the case is airtight (she fears mutiny optics). - **Sato** fears precedent; may demand sealed handling (dangerous). --- # Assembly rules (to make it gameable) The Third Motion isn’t all-or-nothing: it’s a **bundle** you can arrive at with different strength. ### Minimum viable Third Motion (to count as Ending 3: Paper Win) Must pass: **C1 + C2 + (C3 or C4) + C6 + C7** This ensures: vote suspended, Security constrained, audits begin, standing protected, transparency enforced. ### Clean Win path Pass minimum bundle **+ Add-on B** (or Add-on A + later arrest epilogue). --- # Amendment battle (quick mechanic sketch) During the Forum climax, each clause can be: - **Passed cleanly** - **Passed with carve-out** (weaker, creates future problems) - **Struck** Mechanically: - Each ally present (Vale/Oram/Venn/Kwon/Ward/Rigg/Pell/Ren) grants one **“Support Token”** usable to: - block a hostile amendment, - force a vote on a clause, - or call a brief recess (escort witness, fetch exhibit). Kade gets **“Fear Tokens”** equal to ED band and unresolved incidents; he spends them to: - attach carve-outs, - strike transparency (C7), - or keep detention authority. This turns your whole campaign into intentional prep: witness protection and admissibility aren’t flavor—they are literal tokens in the climax. --- # How this ties into your RA hearing If you pass **C6 + C5**, you effectively “future-proof” RA: - RA-0 becomes very hard without quorum and live medical testimony. - The RAH setpiece remains, but it becomes a winnable debate rather than a foregone conclusion—nice pacing after the climax. --- If you want, next I can produce either: - **A sample Forum finale sequence** (beats, when each NPC speaks, where the escort/stealth segment fits), or - **A tuning table** that maps evidence pillars → which clauses unlock, so you can balance playtime and ensure multiple routes to the minimum bundle.

Use **two major routes** to the minimum bundle (keeps the mystery legible, reduces combinatorial balancing), with the **Treaty/External (Venn)** as a **swing modifier** that makes both routes easier/cleaner rather than a full third trunk. Target campaign length: **12–18 runs** for a first complete playthrough, with skilled players able to hit a Paper Win in ~8–10 once they know the map and hearing cadence. Below is the **tuning table** you asked for: what unlocks what, how many “hard gates” exist, and how to pace unlocks across runs without bloat. --- ## A) Two-route structure (to Minimum Bundle) ### Minimum bundle required for Ending 3 (Paper Win) **C1 + C2 + (C3 or C4) + C6 + C7** You want two viable trunks: 1) **Engineering/Mechanism Trunk (“Prove the emergency is staged”)** - Backbone clauses: **C1, C4, C2** - Typical allies: **Rigg, Ward, Vale** - Typical evidence: **E19 + tap/trace proof + suppression link** - Style: stealth/hacking + technical corroboration + procedural pivots 2) **Legal/Medical Integrity Trunk (“Prove the process is corrupted + standing must be presumed”)** - Backbone clauses: **C6, C5, C3 + C1** - Typical allies: **Oram, Pell (flip), Kwon (protection), Vale** - Typical evidence: **baseline depositions + custody forgery proof + coercion link** - Style: social protection + custody games + hearings + sanctuary gameplay **Treaty swing (Venn):** makes C7 easier and reduces SB/ED in key moments; can substitute for missing polish but shouldn’t replace core pillars. --- ## B) Clause unlock table (pacing + evidence requirements) Legend: - **M** = Mechanism proof (Pillar I) - **L** = Laundering proof (Pillar II) - **S** = Standing proof (Pillar III) - **W** = Live witness viability (escort/protection capability) | Clause | What it does | Unlock requirement (tuned) | Route weight | |---|---|---:|---| | **C1 Suspend ECV** | lets you steer | **M: 2-of-3** (physical/systems/testimonial) | Engineering-heavy | | **C2 Restrict Security** | stops witness vanishing | **W: 1** + any suppression indicator (E13 counter, Ward hint, obstruction) | Both | | **C3 Custody Audit** | flips “Clean” advantage | **L: custody proof** (E20 or caught forgery or Pell confession) | Legal-heavy | | **C4 Telemetry Audit** | nerfs “emergency” narrative | **M: systems mismatch (E19)** OR physical trace + Rigg | Engineering-heavy | | **C5 Medical Safeguards** | blocks smoothing/RA abuse | **S or coercion** (Oram link + baseline deposition) | Legal-heavy | | **C6 Standing Presumption** | keeps Ren/you admissible | **S: 1 route** (legal precedent OR Oram route OR Venn certification) | Legal-heavy | | **C7 Broadcast/Certification** | prevents narrative rewrite | **Venn leverage** OR “minutes laundering” proof | Swing modifier | **Design intent:** - Engineering route can hit **C1+C4** early; then needs **C6+C7** which you can reach via either a light legal precedent path or Venn swing help. - Legal route can hit **C6+C3+C5** early; then needs **C1** which forces at least some engagement with sabotage mechanism (prevents “pure court-room win”). --- ## C) Run pacing (12–18 runs) by “unlock tiers” Rather than raw runs, pace by **player milestones** that typically take 2–4 runs each on first playthrough. ### Tier 0 (Runs ~1–3): Orientation + first contradictions **Goals:** - Learn incidents A/B cadence - Meet Vale/Sato/Kade and feel “process as weapon” - Put **Rigg** and **Oram** on the board **Unlocks likely:** - First Caseboard Moves (Split Alibi, Purpose Logging) - Partial M (1-of-3): shadow hint or physical lead (not full E19 yet) ### Tier 1 (Runs ~4–7): First hard gate — custody or telemetry Player should secure **one cornerstone artifact**: - Engineering: **E19 Shadow Telemetry Ledger** (or physical tap signature) → enables C4, helps C1 - Legal: **E20 External checksum** *or* stamp-forgery proof → enables C3 **Expected friction:** - First serious SP2 escalation - First RAH (Paranoid) and RA drops to 1 for many players ### Tier 2 (Runs ~8–12): Standing war + witness protection **Goals:** - Make **Ren** and/or **Ward** viable as live witnesses (W) - Establish **C6 pathway** (legal precedent filed, or Oram sanctuary, or Venn certification) - Lock down C2 (reduce witness vanishing) **Expected friction:** - Pressure cards start forcing “Protective Custody Sweep” style runs - RA threat becomes a lived constraint; players learn sponsor quests ### Tier 3 (Runs ~13–18): Assemble minimum bundle + finale prep **Goals:** - Have C1 draftable (2-of-3 mechanism) - Have at least one of (C3 or C4) fully safe - Ensure C7 is passable (ideally with Venn swing) - Ensure quorum can be physically achieved **Result:** - Forum Night triggers as soon as minimum bundle is *possible*, not when it’s easy—so skilled players can “rush” the finale at higher risk. --- ## D) Difficulty knobs (to hit 8–10 run skilled, 12–18 first-time) 1) **Mechanism proof density** - Easy mode: E19 alone counts as 2-of-3 if Clean custody - Standard: E19 counts as 1-of-3; needs one more (tap signature or witness) 2) **Standing route generosity** - Standard: C6 needs 1 full route (legal precedent *or* Oram coercion package *or* Venn) - Hard: require C6 plus one supporting “baseline deposition” item 3) **Venn as swing** - Standard: Venn can unlock C7 with leverage and reduce SB in hearings - Hard: Venn demands clean tactics (no fabrication/black-market), raising planning cost 4) **Quorum fragility** - Standard: quorum is reachable with one escort objective - Hard: two key voters are “missing” by default in Desperate band, forcing multi-escort --- ## E) “No dead content” guarantee (how to avoid wasted branches) Make every trunk share at least 2 artifacts that are useful on *both* paths: - **E19 Shadow Telemetry** helps in hearings (E11 counter) even if you’re legal-heavy. - **E20 External checksum** helps custody fights and also undermines Kade exhibits in RAH even if you’re engineering-heavy. - **C2** is always relevant (keeps the rest playable). This prevents the classic immersive sim slog where half your discoveries are irrelevant to your chosen ending. --- If you want, next I can write **a run-by-run exemplar “golden path”** (8–10 runs) and a “messy first-time path” (14–16 runs), showing when RAH fires, when RA drops, and which pressure cards tend to appear—useful for validating pacing.

## Numeric tuning sheet (simulation-friendly defaults) This is a **starter spreadsheet spec** that lets you simulate: “How many runs until a typical player can draft/pass the minimum bundle?” and “How fast do things spiral into Desperate?” All values are intentionally small and linear. You can later add nonlinearity (e.g., ED drift accelerates above 70). --- # 0) Globals & default starting values **Start of new campaign (Attempt 1):** - **ED** = 20 - **SB** = 45 - **CS** = 40 - **IF** = 45 - **SP** = 1 - **LM** = 1 - **WC** = +1 - **RA** = 2 **Per-attempt baseline drift (applied once at start of each attempt, before Pressure Card):** - ED **+2** (fear accumulates as “same day” destabilizes) - WC **-0.25** (people tire / rumors spread) - If **SP=3**: ED +1 extra - If **LM=3**: ED +1 extra - Clamp: ED [0..100], SB/CS/IF [0..100], WC [-3..+3] --- # 1) Incident outcome deltas (A–D) For each incident in an attempt, pick the best matching outcome. ## Incident A: Telemetry Panic **A1 — Publicly stabilized (heroic, visible)** - ED -4 - WC +0.5 - SP +1 (Security “tightens” after embarrassment) with 50% chance if Kade is present **A2 — Covertly proven (shadow mismatch secured)** - ED 0 - WC 0 - Enables **E19** progress (track separately) - SB -2 (Sato distrusts “emergency summaries” a bit) **A3 — Unchecked / you fail** - ED +6 - WC -0.5 - SP +1 (auto if ED≥35 after this) ## Incident B: Autodoor Malfunction **B1 — Public rescue + blame defused** - ED -3 - WC +1 - LM -0.5 (crew feels protected without labor escalation) **B2 — Covert trace capture (command origin logged)** - ED 0 - WC 0 - SP +0.5 (someone notices tampering later; apply next attempt) **B3 — Injury/near-casualty rumor spreads** - ED +5 - WC -1 - LM +1 (crew anger) ## Incident C: Archive Reality Split **C1 — You secure checksum/timeline proof (anti-laundering win)** - SB -3 - CS +3 (Sato tightens process, but it now favors *real* custody) - WC +0.5 (people begin believing corruption is real) **C2 — You confront Pell but don’t flip him** - WC -0.5 (he’s scared; stops cooperating) - CS +2 (more bureaucracy) - SP +0.5 (Security adds “archive protection” next attempt) **C3 — Planted logs win the narrative** - ED +4 - SB +2 - WC -1 ## Incident D: Witness Softening / Standing attack **D1 — You protect witness (live, baseline deposition secured)** - WC +1 - IF -3 (standing presumption becomes socially credible) - ED -1 **D2 — Witness smoothed / becomes inconsistent** - WC -2 - IF +4 - ED +2 **D3 — Standing ruling against witness (declared “non-person” or unreliable)** - WC -1.5 - IF +6 - SB +2 --- # 2) “Caught / exposed” deltas (social memory penalties) Apply these immediately when they happen (once per attempt per category). **Caught trespassing / bodycam still (E18 type event)** - ED +2 - SP +1 (if SP<3) - WC -0.5 **Caught fabricating evidence (Fabrication Flag E16)** - ED +8 - SB +5 - WC -2 - Sets persistent tag: *Fabrication Known* (until Ending) **Public death (seen by crew or in custody)** - ED +5 - WC -1 - Triggers RAH eligibility next attempt (if ED≥35) - If RA=1: increases chance RA→0 petition succeeds (+20% “Kade weight” in hearing) **Quiet/reset death (unwitnessed)** - ED +0 - WC -0.25 (rumors) - No automatic RAH trigger --- # 3) Pressure Card effects (start-of-attempt modifiers) These are “scene shapers.” Apply once at attempt start. **Routine Audit** - CS +3, SB -1 **Protective Custody Sweep** - SP +1 - WC -1 (unless C2 already passed in prior attempt; then WC -0.25) **Custody Crackdown** - CS +8 - SB +2 - Your “Questioned” evidence counts as “Tainted” for hearings this attempt (mechanical flag) **Forum Lock** - SP +1 - ED +2 **Work Stoppage Barricade** - LM +1 - ED +1 - If you force through violently: ED +3 extra, WC -1 **Emergency Hearing** - RAH triggers this attempt (mandatory) - SB +2 (Sato in defensive posture) --- # 4) RAH outcome deltas (the setpiece pays/penalizes) Apply after the hearing. Also update RA. **H1 — You win clean (RA unchanged, or RA1→RA2 upgrade)** - SB -6 - ED -2 - CS +2 (Sato “tightens” to avoid being boxed again) - RA: stays at 2 or upgrades from 1→2 only if you had a sponsor + pristine record **H2 — Compromise (RA-1 conditional, sponsor clause or monitor)** - SB -2 - ED +0 - SP +0.5 - RA: set to 1 (if not already) - Add tag if monitored: *Restricted Iterator* (social: WC -0.25 next attempt; mechanical: patrol awareness +) **H3 — Loss (RA-0 suspended)** - SB +4 - ED +3 - WC -1 - RA: set to 0 - Add persistent tag: *Evasion Stigma* (until RA restored; makes future hearings harder) **H4 — You skip / don’t show** - Treat as H3-lite: - SB +2 - ED +2 - RA drops by one tier (2→1 or 1→0) --- # 5) RA restoration deltas (when you complete a sponsor mini-quest) Apply when you secure sponsorship/restoration. **Vale sponsorship signed (RA stabilization)** - RA: 0→1 or 1 stays 1 but removes “drift” - SB -3 - SP +1 next attempt (Security reaction) - WC +0.5 (legitimacy bump) **Oram clinical covenant** - RA: 0→1 or protects RA1 from dropping - IF -3 - SP +0.5 (Security pressure) - WC +0.5 **Venn treaty shield** - RA: 0→1 (only if she chooses to intervene), otherwise adds protection against RA0 - SB -6 (RA issues only; set a separate SB_RA modifier if you want) - ED -1 (optics) **Black-market cradle (dirty fallback)** - RA: treat as “functional RA1” (you can loop), but: - IF +5 (identity contamination) - WC -1 (if discovered; otherwise 0) - Enables Kade Exhibit E5 next hearing --- # 6) Forum clause pass deltas (finale-only + “future-proofing”) Even though the finale ends the campaign, deltas are useful for “epilogue state” and for any postgame/sequel mode. For each clause, record outcome as **Clean / Carve-out / Struck**: ## C1 Suspend ECV - Clean: ED -10, SB -4 - Carve-out (temporary suspension): ED -5, SB -2 - Struck: ED +6 ## C2 Restrict Security - Clean: SP set to min(current,2) and “protective custody” disabled; WC +1 - Carve-out (“continuity hazards” exception): WC +0.25; Kade retains detention lever - Struck: SP +1, WC -1 ## C4 Telemetry Audit - Clean: ED -5 (publicly), SB -2 - Carve-out (“Security oversight”): ED -2 but SP +1 (poison) - Struck: ED +3 ## C6 Standing Presumption - Clean: IF -10 (doctrine shift), WC +1 - Carve-out (crew-only, excludes off-record reprints): IF -4, WC +0.25 - Struck: IF +6, WC -1 ## C7 Broadcast/Certification - Clean: SB -6, ED -3 - Carve-out (delayed broadcast): SB -3, ED -1 - Struck: ED +4, SB +2 (Include C3/C5 similarly if you want; I can add them, but you targeted the C1+C2+C4+C6+C7 bundle.) --- # 7) Suggested thresholds (when the game “feels” like each act) These are the gates your content system can use. **Complacent band** - ED < 35 and SP ≤ 1 and WC ≥ 0 and RA=2 **Paranoid band** - ED 35–69 OR SP=2 OR WC ≤ -1 OR RA=1 **Desperate band** - ED ≥ 70 OR SP=3 OR WC ≤ -2 OR RA=0 OR LM=3 --- # 8) Sanity-check: expected run counts with these numbers - A competent player who repeatedly gets A2/B2/C1/D1 style results will keep ED from spiking, keep WC afloat, and avoid SP3—hitting **8–10 runs** to finale. - A typical first-time player will eat at least one A3 or D2, plus one “Caught” event, likely triggering RAH compromise and SP2 escalation—landing **14–16**. --- If you want the sheet fully complete, I can add the missing clause deltas for **C3 (custody audit)** and **C5 (medical safeguards)**, plus a small “Kade Fear Token” calculation that derives from ED/SP and unresolved incidents for the Forum Night amendment battle.

### Added clause deltas (C3, C5) + Fear Token calc — confirmed & integrated Your numbers are consistent with the earlier sheet’s scale and semantics. Below is the **clean integrated version** (so you can paste it into the same tuning doc), plus one small clarification to keep the math stable: when you add large CS boosts (C3 Clean), it should be paired with a mechanical rule that “higher CS helps the player *if* they’ve secured checksum/forgery proof,” otherwise it can feel like an unintended difficulty spike. You already imply that via the “Pell Clean impossible” flag—good. --- ## 6b) Forum clause pass deltas (additions) ### C3) Evidence Chain-of-Custody Audit (Archive) Record outcome as **Clean / Carve-out / Struck**. **Clean** - **CS +8** - **SB -2** - **ED -2** - **Mechanical flag:** `PELL_CLEAN_CUSTODY_DISABLED = true` (future Kade exhibits cannot be “Clean via Pell”; they start at **Questioned** unless independently sealed) **Carve-out** (scope narrowed to post-incident only) - **CS +4** - **SB +0** - **ED -1** - **Mechanical flag:** `CUSTODY_AUDIT_SCOPE = POST_INCIDENT_ONLY` (prior-death + pre-window records remain vulnerable; Pillar II remains harder in sequel/postgame) **Struck** - **ED +2** - **SB +1** - **WC -0.5** --- ### C5) Medical Autonomy & Clone Integrity Safeguards Record outcome as **Clean / Carve-out / Struck**. **Clean** - **IF -6** - **SB -1** - **WC +1** - **SP -0.5** *(if you keep SP integer-only, treat as: set a postgame flag that lowers escalation chance)* - **Mechanical flag:** `SMOOTHING_REQUIRES_LIVE_HEARING = true` and/or `CLINICAL_COVENANT_AVAILABLE = true` **Carve-out** (“oversight” or “continuity hazard exception”) - **IF -2** - **WC +0.25** - **SP +0.5** - **Mechanical flag:** `SECURITY_MEDICAL_ACCESS = true` (keeps RA vulnerable; Oram remains contested) **Struck** - **IF +3** - **WC -1** - **ED +1** --- ## Optional: Add-on deltas (for epilogue cleanliness score) ### Add-on A) Interim Security Council **Clean** - **SP -1** (cap reduces) - **ED -2** - **WC +0.5** **Carve-out** (stacked council) - **SP +0** - **ED -1** **Struck** - no global change ### Add-on B) Relief/Detention Pending Inquiry **Pass** - **SP = min(SP, 1)** - **ED -4** - **WC +1** - **Mechanical flag:** `KADE_REMOVED = true` --- # Forum Night Fear Tokens (Kade resource) — formula ### Step 1 — Base fear from ED (0–5) `FT_base = clamp(floor(ED / 20), 0, 5)` ### Step 2 — Force posture modifiers (0–3) - `FT_SP = SP - 1` *(SP1=0, SP2=1, SP3=2)* - `FT_LM = (LM == 3) ? 1 : 0` - `FT_force = clamp(FT_SP + FT_LM, 0, 3)` ### Step 3 — Unresolved incident pressure (0–4) `FT_incidents =` - +1 if last 2 attempts include **A3** - +1 if last 2 attempts include **B3** - +1 if last 2 attempts include **C3** - +1 if last 2 attempts include **D2 or D3** Clamp 0..4. ### Step 4 — Reputation accelerants (0–3) Start at 0, then: - +2 if `FABRICATION_KNOWN = true` - +1 if `EVASION_STIGMA = true` - +1 if `RA == 0` at finale start Then `FT_rep = clamp(total, 0, 3)`. ### Total `FT_total = clamp(FT_base + FT_force + FT_incidents + FT_rep, 0, 12)` **Typical bands (as you wrote):** - Golden: 2–3 - Mid: ~6 - Desperate: 11–12 --- ## Fear Token spend menu (consistent costs) During each clause exchange, Kade may spend: - **1 FT:** propose **carve-out** / weakening amendment - **2 FT:** attempt to **strike** a clause outright - **2 FT:** force **sealed exhibit posture** for one exchange *(unless C7 passed clean; then cost becomes 3 or is disallowed—your choice)* - **3 FT:** trigger early **witness crisis** (remove/contain Ren/Ward) --- ## Optional parity: Support Tokens (player-side) Your parallel calc is good. If you want it slightly more “procedural,” add +1 ST if **C7 is draftable** (Venn/recordkeeping infrastructure makes coordination easier), but it’s not required. --- If you still want the **one-page solver**, say what format you prefer: - spreadsheet-style pseudo-formulas, or - a compact rules block (inputs → outputs) suitable for implementation notes.

A compact rules block like this is exactly the right shape for implementation notes. Two tiny adjustments I’d recommend (optional) to make it robust in code, then I’ll give you the JSON-in/JSON-out reference implementation you offered. ## Optional micro-adjustments (keep or ignore) 1) **C2 draft condition:** requiring `(W_live || WC >= 0)` can let C2 draft even when you *can’t actually present anyone* in the finale (WC≥0 but all routes locked). If you want C2 to always be meaningful, set: ``` /// stricter C2_draft = W_live && SUPP_proof ``` Or keep your current logic but add an explicit “finale viability” check that enforces `W_live` for Ending 3. 2) **Quorum_ok:** you’ll want a single boolean for “can physically get 8 bodies in the room,” not just WC/SP. Consider: - `Quorum_ok = (EligibleVoters >= 8) && (AccessToForum == true)` where `EligibleVoters` is derived from story events, and `AccessToForum` from SP + safe conduct + barricades. If you don’t want to track EligibleVoters, your coarse check is fine. --- # Reference implementation (TypeScript, JSON in → JSON out) This mirrors your solver and returns all requested outputs. It assumes you already compute `FT_total` elsewhere (because it needs “recent incident outcomes” history). If you want, I can fold that in too. ```ts type ActBand = "COMPLACENT" | "PARANOID" | "DESPERATE"; type Band = "LOW" | "MID" | "HIGH"; type Trigger = "NO" | "OFFER_WITH_WARNING" | "YES"; export interface CampaignState { attemptCount: number; // Globals ED: number; SB: number; CS: number; IF: number; SP: number; LM: number; WC: number; RA: 0 | 1 | 2; FABRICATION_KNOWN: boolean; EVASION_STIGMA: boolean; // Proof flags M_phys: boolean; M_sys: boolean; M_test: boolean; SUPP_proof: boolean; W_live: boolean; L_custody: boolean; S_legal: boolean; S_med: boolean; S_treaty: boolean; V_leverage: boolean; SEC_split: boolean; K_direct: boolean; // Allies (for ST_est; optional but useful) Vale_allied?: boolean; Oram_allied?: boolean; Venn_allied?: boolean; Kwon_allied?: boolean; Ward_available?: boolean; Rigg_available?: boolean; Pell_flipped?: boolean; Ren_viable?: boolean; // Access flags have_SafeConduct_route?: boolean; // Fear token input (computed elsewhere or estimated) FT_total?: number; } export interface SolverOutput { Act: ActBand; draftable: { C1: boolean; C2: boolean; C3: boolean; C4: boolean; C5: boolean; C6: boolean; C7: boolean; AddOnA: boolean; AddOnB: boolean; }; MinBundle_draftable: boolean; FT_band: Band; ST_band: Band; ST_est: number; Quorum_ok: boolean; Trigger: Trigger; routeFeedback: { Eng_score: number; Legal_score: number; Venn_swing: number; hint: string; }; } const clamp = (x: number, lo: number, hi: number) => Math.max(lo, Math.min(hi, x)); export function solve(state: CampaignState): SolverOutput { // Step 1: Act band let Act: ActBand; if (state.ED < 35 && state.SP <= 1 && state.WC >= 0 && state.RA === 2) Act = "COMPLACENT"; else if (state.ED >= 70 || state.SP === 3 || state.WC <= -2 || state.RA === 0 || state.LM === 3) Act = "DESPERATE"; else Act = "PARANOID"; // Step 2: helper counts const M_count = (state.M_phys ? 1 : 0) + (state.M_sys ? 1 : 0) + (state.M_test ? 1 : 0); const S_any = state.S_legal || state.S_med || state.S_treaty; // Draftability const C1 = M_count >= 2; // Use your original permissive logic (can tighten to W_live && SUPP_proof) const C2 = (state.W_live || state.WC >= 0) && state.SUPP_proof; const C3 = state.L_custody; const C4 = state.M_sys || (state.M_phys && state.M_test); const C5 = state.S_med; const C6 = S_any; const C7 = state.V_leverage || state.S_treaty; const AddOnA = state.SEC_split; const AddOnB = state.K_direct && state.L_custody && (M_count >= 2) && state.W_live; const MinBundle_draftable = C1 && C2 && (C3 || C4) && C6 && C7; // Step 4: Fear band const FT_total = state.FT_total ?? 0; const FT_band: Band = FT_total <= 3 ? "LOW" : (FT_total <= 7 ? "MID" : "HIGH"); // Step 5: Support estimate const Vale = state.Vale_allied ? 1 : 0; const Oram = state.Oram_allied ? 1 : 0; const Venn = state.Venn_allied ? 1 : 0; const Kwon = state.Kwon_allied ? 1 : 0; const Ward = state.Ward_available ? 1 : 0; const Rigg = state.Rigg_available ? 1 : 0; const Pell = state.Pell_flipped ? 1 : 0; const Ren = state.Ren_viable ? 1 : 0; let ST_est = Vale + Oram + Venn + Kwon + Ward + Rigg + Pell + Ren; if (state.WC <= -2) ST_est -= 1; if (state.RA === 0) ST_est -= 1; ST_est = clamp(ST_est, 0, 8); const ST_band: Band = ST_est <= 2 ? "LOW" : (ST_est <= 5 ? "MID" : "HIGH"); // Step 6: Quorum plausibility + trigger const haveSafeConduct = state.have_SafeConduct_route ?? false; const Quorum_ok = (state.WC > -3) && (state.SP < 3 || haveSafeConduct); let Trigger: Trigger = "NO"; if (MinBundle_draftable && Quorum_ok) { if (FT_band === "HIGH" && ST_band === "LOW") Trigger = "OFFER_WITH_WARNING"; else Trigger = "YES"; } // Optional pacing lock if (Trigger !== "NO") { if (state.attemptCount < 6) Trigger = "NO"; else if (state.attemptCount < 10 && Trigger === "YES") Trigger = "OFFER_WITH_WARNING"; } // Step 7: Route feedback const Eng_score = (state.M_sys ? 1 : 0) + (state.M_phys ? 1 : 0) + (state.M_test ? 1 : 0) + (C4 ? 1 : 0); const Legal_score = (state.L_custody ? 1 : 0) + (state.S_med ? 1 : 0) + (state.S_legal ? 1 : 0) + (C3 ? 1 : 0) + (C6 ? 1 : 0); const Venn_swing = (state.V_leverage ? 1 : 0) + (state.S_treaty ? 1 : 0); let hint = ""; if (Eng_score > Legal_score) hint = "Close on mechanism. Shore up standing + minutes (C6/C7) and lock C2."; else if (Legal_score > Eng_score) hint = "Process case is strong. You still need mechanism proof for C1 (2-of-3)."; else hint = "Balanced progress. Prioritize what your next Pressure Card makes feasible."; if (Venn_swing >= 1) hint += " Observer leverage can make the finale cleaner (C7) and soften Sato."; return { Act, draftable: { C1, C2, C3, C4, C5, C6, C7, AddOnA, AddOnB }, MinBundle_draftable, FT_band, ST_band, ST_est, Quorum_ok, Trigger, routeFeedback: { Eng_score, Legal_score, Venn_swing, hint }, }; } ``` If you want the solver to be completely self-contained, send the exact data structure you’re using for “recent incident outcomes,” and I’ll integrate the **FT_total** computation (including the “last 2 attempts include A3/B3/C3/D2-or-D3” checks) into the same function.

Your self-contained solver is solid: it’s deterministic, minimal, and now enforces the important semantic constraints (C2 needs a live witness; quorum uses explicit fields when available). Two small implementation-quality notes, then I’ll give you a sample test vector + expected output so you can sanity-check quickly. ## Two small TypeScript notes (optional) 1) `IncidentGrade` isn’t used; you can remove it. 2) In `computeFTTotal`, `FT_incidents` is already 0–4, but if `historyLast2` can ever include malformed entries you may want a defensive clamp. Not necessary if inputs are controlled. --- ## Sample input JSON (golden-path-ready, attempt 8) This represents “skilled, just before Forum Night,” with explicit quorum fields used. ```json { "attemptCount": 8, "ED": 38, "SB": 52, "CS": 55, "IF": 48, "SP": 2, "LM": 1, "WC": 0, "RA": 2, "FABRICATION_KNOWN": false, "EVASION_STIGMA": false, "M_phys": true, "M_sys": true, "M_test": false, "SUPP_proof": true, "W_live": true, "L_custody": false, "S_legal": true, "S_med": false, "S_treaty": false, "V_leverage": true, "SEC_split": true, "K_direct": false, "Vale_allied": true, "Oram_allied": false, "Venn_allied": true, "Kwon_allied": false, "Ward_available": true, "Rigg_available": true, "Pell_flipped": false, "Ren_viable": false, "EligibleVoters": 9, "AccessToForum": true, "have_SafeConduct_route": true, "historyLast2": [ { "A": "A2", "B": "B2", "C": "C2", "D": "D1" }, { "A": "A2", "B": "B1", "C": "C2", "D": "D1" } ] } ``` ### Expected output highlights - **Act:** PARANOID (ED≥35 and SP=2) - **Draftable:** - C1 ✅ (M_count=2) - C2 ✅ (W_live && SUPP_proof) - C4 ✅ (M_sys true) - C6 ✅ (S_legal true) - C7 ✅ (V_leverage true) - C3 ❌, C5 ❌ - AddOnA ✅, AddOnB ❌ - **MinBundle_draftable:** ✅ (uses C4, skipping C3) - **FT_total:** - FT_base = floor(38/20)=1 - FT_force = (SP-1)=1, LM!=3 => 1 - FT_incidents = 0 (no A3/B3/C3/D2/3) - FT_rep = 0 - **FT_total = 2 → FT_band LOW** - **ST_est:** Vale+Venn+Ward+Rigg = 4 → **ST_band MID** - **Quorum_ok:** true (explicit: 9 and access true) - **Trigger:** with your pacing lock at attemptCount 8: **OFFER_WITH_WARNING** (because attemptCount < 10 and Trigger would otherwise be YES) That last line is the main “dial”: if you want skilled players to be able to go straight to finale on run 8 without being “warned,” change the pacing lock to: - allow **YES** at attemptCount ≥ 8 (or gate by tutorial-complete flag instead of count). --- ## One tweak suggestion (align with your 8–10 skilled target) Replace: ```ts else if (state.attemptCount < 10 && Trigger === "YES") Trigger = "OFFER_WITH_WARNING"; ``` with: ```ts else if (state.attemptCount < 8 && Trigger === "YES") Trigger = "OFFER_WITH_WARNING"; ``` This preserves the “don’t finale too early” goal while matching your golden path. --- If you paste one of your own playtest snapshots (even missing most ally fields), I can check the solver’s outputs and recommend: - thresholds for ED→act transitions, - whether FT_total is too sensitive to SP2/LM3, - and whether C1/C6/C7 unlocks cluster too early or too late.

Paste it. To make the check useful, include at least these fields in the “messy/desperate” vector: - **ED, SP, LM, WC, RA** - **historyLast2** with at least one of: A3/B3/C3/D2/D3 - **SUPP_proof + W_live** (since strict C2 hinges on them) - the core proof flags for the minimum bundle attempt: **M_phys/M_sys/M_test, S_legal/S_med/S_treaty, V_leverage** - **EligibleVoters + AccessToForum** (or omit both to exercise the coarse fallback) Once you send it, I’ll verify: - **FT_total** hits the intended 10–12 range, - whether **C2** becomes the bottleneck too often (W_live false), - and whether your intended “still winnable but ugly” cases fall into `OFFER_WITH_WARNING` rather than `NO`.