# STRATEGY GUIDE — Scenario 30: "The Third Removal"

*Game documentation for a fictional simulation ("The First 90 Days," Tactic Watch). This guide describes choices inside this scenario only. It is general information about how the scenario is built — not legal advice for any real case.*

*Route verified programmatically against `scenario-30.json`: the walk below was scripted from the start node, following each listed choice, and reaches the named ending (see "Path check" at the end).*

---

## (1) The win

**Ending — Closed on the Facts of Now**

Stated honestly: the win in this scenario is a closure, not an erasure. The new assessment is decided on the present facts — the referral's actual words (school absences and daytime sleep; no injury alleged), the school's own confirmed numbers, and a present-tense home visit — and the case closes without a petition. The file itself still exists, as files do, and the guide does not oversell the ending: a future report would be read against that file. What the route wins is that the future reader would meet the file's wrong lines already corrected, with their sources clipped beside them — and that this autumn was decided as this autumn.

## (2) The route

Key decision points, in order, using the scenario's node titles:

1. **Then and Now, in Writing** — Choose: *"Start the packet with this autumn, sourced and dated."*
   Changes: sets FLAG `presentPacketStarted`; hidden item records the present-facts packet begun. It establishes the reading order — NOW first, THEN labelled — that the whole scenario turns on. (The oral-cooperation path stays playable, but the history gets summarized past-first.)

2. **The Request Goes In** — Choose: *"Request the record in writing and keep the stamped copy."*
   Changes: sets FLAG `recordsRequested`; cash −10; hidden item records the complete-record request, including the scored assessment (form, ratings, outcome). This is the move that surfaces the stale line. (The phone-request path also sets `recordsRequested`, but only after a written re-request — and ten days later, in the fiction of the file.)

3. **How a Correction Travels** — Choose: *"File the written correction, certificate and lease attached, and keep the stamped copy."*
   Changes: sets FLAG `correctionFiled`; cash −12; hidden item records the correction paired to the lines it corrects ("declined parenting support sessions, 2021" answered by the completion certificate; the two-year-old address answered by the current lease). A filed correction is read with the error; a verbal one is summarized as a "dispute."

4. **A Second Reader** — Choose: *"Take the packet to the clinic and the school first — checked, confirmed, then submitted."*
   Changes: sets FLAG `packetChecked`; cash −15; hidden item records counsel's review and the school's confirmation of the attendance page against its own system. The packet's key number — seven of eleven absences excused — stops being the parent's claim and becomes the school's number.

5. **How Facts Travel** — Choose: *"Send it formally — the letter, the packet, the acknowledgment kept."*
   Changes: sets FLAG `formallySubmitted`; hidden item records the packet acknowledged as the parent's account. This routes to **The Working File Opens in Autumn**, so the decision meeting opens with the present facts rather than with a three-line summary ending in the history.

6. **The Decision Meeting** — Choose: *"Hear the decision framed on the present facts — the packet read first."*
   Changes: routes to **Deciding on the Present Facts**, closing the removal branch (**Removal Sought on the Strength of History** → **The Third Removal** → **The Shelter Care Hearing**) and keeping the three closure endings open.

7. **Deciding on the Present Facts** — Choose: *"Accept closure on the present facts, and confirm it in writing."*
   Changes: reaches the win ending above. (The other choices reach the partial wins: "Ending — Services Again, on Paper" and "Ending — Closed, but the Stale Line Stays.")

Supporting moves on the same route: reading the referral before answering (**What the Report Actually Says**), keeping the three history lists — accurate / stale / never true — before correcting anything (**Stale, Wrong, and Never True**), and asking that the home-visit note record what was seen that day, dated that day (**The Visit, in the Present Tense**).

