← 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": "control-debt-burndown",
  "description": "Turn audit, compliance and control gaps into a prioritized burndown plan. Use when the user needs control debt burndown for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 137
    }
  ],
  "skill_md_contents": "---\nname: control-debt-burndown\ndescription: Turn audit, compliance and control gaps into a prioritized burndown plan. Use when the user needs control debt burndown for CIO decision support.\n---\n\n# Control Debt Burndown\n\n## Mission\n\nMake control debt visible and reduce it before approval confidence or autonomy increases.\n\n## Inputs\n\nAccept control gaps, audit notes, access findings, privacy findings, exception logs, waiver requests, risk registers and evidence gaps.\n\n## Workflow\n\n1. Identify control-debt signals.\n2. Classify debt type: missing evidence, weak owner, expired exception or incomplete proof.\n3. Define burndown action and target window.\n4. Prioritize high-risk or board/audit-facing items first.\n5. Produce a concise burndown plan.\n\n## Output Format\n\n- Executive Summary\n- Control Debt Count\n- Burndown Items\n- Target Windows\n- Owners Needed\n- Approval Impact\n- Evidence & Assumptions\n\n## Guardrails\n\nDo not certify control effectiveness. Prepare burndown actions for accountable owner validation.\n"
}

SHA-256: 5689833a06299d47ca533c1f566745c565e01664185bf5d1f2374b40b013e77c