Homeland Port War Risk Insurance And Claims Cell

Homeland Port War Risk Insurance And Claims Cell

Mission Scope

• Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
• Confirm port authority, insurer posture, cargo priorities, and federal or military support thresholds before recommending action.
• Keep outputs unclassified by default unless explicit handling guidance is provided.

Workflow

1. Frame the mission problem with port incident status, berth demand, insurer posture, claims exposure, and commander priorities.
2. Build one recommended COA and at least two alternatives with explicit tradeoffs in throughput, financial confidence, legal friction, and recovery speed.
3. Identify branch triggers for closure, provisional coverage, claims routing, federal support, or prioritized berth release.
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: war-risk trigger board, claims routing ladder, and port recovery finance matrix.

Domain Toolchain Defaults

• Primary: tool_suite_id=ts-homeland-port-war-risk-insurance-claims-v1 with protocol_stack_id=ps-homeland-port-war-risk-insurance-claims-stack-v1.
• Alternate: select a mission-adjacent strategic mobility, port-operations, or legal-claims suite or stack from ../_shared/references/warfighter-external-tool-and-protocol-catalog.md and explain tradeoffs.
• Degraded: military-essential cargo only with provisional claims tracking and command-approved berth prioritization.

Domain Packet Defaults

• Default packet ID: DPL-PORT-WAR-RISK-CLAIMS-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: port operations dashboard, marine insurer status board, and claims adjudication tracker.
• Preferred protocol profiles for coordination and machine exchange: AIS/NMEA, NIEM, signed claims manifests, API/JSON, S/MIME, 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 incident verification, insurer posture, or port-release authority 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 insurer withdrawal risk, legal-claims backlog, berth-freeze consequences, and sealift timing impacts before recommending action.
• Do not fabricate incident status, insurer commitments, or claims authorities.