# Strategy Guide — Scenario 116: "The Summary Line"

*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 — Corrected, Entry by Entry."**

State it honestly: this is the capstone, and it is a **win**, labeled as one — with the reason stated, as this series requires. At the permanency review, the summary line "unresolved financial instability" is corrected entry by entry on the record and struck, replaced by the three entries in their true shapes; on the corrected file the court orders Leona's return home on a short transition schedule. The guide can say the record earned it, and here is why that sentence is permitted: every other element of the case — treatment completed, visits kept, work steady — was **already documented as complete** before the phrase appeared, and the *only* obstacle to the case's existing direction was three money entries that the file's own paper refuted. The win is not that a mother argued well. It is that an audit, built entirely from the system's own documents, was filed in front of the room that owned the phrase, at a review taken **before** the fifteen-month date — with a documented-exception packet already on file as backstop, unneeded. Nothing less complete earns this ending, and the other endings show the prices of each incompleteness.

## (2) The route

Verified by walking the scenario graph from the start node (see the verification note at the end). The clock, first, because the route is a race: Leona entered care **Monday, September 1, 2025**. Fifteen calendar months from entry is **Tuesday, December 1, 2026** — computed programmatically (`add_months`), day 60 of a story that opens Friday, October 2, 2026 (month 14). The review is taken at day 59, **Monday, November 30, 2026** — one day before the date. Key decision points, in order:

1. **Ask for the Audit's Pages** — *Put the request in writing — plan, support ledger, posting record, benefits correspondence — and keep a copy.* Cash −6. Sets **recordsRequested** (required on every winning route in this series, and the gate on the packet below). The audit's proving documents are, all three, the agency's own pages.
2. **The Plan's Own Page** (tab one: the arrearage) — *Assemble entry one in writing — the plan page, the pause note, and the treatment admission and discharge dates.* Cash −4. Sets **entry1Doc**. The arrearage accrued during the two months Althea was in inpatient treatment, while the plan's own note recorded the goal as paused. The exhibit is the file contradicting its summary, in its own handwriting.
3. **Paid on One Date, Posted on Another** (tab two: the "missed payment") — *Assemble entry two in writing — the receipt and the posting record, copied as one two-date exhibit.* Cash −4. Sets **entry2Doc**. A posting lag: paid on its date (receipt, from her folder's visit envelope), posted five days later in the system's own record. The summary read one column.
4. **The Envelope in the File** (tab three: the benefits gap) — *Assemble entry three in writing — closure letter, mailing record, and the file's own record of the move, in date order.* Cash −5. Sets **entry3Doc**. The closure letter was mailed to her prior address after her move was on file — the Scenario 115 pattern, now summarized upward as character.
5. **Assemble the Packet, Raise It Aloud, or Wait** — *Assemble and file the entry-by-entry correction packet with counsel.* Cash −8. Sets **auditPacket**. Flag-gated: **recordsRequested**. Filed whole or not at all — the phrase needs only one surviving entry to survive (see ending two).
6. **The Backstop: A Packet for the Date** — *Build and file the written exception packet with counsel, before the fifteen-month date.* Cash −6. Sets **exceptionPacket**. The backstop speaks to December 1, not to the review: if the date arrives before the file is truthful, the filing decision must reckon with a documented exception claim instead of a phrase.
7. **Two Slots in One Letter** — *Take the first slot — the review before the fifteenth month.* A route choice, not a flag: the later slot leads directly to **Ending — The Date Strikes First**, petition filed on the uncorrected file while the audit waits for its calmer morning.
8. **The Permanency Review** (Monday, November 30, 2026) — *Correct the line entry by entry — the plan's pause note, the two posting dates, the letter's own envelope, with the exception packet already on file.* Flag-gated: **recordsRequested** + **entry1Doc** + **entry2Doc** + **entry3Doc** + **auditPacket** + **exceptionPacket**. It leads to **Ending — Corrected, Entry by Entry**.

Supporting route structure: the control test at **The Binder, Checked Against the Summary** (no claim is made at the review without a page number in the binder), the queue's own flat explanation filed ahead of tab two's receipt at **The Queue, in Plain Words**, and the cold-reader turn at **A New Reader, Reading Cold** — the new supervisor who will sign any filing decision can only read what the packets put in the file.

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

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

- **The record is obtainable on request** — 55 Pa. Code § 3130.44(d) ("shall be released upon request"). The entire audit is that right exercised with named pages: the plan, the ledger, the posting record, the correspondence. Each entry is corrected *from the file's own documents* — which is why the room corrects them itself, out loud, instead of weighing a mother's word against a summary.
- **The review's determinations are made on the record before the court** — at a permanency review the court makes the determinations the law lists for reviews (42 Pa.C.S. § 6351(f), including the placement-duration determination, § 6351(f)(9)'s territory). Counsel's move is procedural and exact: correct each entry from its documents *before* the determinations are made, so the determinations rest on a truthful file. A record whose three load-bearing entries are corrected cannot carry the phrase built from them.
- **The ASFA backstop, in its disciplined form.** At 15 of the most recent 22 months, the agency is generally to file a termination petition **unless an exception is documented**: (i) the child is being cared for by a relative, (ii) a documented compelling reason that filing would not serve the child, or (iii) the agency has not provided services it identified as necessary for the child's safe return (42 U.S.C. § 675(5)(E)). The exception is **record-dependent** — it exists as an argument only to the extent the file documents it — and it speaks to the **filing decision** only. Here it was filed and never needed, because the correction at the earlier review removed the phrase the filing decision would have rested on. Had a petition been filed anyway, the agency would still have to prove its grounds by **clear and convincing evidence** at a hearing; no ending in this scenario depicts or decides such a hearing.
- **Counsel** throughout is the parent's right (42 Pa.C.S. § 6337) — used here for its least dramatic function: an audit, assembled into filings, before dated decisions are made from the file.

