Which AI agents work with Strategic Military Cloud Sovereignty Break Glass Continuity Cell?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Strategic Military Cloud Sovereignty Break Glass Continuity Cell by zwright8

Name: Strategic Military Cloud Sovereignty Break Glass Continuity Cell
Rating: 4.2 (5 reviews)
Author: zwright8

Strategic Military Cloud Sovereignty Break Glass Continuity Cell

Execute sovereignty-preserving break-glass continuity for military cloud environments during legal, cyber, or provider-failure crises. Use when mission data and command workloads need emergency migration or controlled isolation.

zwright8 408ee50 2 files · 3.5 KB Updated Sep 10, 2026

File contents

Strategic Military Cloud Sovereignty Break-Glass Continuity 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

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

Required Output Format

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

Domain Products

Primary products: cloud sovereignty break-glass matrix, data custody continuity ladder, strategic command workload migration brief.

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-strategic-military-cloud-break-glass-continuity-v1 with protocol_stack_id=ps-strategic-military-cloud-break-glass-continuity-stack-v1.
Alternate: tool_suite_id=ts-strategic-military-cloud-break-glass-continuity-v1 with protocol_stack_id=ps-strategic-military-cloud-break-glass-continuity-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-STRATEGIC-MILITARY-CLOUD-BREAK-GLASS-CONTINUITY-001, DPL-STRATEGIC-MILITARY-CLOUD-BREAK-GLASS-CONTINUITY-001.
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.

---name: strategic-military-cloud-sovereignty-break-glass-continuity-description: Execute sovereignty-preserving break-glass continuity for military cloud environments during legal, cyber, or provider-failure crises. Use when mission data and command workloads need emergency migration or controlled isolation.---# Strategic Military Cloud Sovereignty Break-Glass Continuity 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.## Workflow1. 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 Format1. 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 ProductsPrimary products: cloud sovereignty break-glass matrix, data custody continuity ladder, strategic command workload migration brief.## 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-strategic-military-cloud-break-glass-continuity-v1` with `protocol_stack_id=ps-strategic-military-cloud-break-glass-continuity-stack-v1`.- Alternate: `tool_suite_id=ts-strategic-military-cloud-break-glass-continuity-v1` with `protocol_stack_id=ps-strategic-military-cloud-break-glass-continuity-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-STRATEGIC-MILITARY-CLOUD-BREAK-GLASS-CONTINUITY-001, DPL-STRATEGIC-MILITARY-CLOUD-BREAK-GLASS-CONTINUITY-001.- 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.

Frequently asked questions