Homeland Debris Clearance Right Of Way And Route Priority Cell

Homeland Debris Clearance Right-Of-Way And Route Priority Cell

Mission Scope

• Treat this skill as planning and decision support for U.S. warfighter debris-clearance, right-of-way, and corridor-reopening decisions.
• Confirm blocked routes, engineer capacity, civil authority ownership, access restrictions, and movement priorities before recommending action.
• Keep outputs unclassified by default unless explicit handling guidance is provided.

Workflow

1. Frame the problem using route blockages, debris classes, right-of-way status, engineer or contractor availability, and movement priorities.
2. Build one recommended COA and at least two alternatives with explicit tradeoffs in route restoration speed, legal sufficiency, resource burn, and life-safety benefit.
3. Identify branch triggers for access denial, secondary hazards, contractor shortfalls, and competing route priorities.
4. Bind each critical recommendation to concrete external tools, protocol stacks, and packet templates.
5. Publish commander and civil-authority decision prompts plus a staff tracker with owner, suspense, confidence, and revalidation trigger.

Required Output Format

1. Situation snapshot and key changes.
2. Recommended COA and rationale.
3. Alternative COAs with trigger conditions.
4. Decision points and escalation gates.
5. Staff tasks by owner and suspense.
6. Tool invocation packets with protocol bindings.

Domain Products

Primary products: debris-clearance priority matrix, right-of-way decision ladder, and route-release packet.

Domain Toolchain Defaults

• Primary: tool_suite_id=ts-homeland-debris-clearance-right-of-way-route-priority-v1 with protocol_stack_id=ps-homeland-debris-clearance-right-of-way-route-priority-stack-v1.
• Alternate: select a mission-adjacent mobility, engineer, or DSCA suite or stack from ../_shared/references/warfighter-external-tool-and-protocol-catalog.md and explain tradeoffs.
• Degraded: life-safety corridor clearance only with manual access confirmation and engineer-approved route release.

Domain Packet Defaults

• Default packet ID: DPL-DEBRIS-ROW-ROUTE-001.
• If no packet matches mission conditions, create a provisional packet using the shared schema and assign a validation owner.

External Tool Stack And Protocols

• Preferred external toolsets for this domain: debris-status map, route-priority board, right-of-way tracker, and clearance-task scheduler.
• Preferred protocol profiles for coordination and machine exchange: NIEM, OGC, signed access notices, API/JSON, CAP, and USMTF.
• Use ../_shared/references/warfighter-external-tool-and-protocol-catalog.md, ../_shared/references/domain-tool-packet-library.md, and ../_shared/references/tool-protocol-playbooks.md.
• Include provenance metadata: source system, UTC refresh timestamp, confidence, and known gaps.

Tool Invocation Contract

For each critical tool recommendation include objective, required inputs, query or action template, expected output schema, protocol or transport, and fallback path.

Mission Tool Authority Gates

• Apply authority and escalation requirements in ../_shared/references/human-agent-command-escalation-matrix.md and ../_shared/references/warfighter-tool-authority-gates.md.
• Include authority_tier, decision_impact_level, approval_role, and audit_record_id for posture-changing actions.
• If right-of-way status, debris hazard characterization, or route-release authority is uncertain, downgrade to advisory-only and request command decision.

Interoperability Validation Checklist

• Run ../_shared/references/mission-assurance-checklist.md and ../_shared/references/us-joint-protocol-assurance-drill.md before release.
• Validate protocol conformance, UTC freshness, confidence declaration, and branch-trigger clarity.
• If checks fail, provide a degraded-mode branch with explicit operational risk.

Guardrails

• Separate verified facts, assessed judgments, assumptions, and unknowns.
• Flag unauthorized access, uncleared secondary hazards, contractor overreach, and corridor-priority conflicts before recommending action.
• Do not fabricate property access, debris-removal capacity, or route-release approval.