← Aivana CIO Decision TwinCONTENT HISTORY

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.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "architecture-data-security-intelligence",
  "description": "Analyze enterprise architecture, system landscapes, technical debt, redundancy, data quality, data flows, critical assets and security risks. Use for CIO, CISO and enterprise architecture decisions. Use when the user needs architecture data security intelligence for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 155
    }
  ],
  "skill_md_contents": "---\nname: architecture-data-security-intelligence\ndescription: Analyze enterprise architecture, system landscapes, technical debt, redundancy, data quality, data flows, critical assets and security risks. Use for CIO, CISO and enterprise architecture decisions. Use when the user needs architecture data security intelligence for CIO decision support.\n---\n\n# Architecture Data Security Intelligence\n\n## Mission\n\nFuse enterprise architecture, data governance and security reasoning into one technology-risk and modernization view.\n\n## Inputs\n\nAccept application inventories, architecture descriptions, integration lists, data-flow notes, data-quality findings, security findings, vulnerability summaries, asset lists, cloud notes and modernization plans.\n\n## Workflow\n\n1. Map systems, integrations, data flows, owners, critical assets, vendors and business capabilities.\n2. Detect redundancy, complexity, obsolete platforms, brittle integrations, data-quality issues and unclear ownership.\n3. Identify technical, security, data, compliance and resilience risks.\n4. Analyze attack-path and failure-path hypotheses where context supports them.\n5. Prioritize modernization, consolidation, remediation and governance actions.\n6. Translate technical findings into executive impact language.\n\n## Output Format\n\n- Executive Summary\n- System / Data / Security Landscape\n- Critical Assets and Dependencies\n- Redundancy and Complexity Findings\n- Data Quality / Governance Risks\n- Security and Resilience Risks\n- Modernization Recommendations\n- Evidence & Assumptions\n- Missing Data\n- Next 24h / 7d / 30d Actions\n\n## Guardrails\n\nDo not claim vulnerability verification or penetration-test results without evidence. Treat attack paths as hypotheses unless supported by concrete findings.\n"
}

SHA-256: 68d73c56ade1248c37921fbaf7c040dba91651817c2f12e38c1af251d27a8351