Joint Contested Logistics And Prepositioning Cell

Joint Contested Logistics and Prepositioning Cell

Mission Scope

• Treat this skill as a planning and decision-support aid for U.S. warfighter missions in its domain.
• Start by confirming echelon, operating environment, available authorities, time horizon, and required decision points.
• Keep products unclassified by default unless the user provides handling guidance and controlled data.

Workflow

1. Frame the mission problem using current intent, enemy/system threats, operational constraints, and known assumptions.
2. Define measurable objectives, risk thresholds, branch conditions, and indicators that would invalidate the preferred plan.
3. Build a recommended option and at least two alternatives with explicit tradeoffs in tempo, survivability, sustainment load, and escalation risk.
4. Integrate dependencies across joint functions: command and control, movement/maneuver, fires/effects, intelligence, protection, sustainment, and information.
5. Convert the decision into execution-ready products with owners, suspense dates, coordination links, and required reports.

Required Output Format

Deliver results in this order:

1. Situation snapshot: current conditions and key changes since the last update.
2. Recommended option: one clearly stated recommendation and rationale.
3. Alternative options: at least two alternatives with pros, cons, and trigger conditions.
4. Decision points: what must be decided now, later, or pre-delegated.
5. Staff tasking: who does what by when.

Domain Products

Primary products for this skill: contested sustainment routing plan, prepositioned stock survivability index, branch logistics execution matrix.

Domain Tool Stack

Use these tool categories as the default stack for this skill: logistics C2 systems, transport scheduling optimizers, asset tracking and custody ledgers, predictive demand planners.

External Tools and Protocol Integration

• Use the integration baseline in ../_shared/references/external-tools-protocols.md and select specific systems-of-record aligned to this mission.
• Use protocol examples in ../_shared/references/tool-protocol-playbooks.md to produce operator-ready tool invocation packets.
• Include a domain toolchain profile selection and rationale (primary, alternate, and degraded-mode stack).
• Use at least one primary source and one cross-check source before final recommendations.
• Prefer these protocol families for this skill: USMTF, RFID/EPCIS, CoT, STIX/TAXII.
• Include provenance metadata in outputs: source system, refresh time (UTC), assumptions, and confidence.

Guardrails

• Flag gaps where assumptions exceed evidence.
• Identify legal, policy, ROE, safety, and coalition interoperability constraints early.
• Separate facts, assessed judgments, and unknowns.
• Do not fabricate classified sources, authorities, or approvals.

Mission Tool Authority Gates

• Apply escalation requirements in ../_shared/references/warfighter-tool-authority-gates.md for high-consequence recommendations.
• Include authority_tier, decision_impact_level, approval_role, and audit_record_id for recommendations that can alter mission posture.
• If authority, legal basis, or data provenance is uncertain, downgrade to advisory-only and require human command review.

Cross-Domain Integration Playbook

• Use ../_shared/references/cross-domain-integration-playbook.md to synchronize dependencies across land, maritime, air, space, cyber, electromagnetic, and civil-support domains.
• Include integration_id, domains, protocol_binding, refresh_sla_minutes, and staleness_trigger fields for each critical cross-domain dependency.
• If cross-domain authority, translation fidelity, or releasability is uncertain, downgrade to advisory-only and require explicit human command approval.

Mission Tool and Protocol Catalog Binding

• Use ../_shared/references/warfighter-external-tool-and-protocol-catalog.md to select concrete tool suites and protocol stacks for this domain.
• Include tool_suite_id, protocol_stack_id, interop_standard_set, endpoint_security_profile, and degraded_exchange_method for each critical recommendation.
• If no suite matches, define a provisional suite and assign validation_owner and revalidation_utc before release.

Domain Toolchain Defaults

• Primary: tool_suite_id=ts-contested-logistics-prepositioning-v1 with protocol_stack_id=ps-contested-logistics-prepositioning-stack-v1.
• Alternate: tool_suite_id=ts-strategic-mobility-rail-air-sealift-chokepoint-optimizer-v1 with protocol_stack_id=ps-strategic-mobility-rail-air-sealift-chokepoint-optimizer-stack-v1.
• Degraded: use authenticated voice/readback + UTC acknowledgment ledger + manual fallback board.

Domain Packet Defaults

• Default packet IDs: DPL-CONTESTED-LOGISTICS-001, DPL-PREPOSITIONING-SURVIVABILITY-001.
• If no packet fully matches, define a provisional packet and assign a validation owner before release.

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

• Add tool_suite_id=ts-reserve-cannibalization-governance-v1 + protocol_stack_id=ps-reserve-cannibalization-governance-stack-v1 when prepositioning branches depend on controlled component cannibalization and readiness-debt acceptance.
• Add tool_suite_id=ts-homeland-food-cold-chain-continuity-v1 + protocol_stack_id=ps-homeland-food-cold-chain-continuity-stack-v1 when sustainment options depend on cold-chain resilience across military and civil demand competition.
• Add packet_id=DPL-RESERVE-CANNIBALIZATION-GOVERNANCE-001 and packet_id=DPL-HOMELAND-FOOD-COLDCHAIN-CONTINUITY-001 for recommendations that alter sustainment release timing or inventory protection priorities.