# Strategy Guide — Scenario 102: "The Deployment Calendar"

*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: "The Deployment Calendar."**

State it honestly: this is a **partial** win, and it is the best this scenario offers, labeled partial in the scenario itself. Juniper spends the entire case with her kin caregiver, Henrietta, and never a night in stranger care. Marlene is recovering and re-entering Juniper's daily care on documented medical steps. Jerome's return date is written into the family plan as a case event, with a reunification step dated to it. And the case is **still open at his return** — reunification steps in a plan still have to be lived and reviewed, and Marlene's recovery runs on a medical timeline no filing can hurry. The win is that the deployment calendar and the case calendar finally describe the same family. There is no ending in this scenario where the case closes during the deployment. 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. **The Arrangement, Signed or Spoken** — *Sign the family care arrangement and file it with the agency, in writing, naming Henrietta as kin caregiver.* Cash −20. Sets **kinArrangementWritten** — the single most important flag in the scenario. Juniper's care is a document from day two, not a recollection of a midnight kitchen.
2. **The Address on the Envelope** — *Correct the mailing address in writing to Henrietta's, with return receipt, and note both parents' contact routes.* Cash −10. Sets **addressCorrected**. Every future letter now goes where a person opens envelopes, instead of to the empty Hollis house.
3. **Shelter Care: A Voice on the Record** — *Ask the court to note Marlene's recovery plan and your return date in the order itself.* Sets **returnInOrder**. Dates in an order are case events; dates in a conversation are weather.
4. **School, From a New Bus Stop** — *Ask Henrietta to keep the log of your calls, Marlene's calls, and every agency visit.* Sets **familyLog**. Pencil, refrigerator, dated — the document that later answers the participation question page by page.
5. **Call Windows, in Writing** — *File the call-window notice and keep participating on that documented rhythm.* Sets **callWindowsFiled**. A file that knows when a deployed father can be reached scores silence differently from a file that never knew.
6. **Discharge Planning, on Speakerphone** — *File the discharge packet into the written plan — therapy, dates, graduated care at Henrietta's.* Sets **reentryWritten**. Marlene re-enters the plan as steps with medical dates, not as the passive phrase "mother recovering, return anticipated."
7. **The Request That Reads the File** — *File the written request for the complete agency record.* Cash −15. Sets **recordsRequested**. This is the highest-leverage move in the scenario: it is what exposes the "no response received" entries — letters mailed to a vacated address — while they can still be corrected before the review that would quote them.
8. **Correcting the Record, in Writing** — *File the written correction with the log, receipts, and return date attached, before the review.* Cash −10. Sets **correctionFiled**. The correction joins the record it corrects; future readers meet the error and its answer on facing pages.
9. **The Review: One Table, Two Calendars** — *The plan is written on both calendars — kinship throughout, your return date a dated reunification step.* This choice is flag-gated: it is only available with **kinArrangementWritten** + **recordsRequested** + **correctionFiled** all set. It leads to **The Deployment Calendar**.

Supporting route choices that cost nothing and keep the folder honest: starting Henrietta's kin assessment on day one at **Ms. Thornbury's First Call**, arranging Jerome's phone participation in advance and in writing at **How a Deployed Parent Appears**, and assembling the single review folder at **One Folder for the Review**.

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

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

- **The placement was heard promptly, with counsel.** Juniper's shelter care hearing fell inside the 72-hour window the law sets after a child is placed in shelter care (42 Pa.C.S. § 6332; 23 Pa.C.S. § 6315(d)), and the family's right to counsel — and to appointed counsel if it could not afford one — was part of the process from the start (42 Pa.C.S. § 6337; § 6332(a)).
- **Kinship is a documented status before it is a recognized one.** Henrietta was identified, assessed, and filed as Juniper's kin caregiver from the first days, within the kinship framework the verified set carries — the kinship definitions at 23 Pa.C.S. § 6302 and the notice provisions at 42 Pa.C.S. § 6336.1 (Act 48 of 2023). The written arrangement, not the family's genuine agreement, is what the shelter care court and every later review could act on.
- **Reviews act on the record before them.** The review proceeded under 42 Pa.C.S. § 6351 — placement, progress, and the plan's next steps, on the record. A return date becomes a reunification step only when it is proposed in documented form; "upon father's return, agency to assess" is what a plan says when it isn't.
- **Agency records are obtainable on request** — 55 Pa. Code § 3130.44(d) ("shall be released upon request"). Step 7 is that right exercised in writing, and it is what converts "non-cooperation" from a character judgment back into what it was: a mailing address.
- **A note on scope, stated honestly:** military-specific legal protections for deployed service members exist in the wider law, but they are **outside this scenario's verified set, are not cited anywhere in play, and this route does not rely on them.** Every winning move here is a generic, documented move available to any family — a written kin arrangement, a corrected address, a kept log, a requested record, a filed correction. The guide claims nothing more for them than that.

## (4) The traps

1. **Keeping the family care arrangement spoken** at "The Arrangement, Signed or Spoken," because everyone in the kitchen already agrees. Cost: no **kinArrangementWritten**. The file records "arrangement verbal, paperwork pending," and when a supervisor later needs a *documented* placement on a deadline, the documented placement available is stranger foster care — the "Unsigned Week" ending, in which Henrietta's eventual, perfect paperwork approves her into a case that has already hardened around a different address.
2. **Mentioning the empty house by phone** at "The Address on the Envelope," because Ms. Thornbury knows it is empty. Cost: no **addressCorrected**. Knowledge held by a person and knowledge held by a mailing system are different departments; the letters keep going to the locked box, and each one is logged by its silence.
3. **Asking for a phone summary of the file** at "The Request That Reads the File," instead of the written record request. Cost: no **recordsRequested**, no packet, nothing correctable line by line — participation stays "a concern the agency is monitoring," and the review inherits a "no response" narrative built entirely from unanswered mail to a house with nobody in it. That is the "No Response" ending, and no one in it ever refused a letter.
4. **Saving the correction to be delivered aloud at the review** at "Correcting the Record, in Writing." Cost: no **correctionFiled**. The kinship holds — Juniper stays with Henrietta, in her school, undisrupted — but the plan that leaves the room describes reunification as "when father returns," with no date and no step: the "Kinship, Without a Date" ending. The correction was true, and rehearsed, and nowhere the next worker will ever find it.

## (5) What no strategy controls

Marlene's medical timeline — therapy milestones, a surgeon's judgment, a setback no filing can prevent. A supervisor's deadline landing in the family's unsigned week. The appellate luck of which worker inherits the file, which judge reads it the night before, and whether a given month's mail routes true. Jerome's deployment itself: its windows, its duties, and its return date are set by an institution that has never read the family plan and is not required to care. The route above does not control any of that — it only guarantees that the family's actual life (a child cared for within the hour, a mother healing on schedule, a father answering every window he was given) exists in the one medium the case is conducted in. Outcomes in this system turn on workers, judges, resources, and luck as much as on any family's choices. The strategy's whole claim is narrower: the parts that *were* theirs — an arrangement, an address, a log, a request, a correction — were done in writing, with receipts, before the rooms where they would be needed.

---
*Verification: this route was walked programmatically against `scenario-102.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; the walk terminates at the ending node titled "The Deployment Calendar" after visiting 29 nodes, with $125 of the $180 starting cash remaining.*