**Full verified route:** The Third Knock → What the Report Actually Says → History, Read Aloud → Then and Now, in Writing → Now, First → Your Own File → The Request Goes In → Reading the Whole Folder → Stale, Wrong, and Never True → How a Correction Travels → Filed, With Sources → The Present-Facts Packet → A Second Reader → Checked and Confirmed → The Visit, in the Present Tense → What the Visit Note Says → The Supervisor Review → How Facts Travel → The Working File Opens in Autumn → The Decision Meeting → Deciding on the Present Facts → **Ending — Closed on the Facts of Now**

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

The route operationalizes only principles from the scenario's verified legal set:

- **The record on request.** The record "shall be released upon request" (55 Pa. Code § 3130.44(d)). The route uses this for the complete record — prior cases and the new scored assessment, form, item ratings, outcome — because the correction strategy is impossible until the parent has read what everyone else will read. Hidden items in this scenario are history entries read as current; the request is the only move that lets the parent see them as entries, with dates.
- **Counsel.** The parent's right to counsel, and to appointed counsel if unaffordable (42 Pa.C.S. § 6337), is what makes the clinic review of the packet — and the THEN/NOW separation as a drafting discipline — available inside the story.
- **Disclosure, with its limit stated.** Adjudication-phase disclosure of assessment/discovery material is addressed by Pa.R.J.C.P. 1340(B)(1); the scenario states in-game that Rule 1340's application to the Universal Assessment is untested. The route rests on the quotable regulation, not the untested extension.
- **The burden, applied to the present.** Dependency decisions require clear and convincing evidence. The packet's function is to make that burden be carried about the facts of now — dated, sourced, checkable — rather than discharged by a history whose episodes are accurate but closed. Separating THEN from NOW in writing is how a parent gives the burden something present-tense to be weighed against.
- **The 72-hour clock (the branch the win avoids).** If removal occurs, a shelter care hearing must be held within 72 hours (42 Pa.C.S. § 6332; 23 Pa.C.S. § 6315(d)). In this scenario's removal branch, removal on day 71 is followed by the hearing on day 74 — exactly three days. The guide notes the clock because its existence is why the packet must be built before any hearing is scheduled: three days is enough to present a packet that exists, and not enough to build one.

## (4) The traps

1. **Answering history questions fully and orally first, at Then and Now, in Writing.** Tempting because cooperation feels like the whole duty — and the cooperation is real. Cost: the notes are arranged past-first, this autumn becomes a footnote to three closed episodes, and the parent's own account enters the file in the file's order instead of hers.
2. **Asking for the record by phone, at The Request Goes In.** Tempting because it saves a trip on a workday. Cost: no stamped copy, no provable date, no packet that month — the written re-request costs ten days the scenario does not give back, and the stale line is found late instead of early.
3. **Telling the caseworker the corrections instead of filing them, at How a Correction Travels.** Tempting because the worker is reasonable and believes her. Cost: the file records "mother disputes a 2021 entry" while the completion certificate stays in a drawer. A dispute is a claim; a filed correction with its source attached is a fact with a paperclip — the scenario's own sentence, and its central mechanic.
4. **Letting the packet travel with the worker's summary, at How Facts Travel.** Tempting at the end of a long case, when the parent is tired and the worker is fair. Cost: nine sourced pages become three lines ending in "extensive history," the decision meeting opens with the folder, and the live branch becomes removal sought on the strength of history — a shelter care hearing under a 72-hour clock that the parent must fight with a packet the room may never read in full.

## (5) What no strategy controls

Who is in the decision room, what their last case was like, whether a supervisor reads the packet or the folder first on a crowded morning, whether a judge on the removal branch reads in the same order — none of that is in the parent's hands, in this scenario or outside it. The scenario is explicit that the same packet can carry a family to closure in one room and to a hearing in another, and that parents reach the hearing ending with strong paper. Workers, supervisors, judges, and luck hold pieces of every outcome. What the route controls is the only thing a parent in this system has ever fully controlled: what exists to be read, in what order, with what sources — built before it is urgently needed. The debriefs say so, and so does this guide.

---

**Path check (programmatic):** route node sequence above walked from `start` in `scenario-30.json` → ending reached: **Ending — Closed on the Facts of Now** (`end_closed`). ✔