Autonomous Littoral Port Reopening Under Mining And Drone Threat Cell

Autonomous Littoral Port Reopening Under Mining and Drone Threat Cell

Mission Scope

• Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
• Confirm echelon, authorities, timeline, and mission decision points before generating recommendations.
• Keep outputs unclassified by default unless the user provides handling guidance.

Workflow

1. Build a mission snapshot with current status, threat posture, support constraints, and commander priorities.
2. Define branch options with explicit tradeoffs in survivability, tempo, sustainment burden, and escalation risk.
3. Select external toolchain configuration (primary, alternate, degraded) and state the protocol/message path.
4. Map each tool output to a commander decision point with confidence, assumptions, and validation gates.
5. Produce commander-facing recommendations plus staff actions with owners, suspense, and branch triggers.

Required Output Format

1. Situation snapshot.
2. Recommended branch and rationale.
3. Alternatives and trigger conditions.
4. Decision points and approval gates.
5. Staff tasking with suspense.

Domain Tool Stack

Use these tool categories by default: minefield mapping fusion, autonomous harbor reconnaissance control, and convoy risk re-sequencing planners.

Protocol Profile

Preferred protocol families for this skill: IHO S-100, AIS, Link 16 J-series, STANAG, API/JSON.

Domain Toolchain Defaults

• Primary: select a mission-fit tool_suite_id from ../_shared/references/warfighter-external-tool-and-protocol-catalog.md.
• Alternate: select a cross-check tool_suite_id with independent data provenance.
• Degraded: commander-approved manual branch board with UTC acknowledgment logging.

External Tools and Protocol Integration

• Use ../_shared/references/warfighter-external-tool-and-protocol-catalog.md to bind concrete tool suites and protocol stacks.
• Use ../_shared/references/domain-tool-packet-library.md and include packet_id=DPL-LITTORAL-PORT-REOPENING-001 for critical recommendations.
• Include tool_suite_id, protocol_stack_id, packet_id, data freshness (UTC), confidence, and fallback path in each high-impact branch.
• If no direct packet match exists, define a provisional packet with validation_owner and revalidation_utc.

Guardrails

• Separate facts, assessed judgments, assumptions, and unknowns.
• Flag legal/policy/ROE constraints and coalition interoperability limits early.
• Downgrade to advisory-only when authority, data provenance, or acknowledgment integrity is uncertain.
• Do not fabricate sources, approvals, or operational authorities.

Domain Toolchain Override (2026-03-12, Expansion Wave XVIII Addendum)

• Add tool_suite_id=ts-littoral-port-mining-drone-clearance-fusion-v1 + protocol_stack_id=ps-littoral-port-mining-drone-clearance-fusion-stack-v1 when port reopening depends on synchronized mine and drone threat suppression.
• Add tool_suite_id=ts-convoy-berth-priority-risk-arbitration-v1 + protocol_stack_id=ps-convoy-berth-priority-risk-arbitration-stack-v1 when branching requires balancing throughput, escort scarcity, and strike risk.
• Add packet_id=DPL-LITTORAL-PORT-REOPENING-001 and packet_id=DPL-CONVOY-BERTH-RISK-ARBITRATION-001 for recommendations that alter channel opening sequence or convoy release authority.