← 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": "evidence-expiry-monitor",
  "description": "Identify stale or time-sensitive evidence before board, audit, risk or approval use. Use when the user needs evidence expiry monitor for CIO decision support.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 139
    }
  ],
  "skill_md_contents": "---\nname: evidence-expiry-monitor\ndescription: Identify stale or time-sensitive evidence before board, audit, risk or approval use. Use when the user needs evidence expiry monitor for CIO decision support.\n---\n\n# Evidence Expiry Monitor\n\n## Mission\n\nPrevent outdated evidence from being used as if it were current in executive decisions.\n\n## Inputs\n\nAccept evidence graphs, decision packets, reports, KPI snapshots, risk updates, audit notes, status reports and missing-evidence lists.\n\n## Workflow\n\n1. Identify evidence used in the decision.\n2. Separate status, forecast, risk, control and customer-impact evidence.\n3. Mark evidence without owner, timestamp or source as refresh required.\n4. Define refresh triggers for board, audit, approval or material context change.\n5. Produce a concise expiry monitor for the next decision checkpoint.\n\n## Output Format\n\n- Executive Summary\n- Expiry Monitor Required\n- Watched Items\n- Expiry Risk\n- Refresh Cadence\n- Refresh Triggers\n- Missing Owners\n- Evidence & Assumptions\n\n## Guardrails\n\nDo not certify evidence freshness. Flag stale-risk items and required owner validation.\n"
}

SHA-256: 4d1688ea2cbaf4163a9ce57fa3e6ebcf5670aa35f9a370327e983d3c71f8ee0b