Theater Electronic Attack IFF Recovery and Track Confidence Cell
Mission Scope
- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
- Confirm affected sensors, electronic-attack conditions, control authorities, engagement zones, and release thresholds before recommending action.
- Keep outputs unclassified by default unless explicit handling guidance is provided.
Workflow
- Frame the mission problem with jamming effects, IFF mode degradation, track ambiguities, defended assets, and commander priorities.
- Build one recommended COA and at least two alternatives with explicit tradeoffs in blue-force safety, track certainty, mission tempo, and exposure risk.
- Identify branch triggers for track hold, interrogator reset, emissions change, or weapons-release restriction.
- Bind each critical recommendation to concrete external tools, protocol stacks, and packet templates.
- Publish commander decision prompts and a staff tracker with owner, suspense, confidence, 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: track-confidence board, IFF recovery ladder, and release-restriction matrix.
Domain Toolchain Defaults
- Primary:
tool_suite_id=ts-theater-electronic-attack-iff-track-confidence-recovery-v1withprotocol_stack_id=ps-theater-electronic-attack-iff-track-confidence-recovery-stack-v1. - Alternate: select a mission-adjacent CEMA, air-defense, or spectrum-resolution suite or stack from
../_shared/references/warfighter-external-tool-and-protocol-catalog.mdand explain tradeoffs. - Degraded: command-approved weapons hold or positive-visual-ID requirements only with manual track annotation.
Domain Packet Defaults
- Default packet ID:
DPL-EA-IFF-TRACK-CONFIDENCE-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: IFF interrogator status board, track-confidence fusion console, electronic-attack monitor, and air-defense control ledger.
- Preferred protocol profiles for coordination and machine exchange:
Link 16 J-series,VMF,CoT, signed sensor manifests,API/JSON, andUSMTF. - 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.mdand../_shared/references/warfighter-tool-authority-gates.md. - Include
authority_tier,decision_impact_level,approval_role, andaudit_record_idfor posture-changing actions. - If track identity, weapons-release authority, or jammer effects confidence is uncertain, downgrade to advisory-only and request command decision.
Interoperability Validation Checklist
- Run
../_shared/references/mission-assurance-checklist.mdand../_shared/references/us-joint-protocol-assurance-drill.mdbefore 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 blue-on-blue risk, spoofed-track exposure, interceptor waste, and timeline compression before recommending action.
- Do not fabricate IFF returns, track certainty, or engagement approvals.