# Strategy Guide — Scenario 111: "The Costs Column"

*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 — Explained, On the Record."**

State it honestly: this is a **partial** win, and it is the best this scenario offers. The visit record is corrected on the record — the written explanation, filed before the review with the pre-Saturday clerk's letter and the payment receipts attached, joins the six-word note so "no explanation" no longer travels alone — and the payment plan is reinstated through the letters' own stated process, on the documented posting dates. Zane does **not** come home at the end of this ending. He remains in kinship care with Sonya, his case continues, the old column continues to be paid down month by month, and one Saturday with a six-year-old is gone in every ending this scenario has. The win is that both files now say what actually happened. There is no ending in this scenario where the Saturday comes back. Anyone selling you one is selling you a different game.

**A withholding that governs this whole guide:** no statute about fines, costs, payment plans, or driving privileges is stated anywhere in the scenario or in this guide, because none is in the project's verified law set. Every procedural fact in the clerk's matter comes from the fictional letters' own faces: their stated deadlines, their enclosed forms, their named offices, their stated consequences, in their own words. The letters are the process, followed exactly — that is the strategy, and it needs no doctrine.

## (2) The route

Verified by walking the scenario graph from the start node (see the verification note at the end). The walk passes, in order, through: The Clerk's Letter; What Lapsed, Exactly; The Plan That Ran; Warm Paper, Kept or Lost; Paid, Then Posted; The Saturday Decision; The Empty Chair; No Explanation; The Balance, Grown; Receipts Against a Ledger; Two Files, One Packet; Ask for the Visit Record; Six Words, Officially; The Explanation, Filed or Spoken; Joined, Not Argued; The Letters' Own Process; Filed, in Its Own Language; The Next Visit, Kept; Two Saturdays, in Two Piles; The Review. Key decision points:

1. **Warm Paper, Kept or Lost** — *Gather both receipts tonight and keep them with the letter, in date order.* Cash −3. Sets **receiptsKept**. The two receipts — paid on their dates, posted by the processor days later across the plan's due line — are the difference between a man who paid late and a posting that lagged, and they are the load-bearing paper for both files.
2. **The Saturday Decision** — *Do not drive against the letter — miss the visit, and stay off the road until the letter's process is answered.* Sets **didNotDrive**. The first letter, dated Monday, August 17, 2026, predates the Saturday visit (Saturday, August 22, 2026) and states its consequence in its own words. Missing the visit is the painful, correct-sized answer to a paper problem; driving against the letter converts it, as the third ending shows.
3. **Ask for the Visit Record** — *Sign the written request for the record — visit notes and draft summary.* Cash −3. Sets **recordsRequested**. This puts the note's exact six words — "Father missed visit, no explanation" — in the father's hands while the draft summary carrying them is still soft enough to be joined.
4. **The Explanation, Filed or Spoken** — *File the written explanation before the review — first letter and receipts attached.* Cash −4. Sets **explanationFiled**. Its strength is sequence: the letter attached to it was mailed before the Saturday it explains, so the explanation cannot have been invented afterward. Filed, it joins the note; spoken, it would only argue with it.
5. **The Letters' Own Process** — *File the reinstatement request through the letters' own process — form and receipts, inside the stated window.* Cash −5. Sets **reinstatementFiled**. The second letter stated its deadline — Friday, September 18, 2026 — and the request is filed Wednesday, September 16, 2026, in the ledger's own language: its form, plus receipts whose dates sit beside the ledger's.
6. **The Review** — *Present the joined record — the explanation filed before today, the pre-Saturday letter, and the receipts, with the plan's reinstatement filed.* This choice is flag-gated: it is only available with **receiptsKept** + **recordsRequested** + **explanationFiled** + **reinstatementFiled** all set, and with **droveAnyway** never set. It leads to **Ending — Explained, On the Record**.

Supporting route choices that cost nothing and keep the route honest: keeping the next visit (Saturday, September 19, 2026) by a road the letters' process leaves open, at **The Next Visit, Kept**, so the review reads two Saturdays — one missed and explained, one kept — and assembling the packet in strict date order at **Two Saturdays, in Two Piles**, because in this scenario date order is not technique; the letter predating the Saturday is the proof.

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

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

