zwright8 Homeland Critical Waterway Lock Dam Cyber Physical Continuity Cell
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
- Frame the mission problem using the latest operational context and critical dependencies.
- Identify assumptions, decision thresholds, and indicators that invalidate the current plan.
- Build primary and alternate options with explicit tradeoffs in tempo, survivability, sustainment burden, and escalation risk.
- Integrate dependencies across command and control, movement/maneuver, fires/effects, intelligence, protection, sustainment, and information.
- Produce commander-facing outputs plus a staff-action version with owners, suspense dates, and branch triggers.
Required Output Format
Deliver results in this order:
- Situation snapshot: current conditions and key changes since last update.
- Recommended option: one clearly stated recommendation and rationale.
- Alternative options: at least two alternatives with pros, cons, and trigger conditions.
- Decision points: what must be decided now, later, or pre-delegated.
- Staff tasking: who does what by when.
Domain Products
Primary products for this skill: waterway continuity ladder, lock/dam restoration priority board, DSCA support tasking packet.
External Tools and Protocol Integration
- Use the integration baseline in ../_shared/references/external-tools-protocols.md.
- Prioritize these tools for this domain: industrial control incident dashboards, inland waterway traffic systems, hydraulic safety monitors, interagency restoration planners.
- Prioritize these protocol families for this domain: NIMS/ICS, NIEM, USMTF, API/JSON.
- Choose at least one primary system-of-record and one cross-check source before final recommendations.
- 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 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.
Authority and Human Approval Gates
- Apply escalation requirements in ../_shared/references/human-agent-command-escalation-matrix.md and ../_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.
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.
- Use ../_shared/references/domain-tool-packet-library.md to include machine-ingestible packet templates.
- Include tool_suite_id=ts-homeland-critical-waterway-lock-dam-cyber-physical-continuity-cell-v1, protocol_stack_id=ps-homeland-critical-waterway-lock-dam-cyber-physical-continuity-cell-stack-v1, and packet_id=DPL-LOCK-DAM-CYBER-PHYSICAL-CONTINUITY-001 for each critical recommendation.
- If no suite fits, define a provisional suite and assign validation_owner and revalidation_utc before release.
Guardrails
- Flag gaps where assumptions exceed evidence.
- Separate facts, assessed judgments, and unknowns.
- Do not fabricate authorities, approvals, or source evidence.