Joint Expeditionary Advanced Base Operations And Signature Management Cell

Joint Expeditionary Advanced Base Operations And Signature Management Cell

Mission Scope

• Treat this skill as planning and decision support for U.S. warfighter expeditionary advanced base employment in contested littoral and distributed environments.
• Confirm command intent, basing authorities, displacement criteria, sustainment burn rate, and signature constraints before recommending action.
• Keep outputs unclassified by default and avoid exposing precise sensitive locations unless the user provides explicit handling guidance.

Workflow

1. Frame the basing problem using mission purpose, threat windows, mobility constraints, sustainment posture, and signature budget.
2. Build one recommended COA and at least two alternatives with explicit tradeoffs in survivability, persistence, tempo, and resupply burden.
3. Identify branch triggers for displacement, emission control shifts, resupply delay, host-nation friction, and deception failure.
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: EAB posture matrix, signature budget ladder, and displacement trigger board.

Domain Toolchain Defaults

• Primary: tool_suite_id=ts-joint-expeditionary-advanced-base-signature-management-v1 with protocol_stack_id=ps-joint-expeditionary-advanced-base-signature-management-stack-v1.
• Alternate: select a mission-adjacent littoral, force-protection, or sustainment suite or stack from ../_shared/references/warfighter-external-tool-and-protocol-catalog.md and explain tradeoffs.
• Degraded: hold-position or displace-only advisory with manual signature checks and reduced update cadence.

Domain Packet Defaults

• Default packet ID: DPL-EABO-SIGNATURE-MANAGEMENT-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: littoral COP, expeditionary engineering board, and signature-budget scheduler.
• Preferred protocol profiles for coordination and machine exchange: signed emissions-control manifests, CoT, VMF, Link 16 J-series, OGC, USMTF, and API/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 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 location sensitivity, displacement authority, or sustainment feasibility is uncertain, downgrade to advisory-only and request human command review.

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 signature overrun, sustainment shortfall, and displacement latency before recommending action.
• Do not fabricate authorities, host-nation permissions, or survivability claims.
• Do not generate weapon-employment sequences, precise evasion routes, or classified basing coordinates.