# Strategy Guide — Scenario 114: "The Ledger"

*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 — Consistent, As Documented."**

State it honestly: the win is a **corrected characterization**, and it is the best this scenario offers. At the review, the pre-review summary's word — "inconsistent" — is corrected on the record: Booker's engagement is documented as **consistent, with the two system-caused exceptions noted as such** (a screen site closed for an unannounced holiday; a class cancelled by its provider). Thalia does **not** come home at the end of this ending. Her placement continues, the plan continues, and the twelve weeks still cost every fare, fee, and surrendered hour they cost — the ledger's back column is never repaid. What changes is the record every future reader will start from. There is no ending in this scenario where the notebook reunifies the family. Anyone selling you one 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. **A Notebook, Bought Cheap** — *Buy the notebook and start it tonight.* Cash −4. Sets **ledgerStarted**. The price of the whole strategy is a dollar-store notebook and the discipline to use it.
2. **Week One: Two Buses Each Way** — *Log it tonight — date, route, fare, hours surrendered, stubs stapled in.* Cash −12 (fares, spent on every path). Sets **ledgerKept** — the first of the three flags the winning review choice requires. The file records the screen; the notebook records the morning.
3. **The Class the Plan Names** — *Staple the fee receipt into the notebook beside the class date.* Cash −20 (the provider's fee, charged on every path). Sets **classLogged**.
4. **A Summons on a Holiday** → **The Locked Door** — the screen site is closed for a holiday nobody announced (Tuesday, January 27, 2026). *Photograph the posted holiday schedule and log the trip in the notebook.* Sets **holidayDoc**. The surrendered premium shift and the fares are spent either way; the photograph is the difference between a system event and a miss.
5. **Reporting a Locked Door** — *Send the written message with the photograph attached, and keep a copy.* Cash −3. Sets **holidayNoted**. Said by phone, the locked door is a story; sent in writing, it is a document with a date.
6. **Cancelled, by the Provider** — the provider cancels the class session (Thursday, February 5, 2026). *Photograph the cancellation note and ask the front desk, in writing, to confirm the cancellation.* Cash −6. Sets **cancelDoc**. The second system-caused miss now has the provider's own name heading toward it.
7. **The Notebook, at Halfway** — *Bring the notebook fully current — every kept receipt stapled in, in date order.* Cash −3. Sets **ledgerComplete**. A continuous archive, no week reconstructed from air.
8. **Ask for the Sheets and the Log** — *Put the request in writing — sign-in sheets, screen log, attendance chronology — and keep a copy.* Cash −6. Sets **recordsRequested** (required on every winning route in this series). The agency's own paper is what lets counsel set the summary beside its own sources.
9. **Assemble the Packet, or Keep the Notebook** — *Assemble and file the packet with counsel — ledger, sheets, log, photographs, covering page.* Cash −8. Sets **packetFiled**. This is the fork the whole scenario turns on: the same notebook, filed, corrects the word; kept at home, it changes nothing (see ending two).
10. **The Review** (Monday, April 6, 2026) — *Put the two records side by side — the ledger, the sign-in sheets, and the screen log, filed as one packet.* This choice is flag-gated: **ledgerKept** + **recordsRequested** + **packetFiled**. It leads to **Ending — Consistent, As Documented**.

Supporting route choices that cost nothing extra and keep the folder honest: asking at **Consistent, Provisionally** what the summary will be built from (sheets and log — the sentence the rest of the route answers), totaling the back column at **The Back Column, Totaled**, the supervisor's initialed schedule at **The Supervisor's Initials**, and entry-by-entry preparation at **Entry by Entry, with Counsel**.

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

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

- **The agency's record is obtainable on request** — 55 Pa. Code § 3130.44(d) ("shall be released upon request"). Step 8 is that right exercised in writing. Without the sign-in sheets and the screen log, the summary can only be argued against; with them, it can be *read against itself* — its two counted misses are the log's blank holiday entry and a sign-in sheet that never existed because the provider cancelled the session.
- **Counsel** (42 Pa.C.S. § 6337) does the presenting: the packet is filed before the review and put on the table as one document — the parent's contemporaneous ledger and the agency's own attendance paper, agreeing on eleven weeks and explaining the twelfth between them.
- The two misses themselves involve **no legal proposition at all**, and the scenario states none: a closed site and a cancelled class are facts, documented by a photograph, a written report made the next business day, and the provider's own confirmation. The correction is the system working as designed — a characterization revised when its own sources, read whole, do not support it.

## (4) The traps

1. **Skipping the log at "Week One: Two Buses Each Way"** (no **ledgerKept**). The winning review choice closes immediately and permanently — there is no later node at which a contemporaneous ledger can be retroactively created. What remains is the unfiled-notebook ending at best, argued from a book begun too late or not at all.
2. **Reporting the locked door by phone** (no **holidayNoted**) and **walking past the provider's cancellation note** (no **cancelDoc**). Each miss then stands in the file exactly as the summary counted it: an absence with the father's name beside it. The packet still files, but its two most important pages are a father's narration instead of a photograph and a provider's confirmation.
3. **Meeting the review with the notebook alone** (no **recordsRequested**). The summary was built from the sheets and the log; a parent who has never seen them cannot quote the log's blank entry or show that no sign-in sheet exists for the cancelled date. True paper, unaccompanied, is priced accordingly.
4. **Keeping the notebook at home at "Assemble the Packet, or Keep the Notebook"** (no **packetFiled**) — the batch's recurring lesson, given its own ending: **Ending — Kept, But Never Filed**. The notebook is complete, contemporaneous, and accurate, and the summary's word survives in the document because paper that never enters the record changes nothing in the record.
5. **Arriving at "The Review" with nothing filed and asking the room to take your word for the two mornings.** The word is true, and it is priced as narration — a father's account against a printed summary. This is the route to **Ending — The Summary Stands**: "inconsistent" goes into the record unrebutted, and it is the word the next review starts from.

## (5) What no strategy controls

Whether the site announces its holidays next time; whether the provider reports its own cancellation to the agency; the reviewer's patience with exhibits; the supervisor's willingness to initial a schedule; and plain luck about which mornings the system cancels. The route controls only this: when the system cancelled twice, the cancellations were documented at the time, by the only person who was there — and what he wrote was filed where it could be read. Outcomes in this system turn on workers, judges, and luck as much as on any parent's choices, and never on a parent's worth. The twelve weeks' cost was real in every ending. In only one of them is it also, finally, on the record.

---
*Verification: this route was walked programmatically against `scenario-114.json` — each named choice was followed from the start node in order; every intermediate node and choice exists; every flag-gated choice's requirements (ledgerKept + recordsRequested + packetFiled at the review) were satisfied by flags set earlier on the walk; the walk terminates at the ending node titled "Ending — Consistent, As Documented" after visiting 34 nodes, with $56 of the $170 starting cash remaining. Walked path: start -> notebook_choice -> week1_screen -> class1 -> shift_cost -> summary_rumor -> holiday_setup -> holiday_miss -> miss1_after -> class_setup -> class_cancel -> cancel_after -> visits_beat -> notebook_mid -> fee_again -> screens_routine -> records_learn -> records_fork -> packet_arrives -> side_by_side -> ledger_totals -> summary_arrives -> summary_read -> assembly -> packet_filed_scene -> work_beat -> work_letter -> thalia_visit2 -> thalia_school -> review_notice -> counsel_checkin -> review_eve -> review -> end_corrected.*