# STRATEGY GUIDE — Scenario 20: "The Daycare Letter"

*Game documentation for a fictional simulation. This guide describes how to reach the best ending in this scenario. It is general information about the scenario's design, not legal advice, and not guidance for any real case.*

*Verified against `scenario-20.json`: the route below was walked programmatically, choice by choice, and reaches the ending named in Section 1. Exact node path: `start → read_letter → daycare → two_clocks → counsel → appeal_filed → records_dep → service_plan → visit → evidence_packet → divided → gather → prehearing → hearing_strong → review_prep_exp → review_exp → decision_exp → end_expunged`.*

---

## 1. The win

**"Ending — Expunged, and Read Accurately"** (node `end_expunged`).

Be honest about what this win is, because the scenario is: it is a **partial win, and it does not oversell itself**. The indicated report about Ana's fall is ordered expunged, and the June 1 dependency review reads Lena's service-plan progress accurately on its own record. But Eli is **not** ordered home at that review, the spring's lost daycare income is not repaid, and months off the classroom rota stay lost. What the win actually consists of is three bounded things: a name removed from the database, an outcome letter that lets the daycare-scheduling conversation reopen under the employer's own stated process, and a dependency record that enters the summer legible, credited, and moving. In this scenario, that is the ceiling — and reaching it requires winning on **two separate tracks at once**, which is why the tier is Hard.

## 2. The route

Key decision points in order, by node title, with the winning choice and what it changes:

1. **"Two Envelopes, One Kitchen Table" (`start`)** — *Read the whole letter again, slowly, with a pen.* Keeps the drawer path from becoming the story; every later clock depends on the back page being read on day 0.
2. **"What the Letter Actually Says" (`read_letter`)** — *Tell Ms. Bell at Sunflower before she hears it any other way.* HIDDEN + the circled deadline (Sunday, May 3, 2026). You learn the employer's stated process from the employer, in writing, instead of by rumor.
3. **"Sunflower's Process" (`daycare`)** — *Ask for the pause in writing, with the date on it* (the alternative choice also advances). HIDDEN + the dated schedule pause. No cash cost; the cost is information discipline.
4. **"Two Clocks" (`two_clocks`)** — *Write both dates on the calendar, in two colors.* HIDDEN + both clocks noted (May 3 CPSL; June 1 dependency). This is the scenario's thesis in one choice: two tracks, visibly separate.
5. **"The Lawyer Who Is Already Yours" (`counsel`)** — *File the written appeal this week, while the gathering of paper happens around it.* FLAG: `appealFiled`; HIDDEN + the burden note. **This is the single most load-bearing choice in the scenario** — it starts the disclosure machinery and answers the May 3 clock in February, leaving all three endings still open but making the win reachable.
6. **"Filed, Stamped, Copied" (`appeal_filed`)** — *Now request Eli's dependency case record, in writing, under § 3130.44(d).* FLAG: `recordsRequested` (set exactly here, and nowhere else); HIDDEN + the request itself. Note what this is *not*: it is not the CPSL investigation evidence — that arrives later, under a different rule.
7. **"Eli's Record, in Your Hands" (`records_dep`)** — *Put the visit log and certificates in the June folder, in date order.* FLAG: `depFolder`; HIDDEN + the kept visit log and two certificates. June's preparation starts in February.
8. **"The Fee-Dependent Line" (`service_plan`)** — *Pay the $45 and keep the receipt in the June folder.* Cash −45 (230 → 185); FLAG: `classPaid`; HIDDEN + the paid final module. This is where the two tracks actually touch — through a wallet — and paying it keeps June's record free of an unexplained gap.
9. **"Thursday, Twice a Week" (`visit`)** — *Pay the week's fares and keep the visit streak unbroken.* Cash −18 (185 → 167); HIDDEN + the unbroken visit streak. The dependency record's most persuasive pages are other people's handwriting about your constancy.
10. **"What the Agency Has to Hand Over" (`evidence_packet`)** — *Build the hearing around what the packet actually says.* HIDDEN + the CPSL disclosure, including the pediatrician's line on page six. This evidence exists in your hands **only because** step 5 was taken.
11. **"Porch, Steps, Walk" (`divided`)** — *Print the photographs, three angles, dated, one caption each.* FLAG: `photos`; HIDDEN + the single-structure photographs. This converts "my account varied" into "two names for one structure" — the hearing's central weighing move.
12. **"Ounces" (`gather`)** — *Collect both letters, in person, this week.* Cash −12 (167 → 155); FLAG: `letters`; HIDDEN + the director's letter and the cousin's signed statement. Weight, in the literal sense the hearing will use.
13. **"Exchange" (`prehearing`)** — *Mail the packet, keep the receipt, and prepare to testify in order.* FLAG: `disclosed`. Exchanging early keeps the hearing about the evidence instead of about the mail, and routes you to the strong hearing (`hearing_strong`) rather than the thin one.
14. **"The Hearing, May 12" (`hearing_strong`) → "The Week Before June" (`review_prep_exp`) → "Monday, June 1 — Eli's Review" (`review_exp`) → "The Envelope, June 5" (`decision_exp`)** — No branching choices remain that can lose the win; the discipline here is thematic: keep the tracks separate in the review room, let the dependency judge read the dependency record, and let the CPSL decision arrive on its own clock (June 5 — 24 days after the hearing concluded).

