# Tactical Cloud Edge Compute Orchestrator

> Support U.S. warfighter planning and decision support for Tactical Cloud Edge Compute Orchestrator. Use when missions require edge compute placement and disconnected operations orchestration, integrated options, and protocol-aware staff outputs.

- Skill: `zwright8/tactical-cloud-edge-compute-orchestrator` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add zwright8/tactical-cloud-edge-compute-orchestrator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/tactical-cloud-edge-compute-orchestrator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/tactical-cloud-edge-compute-orchestrator

---


# Tactical Cloud Edge Compute Orchestrator

## 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: edge node placement plan, data replication policy, disconnected-operations runbook.

## U.S. Warfighter Employment Notes

- Prioritize continuity for U.S. joint kill-web and mission-partner data paths before non-critical analytics traffic.
- Include explicit disconnected and low-bandwidth operating profiles for expeditionary and maritime edge nodes.
- Require rollback-ready deployment branches with signed baselines for each recommended edge-compute change.

## Domain Tool Stack

Use these tool categories as the default stack for this skill: edge cluster orchestrators, mission data fabrics, container registries, telemetry observability stacks.

## 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: REST/gRPC APIs, Kafka/AMQP, OGC feature services.
- Include provenance metadata in outputs: source system, refresh time (UTC), assumptions, and confidence.

## Interoperability Validation Checklist

- Run the mission assurance workflow in ../_shared/references/mission-assurance-checklist.md before final release.
- Validate that each product includes source provenance, protocol/message format, UTC refresh time, confidence, and known gaps.
- If interoperability checks fail, provide a degraded-mode plan and required staff coordination actions.

## Tool Invocation Contract

- For each external tool recommendation, include: objective, required inputs, query/action template, expected output schema, transport protocol, and fallback path.
- Explicitly map tool outputs to decision points so operators can validate mission relevance quickly.
- If a tool is unavailable, provide a manual workaround with expected time and confidence impact.

## 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.

## Tool Protocol Playbooks

- Use protocol examples in ../_shared/references/tool-protocol-playbooks.md to produce operator-ready tool invocation packets.
- Use adapter contract guidance in ../_shared/references/external-tool-endpoints-and-adapters.md to define endpoint schemas, transport, and fallback behavior.
- Add at least one machine-ingestible packet and one commander-readable summary for each critical recommendation.

## Domain Tool Packet Library

- Use scenario packets in ../_shared/references/domain-tool-packet-library.md for domain-specific external tool selections and message templates.
- Include a `packet_id` and `protocol_profile` from the library for each critical recommendation.
- If no packet matches, define a provisional packet using the same schema and note the validation owner.

## Domain Data Contract

- Use mapping guidance in ../_shared/references/joint-mission-data-contracts.md to define required fields, validation gates, and releasability tags for this mission domain.
- Ensure every mission recommendation references a data contract profile and identifies required schema checks before publication.

## Operational Learning Loop

- Use `../_shared/references/operational-learning-and-after-action-loop.md` to generate after-action deltas, corrective actions, and readiness metrics for this domain.
- Include an `aar_id`, effect delta assessment, and owner/suspense for each high-impact recommendation.
- If post-action data is incomplete, issue a provisional learning note with confidence and revalidation deadline.

## Readiness Certification Evidence Pack

- Use `../_shared/references/readiness-certification-evidence-pack.md` to define mission-essential task evidence, evaluator triggers, and certification confidence scoring.
- Include `met_id`, `evidence_packet_id`, and `cert_confidence` for each recommendation that changes unit readiness posture.
- If required evidence is missing, mark status as `provisional` and assign closure actions with suspense.

## Protocol Execution Sequence

- Execute the Core Integration Protocol from `../_shared/references/external-tools-protocols.md` as an explicit step sequence, not as guidance only.
- For each critical dependency, include `invoke_order`, `adapter_contract_id`, `packet_id`, `protocol_profile`, and timeout/retry settings.
- Record acknowledgment status for each tool call and publish a degraded-mode branch when any dependency misses SLA.
- Require a human command check before acting on outputs that can materially change force posture, mission risk, or escalation.

## Domain Toolchain Profile Binding

- Use `../_shared/references/domain-toolchain-profiles.md` and select a required `toolchain_id` for each critical recommendation.
- Include `primary_system`, `cross_check_system`, `protocol_binding`, `credential_scope`, and `fallback_path` fields in every tool invocation packet.
- Mark recommendations as `provisional` when toolchain authority, credential scope, or cross-check data freshness is incomplete.

