zwright8 Disaster Recovery Orchestration for urban planning and mobility
Why This Skill Exists
Use disaster recovery orchestration in urban planning and mobility with emphasis on evidence quality, falsifiability, and calibration.
When To Use
Use this skill when the request explicitly needs "Disaster Recovery Orchestration for urban planning and mobility" outcomes in the urban planning and mobility domain.
Step-by-Step Implementation Guide
- Define measurable outcomes for Disaster Recovery Orchestration for urban planning and mobility, including baseline and target metrics for urban planning and mobility.
- Specify structured inputs/outputs for disaster recovery orchestration and validate schema contract edge cases.
- Implement the core disaster recovery orchestration logic with deterministic scoring and reproducible execution traces.
- Integrate orchestration policy, routing, approval gates, retries, and rollback for autonomous execution.
- Run unit, integration, simulation, and regression suites for Disaster Recovery Orchestration for urban planning and mobility under maximally truth-seeking conditions.
- Roll out behind a feature flag, monitor telemetry, and refine thresholds using observed operational outcomes.
Required Deliverables
- Capability contract: input schema, deterministic scoring, output schema, and failure modes.
- Runtime profile: resilience-engine using disaster recovery orchestration to produce disaster-recovery-orchestration-artifact-urban-planning-and-mobi.
- Orchestration integration: urban-planning-and-mobility:resilience-engine routing, approval gates, retries, and rollback controls.
- Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry.
Operational Runbook
Preflight
- Validate mission scope, contracts, and required inputs.
- Verify feature flag posture, dependencies, and approval prerequisites.
Execution
- Execute disaster recovery orchestration workflow with deterministic scoring and trace capture.
- Track posture transitions and preserve reproducible evidence artifacts.
Recovery
- Apply rollback strategy if posture is critical or guardrails fail.
- Escalate blocked execution to oversight with incident packet and trace references.
Handoff
- Publish outcome report, scorecard, and telemetry links.
- Queue follow-up tasks for unresolved risks, approvals, or optimization work.
Guardrails
- [quality] Require unit and integration validations before promoting Disaster Recovery Orchestration for urban planning and mobility. ->
run-validation:unit+integration+simulation+regression-baseline - [reliability] Trigger rollback on critical posture or repeated failures. ->
rollback:rollback-to-last-stable-baseline - [compliance] Require policy and approval gates prior to autonomous deployment. ->
approval-gates:policy-constraint-check+evidence-review - [cost] Respect bounded resource pressure and execution budget during scaling. ->
budget-guard:resource-pressure-cap