# Defense Support Of Civil Authorities Crisis Cell

> Coordinate military support planning for domestic civil crises under approved authorities. Use when aligning DSCA requests, logistics support, and interagency coordination.

- Skill: `zwright8/defense-support-of-civil-authorities-crisis-cell` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add zwright8/defense-support-of-civil-authorities-crisis-cell`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zwright8/defense-support-of-civil-authorities-crisis-cell/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: zwright8 (https://skillmd.com/u/zwright8)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/zwright8/defense-support-of-civil-authorities-crisis-cell

---


# Defense Support Of Civil Authorities Crisis 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

1. Frame the mission problem using these core inputs: mission assignments, authority constraints, civil agency requests, force availability.
2. Identify assumptions, decision thresholds, and what intelligence or reporting would invalidate the current plan.
3. Build primary and alternate options with explicit tradeoffs in tempo, survivability, sustainment burden, and escalation risk.
4. Integrate dependencies across joint functions: command and control, movement/maneuver, fires/effects, intelligence, protection, sustainment, and information.
5. Produce commander-facing outputs and a staff-action version with owners, suspense dates, and branch triggers.

## Required Output Format

Deliver results in this order:

1. Situation snapshot: current conditions and key changes since 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: DSCA support plan, interagency coordination matrix, resource allocation timeline.

## External Tools and Protocol Integration

- Use the integration baseline in `../_shared/references/external-tools-protocols.md` and name the exact tools selected for this mission set.
- Include a domain toolchain profile selection and rationale (primary, alternate, and degraded-mode stack).
- Prioritize these tools or protocol families for this domain: NIMS/ICS workflows, 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 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.

## Domain Toolchain Override (2026-03-14, Skill Materialization Repair Wave)

- Add `tool_suite_id=ts-homeland-911-cell-broadcast-auth-mass-notification-continuity-v1` + `protocol_stack_id=ps-homeland-911-cell-broadcast-auth-mass-notification-continuity-stack-v1` when DSCA recommendations depend on trusted warning release, PSAP continuity, or mass-notification authenticity under telecom stress.
- Add `packet_id=DPL-HOMELAND-911-CELL-BROADCAST-AUTHENTICATION-MASS-NOTIFICATION-CONTINUITY-001` for branches that materially alter public-warning posture, alert release timing, or 911 mutual-aid requests.

## Domain Toolchain Override (2026-03-15, Expansion Wave LX Addendum)

- Add `tool_suite_id=ts-homeland-wildland-fire-airspace-retardant-priority-v1` + `protocol_stack_id=ps-homeland-wildland-fire-airspace-retardant-priority-stack-v1` when DSCA support depends on military airspace reprioritization, retardant scarcity, or smoke-driven sortie tradeoffs.
- Add `packet_id=DPL-WILDLAND-FIRE-AIRSPACE-RETARDANT-001` for branches that materially alter aviation support posture, airspace release timing, or protected-site prioritization.

## Domain Toolchain Override (2026-04-06, Expansion Wave LXX Addendum)

- Add `toolchain_id=TC-DSC-258`, `tool_suite_id=ts-homeland-dual-status-command-authority-integration-v1`, and `protocol_stack_id=ps-homeland-dual-status-command-authority-integration-stack-v1` when DSCA support depends on dual-status-command nomination, Title 10 versus Title 32 alignment, or split-C2 fallback.
- Add `toolchain_id=TC-EMAC-259`, `tool_suite_id=ts-homeland-emac-interstate-force-flow-synchronization-v1`, and `protocol_stack_id=ps-homeland-emac-interstate-force-flow-synchronization-stack-v1` when domestic response throughput depends on EMAC requests, staging density, or reception-node synchronization.
- Add `toolchain_id=TC-GOVRFF-260`, `tool_suite_id=ts-homeland-governor-request-for-forces-mission-assignment-v1`, and `protocol_stack_id=ps-homeland-governor-request-for-forces-mission-assignment-stack-v1` when DSCA recommendations depend on governor demand, mission-assignment approval, or sourcing viability.
- Add `toolchain_id=TC-TRIBAL-261`, `tool_suite_id=ts-homeland-tribal-sovereignty-defense-support-coordination-v1`, and `protocol_stack_id=ps-homeland-tribal-sovereignty-defense-support-coordination-stack-v1` when support options affect tribal consent, sovereign coordination, or protected-site access.
- Add `toolchain_id=TC-EOCFUSE-262`, `tool_suite_id=ts-homeland-emergency-manager-cop-fusion-v1`, and `protocol_stack_id=ps-homeland-emergency-manager-cop-fusion-stack-v1` when the recommendation depends on reconciling fragmented local reporting into a trusted domestic COP.
- Add `toolchain_id=TC-LEMOVE-263`, `tool_suite_id=ts-homeland-law-enforcement-military-movement-deconfliction-v1`, and `protocol_stack_id=ps-homeland-law-enforcement-military-movement-deconfliction-stack-v1` when support plans hinge on convoy legitimacy, checkpoint control, or route release under public-safety restrictions.
- Add `toolchain_id=TC-FISCAL-264`, `tool_suite_id=ts-homeland-dsca-reimbursement-funding-authority-v1`, and `protocol_stack_id=ps-homeland-dsca-reimbursement-funding-authority-stack-v1` when operational utility depends on valid funding lines, reimbursement timing, or cost-capture integrity.
- Add `toolchain_id=TC-JIC-265`, `tool_suite_id=ts-homeland-joint-information-center-civil-warning-unity-v1`, and `protocol_stack_id=ps-homeland-joint-information-center-civil-warning-unity-stack-v1` when DSCA outcomes depend on unified warning release, rumor control, or multilingual message governance.
- Add `packet_id=DPL-DUAL-STATUS-COMMAND-001`, `packet_id=DPL-EMAC-FORCE-FLOW-001`, `packet_id=DPL-GOV-RFF-MISSION-ASSIGNMENT-001`, `packet_id=DPL-TRIBAL-DSCA-SOVEREIGNTY-001`, `packet_id=DPL-EMERGENCY-MANAGER-COP-FUSION-001`, `packet_id=DPL-LE-MIL-MOVEMENT-DECONFLICT-001`, `packet_id=DPL-DSCA-FUNDING-AUTHORITY-001`, and `packet_id=DPL-JIC-CIVIL-WARNING-UNITY-001` for branches that materially alter DSCA posture, authorities, or public-safety timing.

## Domain Toolchain Override (2026-04-06, Expansion Wave LXXI Addendum)

- Add `toolchain_id=TC-DCO-266`, `tool_suite_id=ts-homeland-dco-fema-region-synchronization-v1`, and `protocol_stack_id=ps-homeland-dco-fema-region-synchronization-stack-v1` when DSCA execution depends on DCO tasking, RRCC or NRCC timing, or FEMA-region synchronization.
- Add `toolchain_id=TC-PRIVATECI-267`, `tool_suite_id=ts-homeland-private-sector-critical-infrastructure-coordination-v1`, and `protocol_stack_id=ps-homeland-private-sector-critical-infrastructure-coordination-stack-v1` when support options depend on owner-operator restoration commitments, private-sector lifeline data, or sector-priority conflicts.
- Add `toolchain_id=TC-MASSCARE-268`, `tool_suite_id=ts-homeland-mass-care-access-functional-needs-support-v1`, and `protocol_stack_id=ps-homeland-mass-care-access-functional-needs-support-stack-v1` when DSCA recommendations hinge on accessible transport, DME or oxygen sustainment, or caregiver continuity in shelters.
- Add `toolchain_id=TC-DEBRIS-269`, `tool_suite_id=ts-homeland-debris-clearance-right-of-way-route-priority-v1`, and `protocol_stack_id=ps-homeland-debris-clearance-right-of-way-route-priority-stack-v1` when route release, engineer prioritization, or right-of-way adjudication controls response tempo.
- Add `toolchain_id=TC-FATALITY-270`, `tool_suite_id=ts-homeland-fatality-management-morgue-family-assistance-v1`, and `protocol_stack_id=ps-homeland-fatality-management-morgue-family-assistance-stack-v1` when DSCA outcomes depend on morgue balancing, decedent accountability, or family-assistance-center integration.
- Add `toolchain_id=TC-HOSPDIV-271`, `tool_suite_id=ts-homeland-hospital-diversion-ambulance-va-dod-bed-bridge-v1`, and `protocol_stack_id=ps-homeland-hospital-diversion-ambulance-va-dod-bed-bridge-stack-v1` when support posture depends on diversion control, ambulance destination confidence, or VA-DOD bed bridging.
- Add `toolchain_id=TC-WATERCOM-272`, `tool_suite_id=ts-homeland-boil-water-food-safety-commodities-distribution-v1`, and `protocol_stack_id=ps-homeland-boil-water-food-safety-commodities-distribution-stack-v1` when life-safety recommendations depend on boil-water advisories, POD sequencing, or food-safety controls.
- Add `toolchain_id=TC-ENERGY-273`, `tool_suite_id=ts-homeland-energy-emergency-fuel-waiver-priority-restoration-v1`, and `protocol_stack_id=ps-homeland-energy-emergency-fuel-waiver-priority-restoration-stack-v1` when DSCA branches depend on emergency fuel waivers, generator support, or priority-restoration governance.
- Add `packet_id=DPL-DCO-FEMA-SYNC-001`, `packet_id=DPL-PRIVATE-SECTOR-CI-COORD-001`, `packet_id=DPL-MASS-CARE-AFN-001`, `packet_id=DPL-DEBRIS-ROW-ROUTE-001`, `packet_id=DPL-FATALITY-MORGUE-FAC-001`, `packet_id=DPL-HOSPITAL-DIVERSION-VA-DOD-001`, `packet_id=DPL-BOIL-WATER-COMMODITIES-001`, and `packet_id=DPL-ENERGY-FUEL-WAIVER-001` for branches that materially alter domestic-support timing, legitimacy, or life-safety posture.

## Domain Toolchain Override (2026-04-06, Expansion Wave LXXII Materialization Addendum)

- Add `toolchain_id=TC-HOUSING-240`, `tool_suite_id=ts-strategic-military-housing-utility-safety-and-restoration-v1`, and `protocol_stack_id=ps-strategic-military-housing-utility-safety-and-restoration-stack-v1` when DSCA support depends on housing habitability, utility isolation, or family relocation near military installations.
- Add `toolchain_id=TC-EVAC-242`, `tool_suite_id=ts-theater-evacuation-route-humanitarian-logistics-and-traffic-priority-v1`, and `protocol_stack_id=ps-theater-evacuation-route-humanitarian-logistics-and-traffic-priority-stack-v1` when domestic support recommendations hinge on evacuation-corridor release, humanitarian traffic arbitration, or shelter-diversion timing.
- Add `toolchain_id=TC-PUBCOMMS-244`, `tool_suite_id=ts-joint-incident-command-post-public-communications-and-media-contingency-v1`, and `protocol_stack_id=ps-joint-incident-command-post-public-communications-and-media-contingency-stack-v1` when DSCA execution depends on incident-command public messaging, life-safety release timing, or media contingency control.
- Add `toolchain_id=TC-PERMIT-246`, `tool_suite_id=ts-joint-civil-works-emergency-permitting-and-right-of-entry-v1`, and `protocol_stack_id=ps-joint-civil-works-emergency-permitting-and-right-of-entry-stack-v1` when engineer support depends on emergency permits, access authority, or right-of-entry acceleration.
- Add `toolchain_id=TC-SCHOOL-248`, `tool_suite_id=ts-homeland-base-school-transport-and-dependent-evacuation-v1`, and `protocol_stack_id=ps-homeland-base-school-transport-and-dependent-evacuation-stack-v1` when DSCA branches affect dependent accountability, school transport, or guardian reunification on defended installations.
- Add `packet_id=DPL-MIL-HOUSING-UTILITY-001`, `packet_id=DPL-EVAC-TRAFFIC-PRIORITY-001`, `packet_id=DPL-ICP-PUBLIC-COMMS-001`, `packet_id=DPL-RIGHT-OF-ENTRY-001`, and `packet_id=DPL-DEPENDENT-EVAC-001` for branches that materially alter domestic-support tempo, legitimacy, or life-safety posture.

## Domain Toolchain Override (2026-04-07, Expansion Wave LXXIII Addendum)

- Add `toolchain_id=TC-LEGALAID-282`, `tool_suite_id=ts-homeland-military-legal-assistance-identity-document-reissuance-v1`, and `protocol_stack_id=ps-homeland-military-legal-assistance-identity-document-reissuance-stack-v1` when DSCA support depends on legal-aid surge, identity-document recovery, or entitlement-proof continuity inside affected military communities.
- Add `toolchain_id=TC-PROTECT-283`, `tool_suite_id=ts-homeland-protective-order-domestic-violence-safe-housing-continuity-v1`, and `protocol_stack_id=ps-homeland-protective-order-domestic-violence-safe-housing-continuity-stack-v1` when domestic support posture depends on victim safety, protective-order continuity, or safe-housing availability.
- Add `toolchain_id=TC-POSTPARTUM-284`, `tool_suite_id=ts-homeland-postpartum-lactation-infant-formula-diaper-continuity-v1`, and `protocol_stack_id=ps-homeland-postpartum-lactation-infant-formula-diaper-continuity-stack-v1` when DSCA recommendations hinge on maternal-infant sustainment, lactation support, or formula and diaper continuity.
- Add `toolchain_id=TC-COSHELTER-285`, `tool_suite_id=ts-homeland-base-pet-service-animal-family-co-shelter-v1`, and `protocol_stack_id=ps-homeland-base-pet-service-animal-family-co-shelter-stack-v1` when shelter or evacuation compliance depends on pet and service-animal co-shelter viability.
- Add `toolchain_id=TC-FOODBRIDGE-286`, `tool_suite_id=ts-homeland-commissary-exchange-food-bank-school-meal-bridging-v1`, and `protocol_stack_id=ps-homeland-commissary-exchange-food-bank-school-meal-bridging-stack-v1` when community support depends on bridging commissary, food-bank, or school-meal disruption.
- Add `toolchain_id=TC-COURT-289`, `tool_suite_id=ts-homeland-installation-courthouse-custody-hearing-family-law-continuity-v1`, and `protocol_stack_id=ps-homeland-installation-courthouse-custody-hearing-family-law-continuity-stack-v1` when household stability and command confidence depend on courthouse access, custody hearings, or family-law filing continuity.
- Add `packet_id=DPL-LEGAL-AID-ID-REISSUE-001`, `packet_id=DPL-PROTECTIVE-ORDER-SAFE-HOUSING-001`, `packet_id=DPL-POSTPARTUM-LACTATION-FORMULA-001`, `packet_id=DPL-PET-SERVICE-ANIMAL-COSHELTER-001`, `packet_id=DPL-COMMISSARY-FOOD-BRIDGE-001`, and `packet_id=DPL-COURTHOUSE-CUSTODY-FAMILY-LAW-001` for branches that materially alter domestic-support legitimacy, household protection, or life-safety timing.

## Domain Toolchain Override (2026-04-07, Expansion Wave LXXII Addendum)

- Add `toolchain_id=TC-PHLAB-274`, `tool_suite_id=ts-homeland-public-health-laboratory-surge-specimen-chain-v1`, and `protocol_stack_id=ps-homeland-public-health-laboratory-surge-specimen-chain-stack-v1` when DSCA support depends on trusted diagnostic throughput, specimen-custody integrity, or public-health reporting speed.
- Add `toolchain_id=TC-MCM-275`, `tool_suite_id=ts-homeland-medical-countermeasure-pod-security-cold-chain-v1`, and `protocol_stack_id=ps-homeland-medical-countermeasure-pod-security-cold-chain-stack-v1` when domestic support options hinge on protected POD operations, refrigerated countermeasure release, or mass-dispensing security.
- Add `toolchain_id=TC-CORR-276`, `tool_suite_id=ts-homeland-corrections-facility-evacuation-guard-force-relief-v1`, and `protocol_stack_id=ps-homeland-corrections-facility-evacuation-guard-force-relief-stack-v1` when DSCA planning depends on lawful custody movement, guard-force relief, or receiving-site capacity.
- Add `toolchain_id=TC-COOL-277`, `tool_suite_id=ts-homeland-cooling-center-load-shedding-generator-priority-v1`, and `protocol_stack_id=ps-homeland-cooling-center-load-shedding-generator-priority-stack-v1` when life-safety posture depends on cooling-center viability, generator allocation, or rolling-blackout prioritization.
- Add `toolchain_id=TC-FERRY-278`, `tool_suite_id=ts-homeland-ferry-evacuation-island-resupply-priority-v1`, and `protocol_stack_id=ps-homeland-ferry-evacuation-island-resupply-priority-stack-v1` when isolated-population support depends on ferry lift, island resupply, or terminal-release sequencing.
- Add `toolchain_id=TC-WASTE-279`, `tool_suite_id=ts-homeland-wastewater-overflow-force-health-waterway-protection-v1`, and `protocol_stack_id=ps-homeland-wastewater-overflow-force-health-waterway-protection-stack-v1` when DSCA outcomes depend on sewage overflow containment, downstream warning integrity, or responder exposure control.
- Add `toolchain_id=TC-ANIMAL-280`, `tool_suite_id=ts-homeland-animal-disease-quarantine-food-system-defense-v1`, and `protocol_stack_id=ps-homeland-animal-disease-quarantine-food-system-defense-stack-v1` when response legitimacy depends on animal-disease quarantine, carcass-disposal support, or food-system continuity.
- Add `toolchain_id=TC-TRANSIT-281`, `tool_suite_id=ts-homeland-transit-bus-evacuation-staging-driver-continuity-v1`, and `protocol_stack_id=ps-homeland-transit-bus-evacuation-staging-driver-continuity-stack-v1` when evacuation tempo depends on transit-bus staging, driver availability, or protected pickup-route release.
- Add `packet_id=DPL-PUBLIC-HEALTH-LAB-CHAIN-001`, `packet_id=DPL-MCM-POD-COLDCHAIN-001`, `packet_id=DPL-CORRECTIONS-EVAC-GUARDFORCE-001`, `packet_id=DPL-COOLING-CENTER-GENERATOR-001`, `packet_id=DPL-FERRY-ISLAND-RESUPPLY-001`, `packet_id=DPL-WASTEWATER-OVERFLOW-WATERWAY-001`, `packet_id=DPL-ANIMAL-DISEASE-FOOD-DEFENSE-001`, and `packet_id=DPL-TRANSIT-BUS-EVAC-DRIVER-001` for branches that materially alter domestic-support timing, life-safety posture, or public legitimacy.