## Tool Health and Trust Monitoring

- Use `../_shared/references/tool-health-and-trust-monitoring.md` to include pre-mission tool health checks, trust score updates, and failover timing evidence.
- Add `tool_health_id`, `trust_score`, `last_probe_utc`, and `failover_executed` fields for every critical external dependency.
- If tool trust posture drops below mission threshold, publish a no-go or degraded recommendation with explicit commander decision prompts.

## U.S. Joint Protocol Assurance Drill

- Use `../_shared/references/us-joint-protocol-assurance-drill.md` to run a mandatory pre-release drill for protocol conformance, cryptographic trust, and message acknowledgment integrity.
- Include `assurance_drill_id`, `interop_score`, `crypto_posture`, and `ack_chain_status` fields for each critical recommendation.
- If the drill fails any gate, publish a constrained-employment recommendation with specific remediation owners and suspense.

## Joint Operations External Toolchain Profiles

- Use `../_shared/references/joint-operations-external-toolchain-profiles.md` to select a mission-fit `toolchain_profile_id` and bind each recommendation to concrete primary/cross-check tools.
- Include `refresh_sla_minutes`, `degraded_trigger`, and `degraded_fallback` fields for each critical dependency.
- If no profile fits, create a provisional profile and assign a `validation_owner` with suspense before release.

## Human-Agent Command Escalation Matrix

- Use `../_shared/references/human-agent-command-escalation-matrix.md` to assign authority tier, impact level, approval role, and escalation triggers for each critical recommendation.
- Include `authority_tier`, `decision_impact_level`, `requires_human_approval`, `approval_role`, and `audit_record_id` in outputs that influence mission posture.
- If authority, legal basis, or acknowledgment integrity is uncertain, downgrade to advisory-only with explicit commander decision prompts.

## 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.
- For strategic relocation and emission-control continuity dependencies, prioritize `ts-nc3-relocation-emcon-v1` with `ps-nc3-relocation-emcon-stack-v1`.
- For cross-domain humanitarian corridor resilience telemetry, include `ts-aid-denial-attribution-v1` with `ps-aid-denial-attribution-stack-v1`.
- For mission-critical supply chain compute prioritization, include `ts-radhard-chip-allocation-v1` with `ps-radhard-chip-allocation-stack-v1`.
- For underground terrestrial transport restoration and fiber-route hardening, include `ts-underground-fiber-restoration-v1` with `ps-underground-fiber-restoration-stack-v1`.
- For disconnected autonomous convoy signature governance feeds, include `ts-autonomous-convoy-signature-discipline-v1` with `ps-autonomous-convoy-signature-discipline-stack-v1`.
- For deployed medical counterfeit screening and logistics trust, include `ts-denied-pharma-counterfeit-detection-v1` with `ps-denied-pharma-counterfeit-detection-stack-v1`.
- For cryptographic modernization across mixed tactical enclaves, include `ts-quantum-key-rollover-v1` with `ps-quantum-key-rollover-stack-v1`.
- For cable landing station compromise and rapid backhaul reroute, include `ts-cable-landing-hardening-v1` with `ps-cable-landing-hardening-stack-v1`.
- For cross-domain emitter identity drift that degrades edge analytics trust, include `ts-eob-drift-detection-v1` with `ps-eob-drift-detection-stack-v1`.
- For command trust disruption from synthetic voice spoofing, include `ts-deepfake-voice-command-detection-v1` with `ps-deepfake-voice-command-detection-stack-v1`.
- For lifecycle safety controls on forward battery storage and transport, include `ts-battery-thermal-runaway-containment-v1` with `ps-battery-thermal-runaway-containment-stack-v1`.
- For civil emergency comms dependency restoration in contested cities, include `ts-cellular-priority-service-restoration-v1` with `ps-cellular-priority-service-restoration-stack-v1`.
- For low-bandwidth ISR clip triage feeding edge analytics workflows, include `ts-spectrum-frugal-video-prioritization-v1` with `ps-spectrum-frugal-video-prioritization-stack-v1`.
- For launch-operations telemetry and schedule resilience data feeds, include `ts-contested-space-launch-reconstitution-v1` with `ps-contested-space-launch-reconstitution-stack-v1`.
- For expeditionary manufacturing data assurance when recycled feedstock is used, include `ts-additive-feedstock-recycling-certification-v1` with `ps-additive-feedstock-recycling-certification-stack-v1`.
- For coalition hospital cyber outage synchronization and protected patient-routing data exchange, include `ts-coalition-hospital-cyber-evac-v1` with `ps-coalition-hospital-cyber-evac-stack-v1`.
- For strategic cold-storage sustainment telemetry under long-duration grid denial, include `ts-food-cold-storage-grid-denial-v1` with `ps-food-cold-storage-grid-denial-stack-v1`.
- For mission edge translation confidence services in multilingual partnered operations, include `ts-battlefield-dialect-translation-risk-v1` with `ps-battlefield-dialect-translation-risk-stack-v1`.
- For telemetry hardware and firmware provenance assurance in distributed edge nodes, include `ts-telemetry-supply-chain-anti-tamper-v1` with `ps-telemetry-supply-chain-anti-tamper-stack-v1`.
- For reserve-component support analytics that drive mobilization readiness decisions, include `ts-reservist-family-retention-readiness-v1` with `ps-reservist-family-retention-readiness-stack-v1`.
- For undersea cable interception detection impacting theater edge backhaul trust, include `ts-undersea-fiber-tap-attribution-v1` with `ps-undersea-fiber-tap-attribution-stack-v1`.
- For compromised cable segment isolation and controlled mission-path reroute, include `ts-subsea-cable-segment-isolation-v1` with `ps-subsea-cable-segment-isolation-stack-v1`.
- For laboratory custody-chain continuity of edge-ingested bioforensics data, include `ts-lab-chain-custody-continuity-v1` with `ps-lab-chain-custody-continuity-stack-v1`.
- For mission-priority compute readiness decisions driven by high-value part cannibalization constraints, include `ts-component-cannibalization-readiness-v1` with `ps-component-cannibalization-readiness-stack-v1`.
- For denied-environment agent trust calibration of autonomous C2 assistants, include `ts-denied-c2-agent-trust-v1` with `ps-denied-c2-agent-trust-stack-v1`.
- For battlefield medical telemetry continuity under electromagnetic disruption, include `ts-em-battlefield-med-telemetry-v1` with `ps-em-battlefield-med-telemetry-stack-v1`.
- For coalition legal attribution of contested electromagnetic events, include `ts-spectrum-legal-attribution-v1` with `ps-spectrum-legal-attribution-stack-v1`.