- **The case record is available on written request** — 55 Pa. Code § 3130.44(d) ("shall be released upon request"). Step 3 is that right, exercised in writing in Zane's case: it is what lets the explanation answer the note's exact words instead of a summary of them, and what surfaces the draft summary while its lines can still be joined.
- **Counsel files the explanation where the note lives** (42 Pa.C.S. § 6337). Ms. Rutledge's work is joining, not eloquence: one paragraph, two attachments, filed before the review, so that every future reader of that Saturday reads note and reason in the order they happened.
- **Everything in the clerk's matter is the letters' own process, followed on the letters' own terms** — stated without citation on purpose. The letters state the lapse, the balance, the forms, the offices, the deadlines, and the consequences in their own words; the reinstatement is won by answering a ledger in its own language (its form, with receipts whose payment dates answer its posted dates) inside its own stated window. No fines, costs, or driving rule is claimed anywhere, because the route never needs one: it needs receipts and dates, filed twice — once in each file the Saturday touched.

## (4) The traps

1. **Leaving the receipts scattered at "Warm Paper, Kept or Lost"** because you know you paid. You did, and the ledger has already published its version — late, late, lapsed — in a column that does not attend kitchen tables. Cost: no **receiptsKept**, and both later filings lose their attachments; the best presentation at the review closes.
2. **Driving anyway at "The Saturday Decision"** because the visit matters more than a clerk's column. The visit is kept and the gamble, that day, is won — and a paper problem becomes an exposure that no receipt can pay down. This route reaches **"Ending — A Paper Problem, Driven Into a Legal One,"** and it closes the winning presentation outright: the joined-record choice is unavailable to a route that drove.
3. **Explaining it at the review at "The Explanation, Filed or Spoken"** because your voice, and Sonya's, will carry it. Voices carry rooms; files carry reviews, and every room after this one. The note was filed weeks before the review convened and will be quoted long after the voices leave. That route reaches **"Ending — No Explanation, Still Standing."**
4. **Letting the letters wait at "The Letters' Own Process"** because Zane's review matters more than an old column. Both matter, and columns unattended do not stay columns — the second letter's grown balance and stated consequence are its whole message. Cost: no **reinstatementFiled**, the plan stands lapsed on its own paper, and the best presentation closes.

## (5) What no strategy controls

Whether the clerk's office reads the same receipts generously; whether a different reviewer corrects the note and still weighs the missed visit heavily; whether the processor lags again next quarter, in a month whose receipts end up in a coat that gets donated; whether Sonya's labeled binder — luck wearing an apron — is there to show a father his own visit note. Zane's Saturdays themselves are not controlled by any of this: one of them is gone in every ending, and no filing returns it. What the route controls is the paper: receipts gathered before a Saturday complicated them, a record requested while a draft was soft, an explanation filed instead of spoken, a reinstatement sought through the very process the letters offered, in their own window — and one refusal, on one Saturday, to let a ledger's dates be the only dates in the room, purchased at the price the scenario never hides. Outcomes in this system turn on clerks, reviewers, processors, and luck as much as on any father's choices.

---
*Verification: this route was walked programmatically against `scenario-111.json` — each named choice was followed from the start node in order; every intermediate node and choice exists; every flag-gated choice's requirements were satisfied by flags set earlier on the walk (flags at the ending: didNotDrive, explanationFiled, receiptsKept, recordsRequested, reinstatementFiled); cash never went negative on the walk. Walked path: start → letter_close → old_plan → receipts_choice → receipts_found → saturday_choice → visit_missed → note_phrase → second_letter → ledger_beat → counsel_visit → records_fork → record_arrives → explanation_choice → explanation_filed → reinstatement_choice → reinstatement_filed → zane_visit → prep → review → end_win. The walk terminates at the ending node titled "Ending — Explained, On the Record" after visiting 21 nodes, with $141 of the $160 starting cash remaining.*