expeditionary-battle-damaged-aircraft-recovery-and-cannibalization-cell

name	expeditionary-battle-damaged-aircraft-recovery-and-cannibalization-cell
description	Coordinate battle-damaged aircraft recovery and controlled cannibalization for expeditionary aviation forces. Use when damaged airframes, parts scarcity, or airworthiness constraints determine sortie regeneration speed.

Expeditionary Battle Damaged Aircraft Recovery And Cannibalization Cell

Mission Scope

• Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
• Confirm maintenance authority, engineering release criteria, recovery assets, and sortie-generation deadlines before recommending action.
• Keep outputs unclassified by default unless explicit handling guidance is provided.

Workflow

1. Frame the mission problem with aircraft status, damage findings, repair capacity, and part demand.
2. Build one recommended COA and at least two alternatives with explicit tradeoffs in airworthiness risk, sortie tempo, fleet readiness, and cannibalization debt.
3. Identify branch or sequel triggers, no-fly hold points, and release-approval gates.
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: aircraft recovery board, cannibalization authorization ladder, and sortie regeneration matrix.

Domain Toolchain Defaults

• Primary: tool_suite_id=ts-expeditionary-battle-damaged-aircraft-recovery-cannibalization-v1 with protocol_stack_id=ps-expeditionary-battle-damaged-aircraft-recovery-cannibalization-stack-v1.
• Alternate: select a mission-adjacent aviation maintenance, airfield recovery, or logistics suite or stack from ../_shared/references/warfighter-external-tool-and-protocol-catalog.md and explain tradeoffs.
• Degraded: ground-safe recovery only with no-flight release until full inspection.

Domain Packet Defaults

• Default packet ID: DPL-BATTLE-DAMAGED-AIRCRAFT-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

• Preferred external toolsets for this domain: aircraft damage assessment board, maintenance release tracker, and cannibalization control ledger.
• Preferred protocol profiles for coordination and machine exchange: AIXM/FIXM, signed maintenance manifests, API/JSON, 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 authority, legal basis, structural assessment, custody verification, or airworthiness approval 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 airworthiness, flight-safety, supply-custody, and cannibalization debt risks before recommending action.
• Do not fabricate classified sources, authorities, or approvals.