**Cash on the winning route: 230 → 155.** Every dollar of the 75 spent buys a record item, not a service from the system: a class receipt, a visit streak, two letters.

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

Verified principles only, as the scenario uses them:

- **The written appeal, and its clock — 23 Pa.C.S. § 6341(a)(2).** A person named as a perpetrator in an indicated report may request, in writing, that it be amended or expunged, within 90 days of being notified. In this scenario Lena is notified Monday, February 2, 2026, so the deadline is **Sunday, May 3, 2026** (February 2 + 90 days, verified programmatically). Filing in February is what makes everything else in this guide possible; the right is real, and it is perishable.
- **The right to the investigation evidence — 23 Pa.C.S. § 6341(c.2)(4).** On appeal, the department or county agency must provide the appellant with all evidence gathered during the child abuse investigation that is relevant to the determination, **including potentially exculpatory evidence**. Page six — Ana's pediatrician's line, present in the agency's own file all along — is the scenario's illustration: the disclosure duty is not a courtesy, and in this scenario it is triggered by the appeal, which is why the never-filed ending never sees it used.
- **The agency's burden at the hearing — 23 Pa.C.S. § 6341(c.2)(5).** The department or county agency bears the burden of proving **by substantial evidence** that the report should remain categorized as an indicated report. The burden is never Lena's. Her packet does not have to prove January; it has to give the weighing something true to hold against the agency's side — photographs that answer "flat surface," a signed account of the fall, three documented years in a classroom.
- **Prompt decision — 23 Pa.C.S. § 6341(c.3).** The hearing decision is to be entered, filed, and served within 45 days of the hearing's conclusion. In this scenario the hearing concludes May 12, 2026 and the decision is entered June 5, 2026 — 24 days, within the window — which is also why the dependency review on June 1 properly happens *before* the CPSL outcome is known, and neither room waits for the other.
- **The separate dependency record — 55 Pa. Code § 3130.44(d).** The dependency case record "shall be released upon request." This is a **different record, under a different rule, for a different purpose** from the CPSL disclosure under § 6341(c.2)(4): § 3130.44(d) produces Eli's case record (service plan, visit log, class certificates); § 6341(c.2)(4) produces the investigation evidence about Ana. The scenario sets the `recordsRequested` flag only on the § 3130.44(d) request, deliberately, to keep that distinction mechanical rather than rhetorical.
- **Keeping the tracks distinct is itself the legal point.** A CPSL expunction hearing is an administrative proceeding about whether one report is accurate, decided on the substantial-evidence burden above. A dependency permanency review is a court proceeding about a child's plan and a parent's progress, decided on that case's own record. In this scenario the June 1 review credits Lena's visits, classes, and progress from the dependency record — in *both* the expunged and the upheld endings — because that is what the review is for. (For completeness: the upheld ending notes the further-review clocks of 23 Pa.C.S. § 6341(g) — reconsideration within 15 calendar days of the mailing date of the Bureau's final order, or an appeal to Commonwealth Court perfected within 30 calendar days of that mailing date. The winning route never needs them.)

One deliberate absence: the daycare's schedule pause is presented throughout as **that fictional employer's own stated process**, in its binder, in its director's words. The scenario asserts no employment-law right or consequence, and neither does this guide.

## 4. The traps

1. **The drawer (`start` → `drawer` → `quiet_wait`, or `counsel` → `wait_risk` → `quiet_wait` → `deadline_passes`).** The most tempting trap because it does not feel like a choice. Letting the letter sit carries the story past **Sunday, May 3, 2026**, after which the § 6341(a)(2) written-appeal right is gone — not denied, never exercised. Cost: the hearing, the § 6341(c.2)(4) disclosure, and the agency ever having to carry its § 6341(c.2)(5) burden; in-story, the daycare income ends and dependency progress slows through the unpaid module and missed fares, ending at `end_quiet`. The scenario is careful, and this guide repeats it: that ending is about documentation and regret, **not moral worth**.
2. **"Gather everything first" (`counsel` → `wait_risk`).** Perfectionism dressed as diligence. Filing in April still answers the clock — this trap does not close the appeal — but it closes the *win*: the shortened spring produces no photographs, no letters, and no time to exchange them, routing to `prehearing_thin` and `hearing_thin`, where one pediatrician's line is outweighed and the report is upheld (`end_upheld`). Cost: the expungement, on a record the player had the February to build.
3. **Skipping the § 3130.44(d) request (`appeal_filed` → `service_plan`, bypassing `records_dep`).** One file at a time feels manageable. Cost: June's review gets prepared from summaries instead of the actual visit log, certificates, and caseworker notes — and summaries are, in this scenario's repeated phrase, where nuance goes to be shortened. The flag forgone is small; the record blindness in June is not.
4. **Saving money at the record's expense (`service_plan` → let the module slip; `visit` → skip a visit; `divided` → testimony alone; `gather` → save the asking).** Each individual saving is rational — $45, $18, $12, a morning. Together they convert a strong hearing into a thin one and a legible June record into a gapped one. Cost: exactly the ounces the hearing weighs. In this scenario, cash kept is rarely cash saved; it is weight removed from your own side of a scale someone else will read.

## 5. What no strategy controls

This route maximizes what is Lena's to control — the filing date, the two record requests, the receipts, the photographs, the exchange, the testimony's order. It controls nothing else, and the scenario says so in every debrief. A different hearing officer could weigh the same two doctors differently; credibility and weight are human judgments, not mechanisms. A different dependency judge could read the same folder with a different sense of risk. The caseworker's warmth, the director's precision, the cousin's willingness to sign, the pediatrician having written her line down in the first place — all of that is other people, and luck, and none of it is purchasable with the $75 or earnable by the route. Parents in the published record this scenario is built from reached worse endings with strong files and better ones with thin files and fortunate rooms. The honest claim for this guide is the narrow one the scenario makes everywhere: strategy does not decide outcomes in this system. It decides what the record holds when the humans who do decide outcomes open the folder.

---

*Draft game documentation — fictional simulation, general information only, not legal advice. Companion files: `scenario-20.json`, `scenario-20-script.md`. Sources and alterations for the scenario's published-record basis are documented in the scenario research report accompanying this build.*