# Strategy Guide — Scenario 107: "The Card That Stopped"

*Game documentation for a fictional simulation in "The First 90 Days" (Tactic Watch). The family, the case, and every choice below are fictional. This guide is general information about how the scenario is built — it is not legal advice for any real case.*

## (1) The win

**Best ending: "Ending — Restored, Going Forward."**

State it honestly: this is a **partial** win, and it is the best this scenario offers. At the meeting on Wednesday, May 20, 2026, the closure is attributed on the record to the notice failure — a closure notice mailed to the previous address, in a spring when the agency's own file had carried the new address since Monday, February 9, 2026 — and the household's benefits for the members still at home are restored going forward, with the corrected address standing in writing in both systems. Camille does **not** get the strained weeks back, Zora — in kinship care with her aunt throughout, as she was from before the first page — remains placed, and the case is still open. One thing more, stated as plainly in the guide as in the debrief: **Zora's own portion while she is placed is a separate question that this scenario deliberately does not resolve.** It has its own papers and its own room, and no route in this game settles it. Anyone selling you a bigger win is selling you a different game.

## (2) The route

Verified by walking the scenario graph from the start node (see the verification note at the end). Key decision points, in order — node title, winning choice, and what it changes:

1. **The Number on the Back of the Card** — *Stay on the line until the voice reads you the exact address the notice was mailed to.* Hidden item: the closure's "failure to respond" framing enters the file's quiet record, together with the fact that it rests on a mailed notice. Explanations are fog; an exact address is a fact, and this one turns out to be the whole case.
2. **The Old Address, Read Aloud** — *Correct the address in writing to BOTH offices, ask in writing for the notice to be re-sent, and attach a dated written statement of the facts.* Cash −4. Sets **addressCorrected**; hidden item: the written correction to both systems. This is the single most important choice in the scenario: it is the moment the address stops living in one system's file and one mother's memory, and starts living, dated, in both systems at once.
3. **Two Envelopes** — *Keep both confirmations with the statement.* Hidden item: both offices' written confirmations. The system has now documented its own correction — the strongest kind of document there is, because its authors are the systems.
4. **Ask for the File, or Don't** — *Put the request in writing — chronology and address entries — and keep a copy.* Cash −3. Sets **recordsRequested**. The packet that arrives shows the load-bearing page: the agency file's own entry recording the new address on Monday, February 9, 2026, from the conversation of Monday, January 26, 2026 — weeks before Zora's placement on Monday, March 16, 2026, and long before the card declined on Monday, April 6, 2026.
5. **The File's Own Hand** — *Keep the packet with the statement and the confirmations.* Hidden item: the packet itself, preserved in date order. Folder and closure letter now disagree about the same spring, in writing, with dates — and one side of the disagreement is in the system's own hand.
6. **One Page, or a Story** — *Build the one-page chronology from the statement, the confirmations, and the file's own entry, in date order.* Sets **paperAssembled**; hidden item: the assembled chronology. Six dated lines — address given Monday, January 26, 2026; address recorded Monday, February 9, 2026; placement Monday, March 16, 2026; card declined Monday, April 6, 2026; corrections sent Monday, April 13, 2026; packet received Monday, April 27, 2026 — and no adjectives for anyone to argue with.
7. **The Meeting** — *Put the dated paper on the table — the statement, both address confirmations, and the case file's own address entry.* This choice is flag-gated: it is only available with **addressCorrected** + **recordsRequested** + **paperAssembled** all set. It leads to **Ending — Restored, Going Forward**. (The meeting trip itself costs $6 of fare at **The Night Before the Meeting**; you finish the route with $137 of the $150 start.)

Supporting route texture: **The Flyer in the Folder** is where the record right is learned — it is taught by a waiting-room flyer, because in real cases it very often is — and **Failure to Respond** (the closure letter of Monday, May 11, 2026) is where the player reads the sentence the meeting will start from, in the file's own grammar, before deciding what will sit beside it.

