← 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": "decision-sla-enforcer",
"description": "Assign decision deadlines and escalation thresholds based on board risk, missing evidence, decision debt and business impact. Use when the user needs decision sla enforcer for CIO decision support.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 137
}
],
"skill_md_contents": "---\nname: decision-sla-enforcer\ndescription: Assign decision deadlines and escalation thresholds based on board risk, missing evidence, decision debt and business impact. Use when the user needs decision sla enforcer for CIO decision support.\n---\n\n# Decision SLA Enforcer\n\n## Mission\n\nPrevent executive decisions from drifting by assigning a clear decision SLA, owner checkpoint and breach consequence.\n\n## Inputs\n\nAccept decision packets, operating reviews, risk registers, steering actions, meeting notes and escalation context.\n\n## Workflow\n\n1. Identify open decisions, board risk, missing evidence and decision debt.\n2. Assign SLA: `24h`, `7d`, `30d` or `monitor`.\n3. Define owner, evidence gate, decision date and escalation threshold.\n4. State what happens if the SLA is missed.\n5. Produce a concise clearance plan.\n\n## Output Format\n\n- Executive Summary\n- Decision SLA\n- Breach Risk\n- SLA Drivers\n- Required Checkpoint\n- Escalation Threshold\n- Evidence & Assumptions\n\n## Guardrails\n\nDo not execute escalations. Draft the SLA and escalation logic for human approval.\n"
}SHA-256: ad7ab09d007110f99517d117174c66abad4b410f53669b4e3e5e06fe0dee1e7e