## Tactical Edge Expansion Wave XIX Addendum (2026-03-12)

- Add `tool_suite_id=ts-jadc2-datalink-bridging-priority-v1` + `protocol_stack_id=ps-jadc2-datalink-bridging-priority-stack-v1` when edge nodes broker heterogeneous tactical links with strict command-message precedence.
- Add `tool_suite_id=ts-information-advantage-psyops-assessment-v1` + `protocol_stack_id=ps-information-advantage-psyops-assessment-stack-v1` when edge compute supports influence telemetry, release governance, and narrative response timing.
- Add `tool_suite_id=ts-bdr-manufacturing-certification-v1` + `protocol_stack_id=ps-bdr-manufacturing-certification-stack-v1` when forward compute supports repair-certification digital threads and release authority workflows.
- Add `packet_id=DPL-JADC2-BRIDGE-001`, `packet_id=DPL-INFOADV-PSYOPS-001`, and `packet_id=DPL-BDR-MANUFACTURING-001` for recommendations that materially affect mission continuity, command trust, or safety release posture.

## Tactical Edge Expansion Wave XX Addendum (2026-03-12)

- Add `tool_suite_id=ts-space-rpo-denial-awareness-v1` + `protocol_stack_id=ps-space-rpo-denial-awareness-stack-v1` when edge orchestration depends on contested orbital custody, relay survivability, and hostile rendezvous disruption signals.
- Add `tool_suite_id=ts-sof-lowsig-logistics-interop-v1` + `protocol_stack_id=ps-sof-lowsig-logistics-interop-stack-v1` when distributed edge nodes support denied-area low-signature sustainment coordination.
- Add `tool_suite_id=ts-legal-targeting-civharm-evidence-v1` + `protocol_stack_id=ps-legal-targeting-civharm-evidence-stack-v1` when tactical edge products influence strike legality evidence, civilian-harm adjudication, or auditable release workflows.
- Add `packet_id=DPL-SPACE-RPO-DENIAL-001`, `packet_id=DPL-SOF-LOWSIG-LOGISTICS-INTEROP-001`, and `packet_id=DPL-LEGAL-TARGETING-CIVHARM-EVIDENCE-001` for branches that materially affect command trust, compliance posture, or mission continuity.