joint-contested-space-launch-window-reconstitution-cell

# Joint Contested Space Launch Window Reconstitution Cell ## Mission Scope - Treat this skill as planning and decision support for U.S. warfighter missions. - Confirm echelon, authorities, timeline, and decision owner before recommending options. - Keep outputs unclassified by default unless user-provided handling guidance changes that. ## Workflow 1. Frame the mission problem with domain constraints, available resources, and threat indicators. 2. Identify assumptions, risk thresholds, and invalidation triggers. 3. Build one recommended COA and at least two alternatives with explicit tradeoffs. 4. Bind each recommendation to concrete tools, protocols, data freshness, and authority gates. 5. Produce commander summary plus staff action tracker with owners and suspense. ## Required Output Format 1. Situation snapshot. 2. Recommended option. 3. Alternative options. 4. Decision points and branch triggers. 5. Staff tasking and suspense dates. ## Domain Products Primary products for this skill: launch window recovery matrix, payload reprioritization board, range and telemetry resilience timeline. ## U.S. Warfighter Employment Notes - Prioritize military mission assurance and strategic warning continuity when launch windows collapse under contested conditions. ## External Tools and Protocol Integration - Use `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` to select a concrete `tool_suite_id` and `protocol_stack_id`. - Include `interop_standard_set`, `endpoint_security_profile`, `primary_exchange_path`, and `degraded_exchange_method` for each critical recommendation. - Include one `packet_id` from `../_shared/references/domain-tool-packet-library.md` for each critical recommendation. - For this domain, prioritize `ts-contested-space-launch-reconstitution-v1` with `ps-contested-space-launch-reconstitution-stack-v1` and `DPL-CONTESTED-SPACE-LAUNCH-RECONSTITUTION-001`. ## Guardrails - Separate facts, assessments, and unknowns. - Flag legal, policy, ROE, safety, and coalition interoperability constraints early. - If authority or data provenance is uncertain, downgrade to advisory-only and require human command approval. ## Domain Toolchain Override (2026-03-11, Expansion Wave XIII Addendum) - Add `tool_suite_id=ts-coalition-denied-environment-digital-map-rights-and-provenance-cell-v1` + `protocol_stack_id=ps-coalition-denied-environment-digital-map-rights-and-provenance-cell-stack-v1` when launch-window branches depend on trusted geospatial inputs and coalition rights constraints. - Add `tool_suite_id=ts-joint-distributed-mission-brief-multilingual-assurance-cell-v1` + `protocol_stack_id=ps-joint-distributed-mission-brief-multilingual-assurance-cell-stack-v1` when launch coordination requires multilingual command-intent fidelity. - Add `packet_id=DPL-MAP-PROVENANCE-001` and `packet_id=DPL-MISSION-BRIEF-MULTI-001` for branches that alter launch authorization confidence or coalition release conditions.