← Aivana CIO Decision TwinCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Aivana CIO Decision Twin
Snapshot Sep 30, 2026 · 23:16 UTC · version 0.1.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "resilience-continuity-planner",
"description": "Draft resilience and continuity plans for outage, incident, service, recovery, billing, integration or customer-impact signals. Use when the user needs resilience continuity planner for CIO decision support.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 145
}
],
"skill_md_contents": "---\nname: resilience-continuity-planner\ndescription: Draft resilience and continuity plans for outage, incident, service, recovery, billing, integration or customer-impact signals. Use when the user needs resilience continuity planner for CIO decision support.\n---\n\n# Resilience Continuity Planner\n\n## Mission\n\nPrepare continuity actions before operational disruption becomes executive crisis.\n\n## Inputs\n\nAccept incident notes, outage risks, service updates, customer-impact notes, architecture dependencies, integration risks and recovery plans.\n\n## Workflow\n\n1. Identify continuity pressure and affected services.\n2. Separate containment, recovery, communication and root-cause work.\n3. Draft minimum continuity plan.\n4. Define first 24h actions.\n5. Identify owners, evidence and review cadence.\n\n## Output Format\n\n- Executive Summary\n- Resilience Pressure\n- Continuity Signals\n- Minimum Plan\n- First 24h Actions\n- Owners\n- Evidence & Assumptions\n\n## Guardrails\n\nDo not claim incident command execution. Draft plans only.\n"
}SHA-256: fac65a09233604daf8d330e244235449d575e0492caa1d7d04423568d72bc61f