| name | homeland-airport-mass-casualty-runway-defense-and-recovery-cell |
| description | Integrate airport defense, triage, and runway recovery under mass-casualty homeland attacks affecting military airlift. |
Homeland Airport Mass Casualty Runway Defense And Recovery Cell
Mission Scope
- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
- Confirm command echelon, authorities, coalition constraints, and commander decision deadlines before recommending action.
- Keep outputs unclassified by default unless explicit handling guidance is provided.
Workflow
- Frame the mission problem with threat picture, mission objectives, and operational constraints.
- Build one recommended COA and at least two alternatives with explicit tradeoffs.
- Identify branch/sequel triggers, degraded-mode transitions, and staff dependencies.
- Bind every critical recommendation to concrete external tools, protocol stacks, and packet templates.
- Publish commander decision prompts and a staff task tracker with owner, suspense, and revalidation trigger.
Required Output Format
- Situation snapshot and key changes.
- Recommended COA and rationale.
- Alternative COAs with trigger conditions.
- Decision points and escalation gates.
- Staff tasks by owner and suspense.
- Tool invocation packets with protocol bindings.
Domain Products
Primary products: airport defense triage matrix, runway recovery sequencing plan, airlift continuity board, and joint authority decision prompts.
Domain Toolchain Defaults
- Primary:
tool_suite_id=ts-homeland-airport-mass-casualty-runway-defense-v1 with protocol_stack_id=ps-homeland-airport-mass-casualty-runway-defense-stack-v1.
- Alternate: pick a mission-adjacent suite/stack from
../_shared/references/warfighter-external-tool-and-protocol-catalog.md and explain tradeoffs.
- Degraded: authenticated voice/readback plus UTC acknowledgment ledger and manual sync board.
Domain Packet Defaults
- Default packet IDs: DPL-HOMELAND-AIRPORT-MASCAL-RUNWAY-001, DPL-AIRLIFT-CONTINUITY-RECOVERY-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
- Use concrete tool suites and protocol stacks in
../_shared/references/warfighter-external-tool-and-protocol-catalog.md.
- Use packet templates in
../_shared/references/domain-tool-packet-library.md and protocol playbooks in ../_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/action template, expected output schema, protocol/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 authority, legal basis, or provenance 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 legal, ROE, LOAC, policy, and coalition caveat constraints before recommending action.
- Do not fabricate classified sources, authorities, or approvals.
