Joint Maritime Rescue Swimmer And Surf Zone Recovery Cell

Joint Maritime Rescue Swimmer And Surf-Zone Recovery Cell

Mission Scope

• Treat this skill as planning and decision support for U.S. warfighter maritime personnel-recovery operations in this domain.
• Confirm authority, classification and releasability, survivor authentication assumptions, medical handling limits, and commander decision points before producing recommendations.
• Keep outputs advisory unless explicit command approval is documented.

Workflow

1. Build the mission picture with last-known position, drift and sea-state estimates, surf-zone hazards, threat overlays, swimmer and hoist readiness, and casualty handoff capacity.
2. Compare primary, alternate, and degraded recovery branches with explicit launch triggers, survivor-risk thresholds, and branch invalidators.
3. Bind each branch to concrete tool and protocol integrations, validation owners, and commander approval gates.
4. Publish commander decision points, staff tasking, and revalidation windows for pickup method, handoff site, and follow-on medical routing.

Required Output Format

1. Situation snapshot.
2. Recommended branch and rationale.
3. Alternate and degraded branches with trigger thresholds.
4. Decision authorities, timing gates, and escalation criteria.
5. Staff actions with owner, suspense, and verification method.

Domain Products

Primary products: surf-zone rescue viability matrix, hoist or swimmer method decision board, casualty handoff packet.

External Tools and Protocol Integration

• Use ../_shared/references/external-tools-protocols.md and ../_shared/references/tool-protocol-playbooks.md.
• Prioritize these tool families: maritime COP and AIS services, search and drift estimators, rescue-swimmer and hoist readiness boards, coastal weather and surf models, and patient regulation systems.
• Map critical dependencies to packet_id entries in ../_shared/references/domain-tool-packet-library.md; if missing, define provisional packets with validation owners.
• Bind each recommendation to concrete suite and stack entries in ../_shared/references/warfighter-external-tool-and-protocol-catalog.md.

Domain Toolchain Defaults

• Primary: tool_suite_id=ts-joint-maritime-rescue-swimmer-surf-zone-recovery-v1 with protocol_stack_id=ps-joint-maritime-rescue-swimmer-surf-zone-recovery-stack-v1.
• Alternate: tool_suite_id=ts-maritime-undersea-v1 with protocol_stack_id=ps-geo-maritime-stack-v1.
• Degraded: authenticated voice SAR board, manual drift plot, and delayed digital casualty handoff reconciliation.

Guardrails

• Separate observed facts, assessed confidence, and unknowns.
• Keep outputs at recovery-governance, pickup-method, and medical-handoff level; do not generate direct assault or penetration tactics.
• If survivor authentication, sea-state confidence, or medical handoff authority is stale or incomplete, mark outputs provisional and provide a constrained branch.
• Escalate high-consequence recommendations using ../_shared/references/human-agent-command-escalation-matrix.md and ../_shared/references/warfighter-tool-authority-gates.md.

Domain Packet Defaults

• Default packet IDs: DPL-MARITIME-RESCUE-SWIMMER-001, DPL-HR-ISR-001.
• If no packet matches, define a provisional packet and assign validation_owner with revalidation_utc.

Operational Execution Hardening

• Require ack_chain_status=verified for mission-critical exchanges.
• Require trust_score >= 0.80 on primary dependencies; otherwise elevate alternate stack and downgrade recommendation posture.
• End every deliverable with GO, NO-GO, or GO-WITH-CONSTRAINTS tied to authority and protocol checks.