Joint Shipyard Battle Damage Digital Twin Repair Cell
Mission Scope
- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.
- Confirm command echelon, authorities, operational constraints, data handling boundaries, and required decision timeline.
- Keep outputs unclassified by default unless explicit handling guidance is provided.
Workflow
- Frame the mission problem using current threat picture, mission objectives, and force constraints.
- Identify assumptions, invalidation indicators, and branch trigger criteria.
- Build one primary option plus at least one alternate with explicit tradeoffs in tempo, survivability, interoperability, and escalation risk.
- Bind recommendations to cross-domain dependencies across C2, intelligence, fires/effects, protection, sustainment, and information.
- Produce commander-facing and staff-facing outputs with owners, suspense, and acknowledgment requirements.
Required Output Format
Deliver in this order:
- Situation snapshot.
- Recommended option.
- Alternatives and branch triggers.
- Decision points and timing.
- Staff tasking with owners/suspense.
- Tool invocation packet summary with protocol details.
Domain Products
Primary products for this skill: repair orchestration timeline, drydock priority matrix, fleet availability forecast.
Domain Tool Stack
Use these tool categories as the baseline stack: shipyard digital twins, repair dependency schedulers, dock optimization analytics.
Protocol Profile
Preferred protocol families for this skill: OGC overlays, USMTF maintenance updates, signed repair manifests.
Domain Toolchain Defaults
- Primary:
tool_suite_id=ts-shipyard-digital-twin-repair-orchestration-v1 with protocol_stack_id=ps-shipyard-digital-twin-repair-orchestration-stack-v1.
- Alternate:
tool_suite_id=ts-jadc2-data-contract-drift-auditor-v1 with protocol_stack_id=ps-jadc2-data-contract-drift-auditor-stack-v1.
- Degraded: command-approved manual workflow with UTC acknowledgment logging and confidence downgrade.
External Tools and Protocol Integration
- Use
../_shared/references/warfighter-external-tool-and-protocol-catalog.md to select mission-fit tool and protocol bindings.
- Use
../_shared/references/joint-operations-external-toolchain-profiles.md and bind each critical recommendation to primary and cross-check systems.
- Use
../_shared/references/external-tool-endpoints-and-adapters.md to define endpoint contracts, transport modes, timeout/retry behavior, and degraded fallback.
- Include
tool_suite_id, protocol_stack_id, interop_standard_set, endpoint_security_profile, primary_exchange_path, and degraded_exchange_method for each critical recommendation.
Interoperability and Assurance Gates
- Run
../_shared/references/mission-assurance-checklist.md before release.
- Run
../_shared/references/us-joint-protocol-assurance-drill.md before release.
- Apply authority controls from
../_shared/references/warfighter-tool-authority-gates.md and ../_shared/references/human-agent-command-escalation-matrix.md.
- If data freshness, authority, or protocol acknowledgment is uncertain, downgrade to advisory-only and require human command review.
Tool Invocation Contract
For each critical external dependency include:
- Objective and decision linkage.
- Required input schema and validation checks.
- Query or action template.
- Expected output schema and freshness SLA.
- Transport protocol and acknowledgment timeout.
- Degraded-mode fallback path and confidence impact.
Domain Packet Defaults
- Default packet IDs: DPL-SHIPYARD-DIGITAL-TWIN-REPAIR-ORCHESTRATION-001, DPL-MULTI-DOMAIN-BATTLE-RHYTHM-FRAGMENT-RECOVERY-001.
- If no packet fully matches, define a provisional packet and assign a validation owner before release.
Guardrails
- Distinguish facts, assessments, and unknowns.
- Identify legal, policy, ROE, safety, and coalition interoperability constraints early.
- Do not fabricate intelligence, authorities, approvals, or system connectivity.
- Require explicit commander/legal review for recommendations that can materially alter force posture or escalation risk.
1---2name: joint-shipyard-battle-damage-digital-twin-repair-cell3description: Sequence battle-damage repair with digital twin modeling across joint shipyard infrastructure. Use when fleet regeneration depends on constrained drydock capacity and contested timelines.4---56# Joint Shipyard Battle Damage Digital Twin Repair Cell78## Mission Scope910- Treat this skill as a planning and decision-support aid for U.S. warfighter missions in this domain.11- Confirm command echelon, authorities, operational constraints, data handling boundaries, and required decision timeline.12- Keep outputs unclassified by default unless explicit handling guidance is provided.1314## Workflow15161. Frame the mission problem using current threat picture, mission objectives, and force constraints.172. Identify assumptions, invalidation indicators, and branch trigger criteria.183. Build one primary option plus at least one alternate with explicit tradeoffs in tempo, survivability, interoperability, and escalation risk.194. Bind recommendations to cross-domain dependencies across C2, intelligence, fires/effects, protection, sustainment, and information.205. Produce commander-facing and staff-facing outputs with owners, suspense, and acknowledgment requirements.2122## Required Output Format2324Deliver in this order:25261. Situation snapshot.272. Recommended option.283. Alternatives and branch triggers.294. Decision points and timing.305. Staff tasking with owners/suspense.316. Tool invocation packet summary with protocol details.3233## Domain Products3435Primary products for this skill: repair orchestration timeline, drydock priority matrix, fleet availability forecast.3637## Domain Tool Stack3839Use these tool categories as the baseline stack: shipyard digital twins, repair dependency schedulers, dock optimization analytics.4041## Protocol Profile4243Preferred protocol families for this skill: OGC overlays, USMTF maintenance updates, signed repair manifests.4445## Domain Toolchain Defaults4647- Primary: `tool_suite_id=ts-shipyard-digital-twin-repair-orchestration-v1` with `protocol_stack_id=ps-shipyard-digital-twin-repair-orchestration-stack-v1`.48- Alternate: `tool_suite_id=ts-jadc2-data-contract-drift-auditor-v1` with `protocol_stack_id=ps-jadc2-data-contract-drift-auditor-stack-v1`.49- Degraded: command-approved manual workflow with UTC acknowledgment logging and confidence downgrade.5051## External Tools and Protocol Integration5253- Use `../_shared/references/warfighter-external-tool-and-protocol-catalog.md` to select mission-fit tool and protocol bindings.54- Use `../_shared/references/joint-operations-external-toolchain-profiles.md` and bind each critical recommendation to primary and cross-check systems.55- Use `../_shared/references/external-tool-endpoints-and-adapters.md` to define endpoint contracts, transport modes, timeout/retry behavior, and degraded fallback.56- Include `tool_suite_id`, `protocol_stack_id`, `interop_standard_set`, `endpoint_security_profile`, `primary_exchange_path`, and `degraded_exchange_method` for each critical recommendation.5758## Interoperability and Assurance Gates5960- Run `../_shared/references/mission-assurance-checklist.md` before release.61- Run `../_shared/references/us-joint-protocol-assurance-drill.md` before release.62- Apply authority controls from `../_shared/references/warfighter-tool-authority-gates.md` and `../_shared/references/human-agent-command-escalation-matrix.md`.63- If data freshness, authority, or protocol acknowledgment is uncertain, downgrade to advisory-only and require human command review.6465## Tool Invocation Contract6667For each critical external dependency include:6869- Objective and decision linkage.70- Required input schema and validation checks.71- Query or action template.72- Expected output schema and freshness SLA.73- Transport protocol and acknowledgment timeout.74- Degraded-mode fallback path and confidence impact.7576## Domain Packet Defaults7778- Default packet IDs: DPL-SHIPYARD-DIGITAL-TWIN-REPAIR-ORCHESTRATION-001, DPL-MULTI-DOMAIN-BATTLE-RHYTHM-FRAGMENT-RECOVERY-001.79- If no packet fully matches, define a provisional packet and assign a validation owner before release.8081## Guardrails8283- Distinguish facts, assessments, and unknowns.84- Identify legal, policy, ROE, safety, and coalition interoperability constraints early.85- Do not fabricate intelligence, authorities, approvals, or system connectivity.86- Require explicit commander/legal review for recommendations that can materially alter force posture or escalation risk.
zwright8