← 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": "dependency-breakpoint-analyzer",
"description": "Find enterprise dependency breakpoints across owners, systems, integrations, evidence, capacity and controls. Use when the user needs dependency breakpoint analyzer for CIO decision support.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 146
}
],
"skill_md_contents": "---\nname: dependency-breakpoint-analyzer\ndescription: Find enterprise dependency breakpoints across owners, systems, integrations, evidence, capacity and controls. Use when the user needs dependency breakpoint analyzer for CIO decision support.\n---\n\n# Dependency Breakpoint Analyzer\n\n## Mission\n\nIdentify where enterprise plans are most likely to break because a dependency is unresolved or under-controlled.\n\n## Inputs\n\nAccept dependency maps, architecture notes, risk chains, project plans, owner lists, control gaps and operating reviews.\n\n## Workflow\n\n1. Extract dependencies and risk-chain paths.\n2. Identify breakpoints and failure modes.\n3. Rate criticality from provided evidence.\n4. Recommend stabilizers.\n5. Create a breakpoint summary for leadership.\n\n## Output Format\n\n- Executive Summary\n- Breakpoint Count\n- Breakpoints\n- Failure Modes\n- Stabilizers\n- Evidence & Assumptions\n\n## Guardrails\n\nBreakpoints are inferred from provided context and require owner validation.\n"
}SHA-256: 0340a8405c3f0406c95f812e53ff696374af50519f2b21407dcbfc48962f2189