Sample survivor case file

What a Component B case looks like

This is an illustrative example — not a real case — of how a survivor moves through Project Exodus from rescue through reunification. Cases are referenced by pseudonymous IDs across the platform; identifying information sits in a segregated schema with separate access controls.

Case · EXO-2026-XXXXXX · Phoenix-ZPhase: Reunification

Phase 1. Rescue

done

2026-02-12

Recovered jointly with state task force after a CCSA hotspot alert clustered 3 independent reports at a Nashville-area truck stop. Advocate met the child at emergency-medical intake within 2 hours.

Phase 2. 72-hour protocol

done

2026-02-12 → 02-15

Medical, physical, emotional, and forensic (SANE) triage at Memorial Children's. Recommended level of care: L3 (Intense) based on trauma indicators. Spanish-language preference recorded.

Phase 3. Short-term stabilization (90 days)

done

2026-02-15 → 05-15

Treatment team assigned: case manager, therapist, education specialist. Trauma-focused individual + group counseling. ESL track for school re-entry. Mentor pairing with Maria S. (paid adult-survivor consultant) initiated with consent on day 30.

Phase 4. Reunification

active

2026-05-08 (in progress)

Family assessment completed by case manager. Aunt approved as primary caregiver. DNA verification complete (confirmed match). All household adults cleared via background check. Personalized reunification plan signed off — supervised contact protocol with biological father, restraining order in place.

Approval workflow gates the move on family-assessment-approved + DNA-confirmed + all household-adults-cleared + personalized plan present. Blocked attempts are audited.

Phase 5. Post-placement monitoring (12 months)

upcoming

2026-05-15 → 2027-05-15

12 monthly touchpoints scheduled. Each touchpoint can raise a flag if the survivor reports contact attempts or feels unsafe — flag-raised auto-creates a CrisisEvent and pages the case manager + on-call rotation.

Cross-cutting (Component D) layers active throughout

Sibling/family search: when this case opened, search-and-surface flagged Phoenix-Y at 40% confidence via shared language + similar age + shared pseudonym prefix; awaiting analyst review.
Missing-children DB: initial cross-check produced a 55% match against MCDB-2025-019901; reviewed and confirmed.
Mentor re-exploitation prevention: Maria S. active 60+ days; consent timestamp recorded; survivor magic link issued so the survivor can press the panic button at any time and reach the assigned case manager directly.
Audit chain: every transition above is a hash-chained entry in the platform-wide audit log.

Survivors with a magic link see a calmer version of this same information at /survivor: first-name-only team, gentle phase labels (“Coming home” instead of “Reunification”), upcoming touchpoints in plain dates, and the panic button persistently available.