Strategic Commercial Port Crane Firmware Rollback And Sealift Recovery Cell
Mission Scope
- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
- Confirm port authority roles, military cargo priorities, OT safety thresholds, and decision deadlines before recommending action.
- Keep outputs unclassified by default unless explicit handling guidance is provided.
Workflow
- Frame the mission problem with crane OT status, berth backlog, cargo priority, and sealift schedule pressure.
- Build one recommended COA and at least two alternatives with explicit tradeoffs in throughput, safety, cyber containment, and force-flow disruption.
- Identify branch/sequel triggers, rollback thresholds, and command approval gates.
- 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: crane rollback decision board, berth-priority ladder, and sealift recovery packet.
Domain Toolchain Defaults
- Primary:
tool_suite_id=ts-strategic-commercial-port-crane-firmware-rollback-sealift-recovery-v1withprotocol_stack_id=ps-strategic-commercial-port-crane-firmware-rollback-sealift-recovery-stack-v1. - Alternate: select a mission-adjacent sealift, port-recovery, or OT-restoration suite/stack from
../_shared/references/warfighter-external-tool-and-protocol-catalog.mdand explain tradeoffs. - Degraded: manual crane safety board with phased berth release worksheet and UTC berth-acknowledgment logging.
Domain Packet Defaults
- Default packet ID:
DPL-STRATEGIC-PORT-CRANE-FIRMWARE-ROLLBACK-SEALIFT-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: crane OT telemetry board, firmware rollback workflow, pier throughput planner, and sealift berth-priority tracker.
- Preferred protocol profiles for coordination and machine exchange:
STIX/TAXII,AIS/NMEA,NIMS/ICS,USMTF, andAPI/JSON. - 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/action template, expected output schema, protocol/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 authority, legal basis, OT safety evidence, or cargo-priority provenance 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 port authority boundaries, worker safety, hazardous cargo handling, and OT rollback hazards before recommending action.
- Do not fabricate classified sources, authorities, or approvals.