## (3) Why this wins — the law as it is supposed to work

Only principles from the scenario's verified set are stated here:

- **Agency records are obtainable on request** — 55 Pa. Code § 3130.44(d) ("shall be released upon request"). Step 4 is that right, exercised in writing. It matters because the case file's dated address entry is the strongest evidence in the scenario, and you cannot quote an entry you have never been shown.
- **Counsel presents the record in the room where the closure is weighed** — the right to counsel, and to appointed counsel if a parent cannot afford one (42 Pa.C.S. § 6337). The lawyer's work here is not argument in the dramatic sense; it is sequence — asking that the record be completed before the "failure to respond" line is weighed.
- **No benefit rule is stated, in the scenario or in this guide, because none is in the verified set and none is needed.** Benefit programs have their own rulebooks; this scenario deliberately states no amount, eligibility rule, or payee rule as law. The closure notice, the confirmations, and the meeting letter state their own instructions on their faces, inside the fiction, and the story turns on notices, addresses, dates, and paper — not on the rulebook.
- Everything else on the route is generic process, deliberately without citation: correct an address **in writing to every system that holds a version of you**; ask **in writing** for a missed notice to be re-sent; state the facts once, with dates, while they are new; keep the confirmations when they come back. The scenario's thesis is that meetings weigh the record that exists when they sit — and that a parent can, lawfully and cheaply, change what that record contains about a letter she never received.

## (4) The traps

1. **Correcting the address out loud at "The Old Address, Read Aloud"** because both voices sounded helpful and it is faster. Cost: no **addressCorrected**, and no dated anything in either system. The meeting's gated presentation closes, and the route ends at **Ending — Failure to Respond, As Filed** — the closure stands as written, and the corrected address lives only where it was spoken.
2. **Waiting for the meeting at "Ask for the File, or Don't"** to explain the two systems in person. Cost: no **recordsRequested**, so the file's own February entry is never seen, never quoted, and never set beside the closure letter. A spoken account is believed personally and set aside professionally; the ending is again **Ending — Failure to Respond, As Filed**.
3. **Going in with the story at "One Page, or a Story"** because the story is clear, in order, and true. Cost: no **paperAssembled**. The closure letter — one line, printed, already read — outlasts the telling, and the ending is **Ending — Failure to Respond, As Filed**.
4. **Presenting partial paper at "The Meeting."** Cost: the whole route's assembly work. Half a chronology is an argument with missing premises; the gated choice exists precisely because the room can only complete a record that arrives complete.

## (5) What no strategy controls

Why the benefits office never received an address the agency file held for months — a handoff, a queue, a form nobody remembers not sending; the scenario deliberately never shows it, because the parent never learns it either. Whether a future letter goes astray again, and whether the next worker in either system reads the confirmations before writing the next sentence. The meeting's temperament: a different one could note the chronology and restore less, or later, because the household's strained weeks are real too and no order replays them. And, by design, Zora's own portion while placed: it is governed by papers and rooms this scenario never enters, and this guide does not pretend a route through a grocery-store closure settles it. The route controls none of that. It controls only whether, when the uncontrollable is weighed, the spring arrives in the room as a documented notice failure or as an unexplained silence with a mother's name beside it. Outcomes in this system turn on workers, offices, and luck as much as on any parent's choices; the strategy's claim is the narrower one the scenario is named for — when the system's letter goes to the wrong home, make the system's own file say so.

---
*Verification: this route was walked programmatically against `scenario-107.json` — each named choice was followed from the start node in order (start → call_maze → two_systems → written_moves → waiting_weeks → flyer_beat → records_fork → packet_arrives → closure_stands → prep → chronology_built → meeting_eve → meeting → end_win); every intermediate node and choice exists; every flag-gated choice's requirements were satisfied by flags set earlier on the walk; the walk terminates at the ending node titled "Ending — Restored, Going Forward" after visiting 14 nodes, with $137 of the $150 starting cash remaining.*