## (4) The traps

1. **Leaving any one tab unassembled** (no **entry1Doc**, **entry2Doc**, or **entry3Doc**). The review node carries a separate gated choice for each single-missing-entry combination, and all three lead to the same place: **Ending — The Phrase Survives on One Entry**. Two entries are corrected on the record; the phrase re-forms around the survivor, shorter and weaker and still the file's description of her money. Partial paper partially works, in exact proportion — this scenario is the batch's proof of that sentence.
2. **Auditing from the folder alone** (no **recordsRequested**). Her folder proves her life; the summary was not built from it, and the packet choice at the assembly node is gated on the record request — it never appears. What remains is the oral raise and waiting, both of which end at **Ending — The Phrase Stands Whole**.
3. **Raising the audit orally** (sets **oralRaised**). Three true stories, clearly told, filed in a transcript nobody summarizes — against a phrase sitting in a summary everybody reads. The exhibits stay in a binder in counsel's office.
4. **Taking the later review slot.** The calendar trap, priced in full by **Ending — The Date Strikes First**: the agency files on December 1 on the file as the date found it, and the audit debuts in a harder proceeding as an exhibit about grounds, instead of correcting a summary at a review. Reviews can be rescheduled. Filing dates are not reviews.

## (5) What no strategy controls

The new supervisor's reading of the same packets — a colder reader corrects two entries and keeps the phrase on the third, and the route's paper then travels into the proceeding of ending two or four. The summary writer who read one column; the worker who wrote a pause note and never carried it across her own file; the queue's speed; the court's calendar and its two polite slots; and luck, in the specific form of which offices keep their envelopes. The route controls only this: every entry was audited from documents, the audit was filed before the room that owned the phrase, the backstop was filed before the date that owned the calendar, and the review was taken while the file could still change what the date would do. Outcomes in this system turn on workers, supervisors, judges, and luck as much as on any parent's choices — and never on a parent's worth.

---
*Verification: this route was walked programmatically against `scenario-116.json` — each named choice was followed from the start node in order; every intermediate node and choice exists; every flag-gated choice's requirements (recordsRequested at the packet; recordsRequested + entry1Doc + entry2Doc + entry3Doc + auditPacket + exceptionPacket at the review) were satisfied by flags set earlier on the walk; the ASFA arithmetic was recomputed in the generator and asserted (entry Monday, September 1, 2025 + 15 calendar months = Tuesday, December 1, 2026 = dayOffset 60 from the Friday, October 2, 2026 start; the review node sits at dayOffset 59, Monday, November 30, 2026, one day before the date); the walk terminates at the ending node titled "Ending — Corrected, Entry by Entry" after visiting 32 nodes, with $137 of the $170 starting cash remaining. Walked path: start -> summary_line -> counsel_meet -> three_entries -> folder_beat -> records_learn -> records_fork -> packet_arrives -> audit_plan -> binder_check -> entry1_setup -> entry1_doc -> treatment_dates -> ledger_page -> entry2_setup -> entry2_doc -> posting_office -> queue_explain -> entry3_setup -> entry3_doc -> address_proof -> summary_draft116 -> leona_visit -> assembly116 -> filed116 -> exception_beat -> cold_read -> review_prep116 -> calendar_choice -> morning116 -> review116 -> end_corrected116.*