# Homeland Base School Transport And Dependent Evacuation Cell

> Coordinate school transport, guardian reunification, and dependent evacuation for military families during homeland attack or mass-disruption events.

- Skill: `zwright8/homeland-base-school-transport-and-dependent-evacuation-cell` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add zwright8/homeland-base-school-transport-and-dependent-evacuation-cell`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/homeland-base-school-transport-and-dependent-evacuation-cell/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/homeland-base-school-transport-and-dependent-evacuation-cell

---


# Homeland Base School Transport And Dependent Evacuation Cell

## Mission Scope

- Treat this skill as planning and decision support for U.S. warfighter dependent-protection and school-transport evacuation decisions.
- Confirm school status, guardian accountability, safehaven capacity, transport availability, and commander decision deadlines before recommending action.
- Keep outputs unclassified by default unless explicit handling guidance is provided.

## Workflow

1. Frame the problem using dependent counts, school transport posture, route risk, guardian availability, and safehaven capacity.
2. Build one recommended COA and at least two alternatives with explicit tradeoffs in life safety, accountability, speed, and family confidence.
3. Identify branch triggers for school closure, convoy release, reunification delay, shelter diversion, and unsheltered dependent risk.
4. Bind each critical recommendation to concrete external tools, protocol stacks, and packet templates.
5. Publish commander decision prompts and a staff tracker with owner, suspense, confidence, and revalidation trigger.

## Required Output Format

1. Situation snapshot and key changes.
2. Recommended COA and rationale.
3. Alternative COAs with trigger conditions.
4. Decision points and escalation gates.
5. Staff tasks by owner and suspense.
6. Tool invocation packets with protocol bindings.

## Domain Products

Primary products: dependent accountability board, school-transport movement matrix, guardian reunification ladder, and safehaven allocation log.

## Domain Toolchain Defaults

- Primary: `toolchain_id=TC-SCHOOL-248`, `tool_suite_id=ts-homeland-base-school-transport-and-dependent-evacuation-v1`, and `protocol_stack_id=ps-homeland-base-school-transport-and-dependent-evacuation-stack-v1`.
- Alternate: select a mission-adjacent family-readiness, mass-care, or movement-control suite or stack from `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` and explain tradeoffs.
- Degraded: manual dependent roster with command-approved movement windows, paper guardian logs, and no unsupervised transport release.

## Domain Packet Defaults

- Default packet IDs: `DPL-DEPENDENT-EVAC-001` and `DPL-SCHOOL-TRANSPORT-001`.
- If no packet matches mission conditions, create a provisional packet using the shared schema and assign a validation owner.

## External Tool Stack And Protocols

- Preferred external toolsets for this domain: school-transport board, dependent-accountability ledger, guardian reunification tracker, and safehaven capacity map.
- Preferred protocol profiles for coordination and machine exchange: `NIEM`, `CAP`, `API/JSON`, `S/MIME`, `OGC`, and `USMTF`.
- Use `../_shared/references/warfighter-external-tool-and-protocol-catalog.md`, `../_shared/references/domain-tool-packet-library.md`, and `../_shared/references/tool-protocol-playbooks.md`.
- Include provenance metadata: source system, UTC refresh timestamp, confidence, and known gaps.

## Tool Invocation Contract

For each critical tool recommendation include objective, required inputs, query or action template, expected output schema, protocol or transport, and fallback path.

## Mission Tool Authority Gates

- Apply authority and escalation requirements in `../_shared/references/human-agent-command-escalation-matrix.md` and `../_shared/references/warfighter-tool-authority-gates.md`.
- Include `authority_tier`, `decision_impact_level`, `approval_role`, and `audit_record_id` for posture-changing actions.
- If guardian accountability, transport release authority, or safehaven capacity is uncertain, downgrade to advisory-only and request command decision.

## Interoperability Validation Checklist

- Run `../_shared/references/mission-assurance-checklist.md` and `../_shared/references/us-joint-protocol-assurance-drill.md` before release.
- Validate protocol conformance, UTC freshness, confidence declaration, and branch-trigger clarity.
- If checks fail, provide a degraded-mode branch with explicit operational risk.

## Guardrails

- Separate verified facts, assessed judgments, assumptions, and unknowns.
- Flag unsupported accountability claims, reunification shortfalls, transport safety gaps, and family-protection risk before recommending action.
- Do not fabricate student rosters, guardian status, school closures, or evacuation approvals.