Theater Multi Corps Water Bridging And Bulk Fuel Crossing Cell

Theater Multi-Corps Water Bridging and Bulk Fuel Crossing Cell

Mission Scope

• Treat this skill as planning and decision support for U.S. warfighter operations in this domain.
• Confirm authority, classification/releasability, coalition sharing limits, and required commander decisions.
• Keep outputs advisory unless explicit command approval is documented.

Workflow

1. Build the mission picture with threat indicators, critical dependencies, and timing constraints.
2. Compare primary, alternate, and degraded branches with explicit triggers and uncertainty notes.
3. Bind each branch to concrete tool/protocol integrations and validation owners.
4. Publish commander decision points, staff tasking, and revalidation windows.

Required Output Format

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

Domain Products

Primary products: crossing fuel synchronization matrix, bridge survivability branch plan, corps throughput timeline.

External Tools and Protocol Integration

• Use ../_shared/references/external-tools-protocols.md and ../_shared/references/tool-protocol-playbooks.md.
• 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/stack entries in ../_shared/references/warfighter-external-tool-and-protocol-catalog.md.

Domain Toolchain Defaults

• Primary: tool_suite_id=ts-water-bridging-fuel-crossing-v1 with protocol_stack_id=ps-water-bridging-fuel-crossing-stack-v1.
• Alternate: tool_suite_id=ts-logistics-distribution-v1 with protocol_stack_id=ps-rail-bridge-recovery-stack-v1.
• Degraded: authenticated voice/text branch with UTC event logs, cross-check witness, and delayed machine reconciliation.

Guardrails

• Separate observed facts, assessed confidence, and unknowns.
• If tool trust, authority, or data freshness is below threshold, 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-LOGISTICS-CONTINUITY-001, DPL-PORT-SAFETY-001, DPL-C2-DISP-002.
• 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.

Domain Toolchain Override (2026-03-15, Expansion Wave LVIII Addendum)

• Add tool_suite_id=ts-expeditionary-ribbon-bridge-maintenance-raft-launch-v1 + protocol_stack_id=ps-expeditionary-ribbon-bridge-maintenance-raft-launch-stack-v1 when crossing viability depends on bridge-bay serviceability, raft-launch cadence, or anchorage integrity under sustained load.
• Add tool_suite_id=ts-joint-bridge-erection-boat-gap-crossing-recovery-v1 + protocol_stack_id=ps-joint-bridge-erection-boat-gap-crossing-recovery-stack-v1 when bridge emplacement depends on bridge-erection-boat propulsion recovery, tow posture, or gap-crossing rescue readiness.
• Add packet_id=DPL-RIBBON-BRIDGE-RAFT-LAUNCH-001 and packet_id=DPL-BRIDGE-ERECTION-BOAT-RECOVERY-001 for branches that materially alter bridge uptime, raft throughput, or engineer recovery confidence.