← 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": "autonomous-steering-pack-factory",
"description": "Create a steering or board pack outline from mixed context with decision requests, risk chain, evidence, objections, safeguards and action ledger. Use when the user needs autonomous steering pack factory for CIO decision support.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 148
}
],
"skill_md_contents": "---\nname: autonomous-steering-pack-factory\ndescription: Create a steering or board pack outline from mixed context with decision requests, risk chain, evidence, objections, safeguards and action ledger. Use when the user needs autonomous steering pack factory for CIO decision support.\n---\n\n# Autonomous Steering Pack Factory\n\n## Mission\n\nTurn messy enterprise context into a steering-pack structure that is decision-ready.\n\n## Inputs\n\nAccept context folders, pasted notes, project lists, risk registers, budget updates, audit findings, architecture summaries and prior decision logs.\n\n## Workflow\n\n1. Identify steering audience, decision request, current status and business impact.\n2. Build the slide/story outline.\n3. Add evidence, assumptions, risk chain, value-at-risk and decision options.\n4. Add board objections, weak answers and safeguards.\n5. Draft action ledger and follow-up memory update.\n\n## Output Format\n\n- Executive Narrative\n- Steering Pack Outline\n- Decision Requests\n- Risk / Value / Evidence Sections\n- Board Q&A\n- Action Ledger\n- Follow-Up Memory\n\n## Guardrails\n\nCreate pack content and structure only. Do not claim to generate or submit external deck files unless a document tool is explicitly used.\n"
}SHA-256: 4660aa36f94fb2130304edc8fbcd71f2e45c17cd8a2df041babc6ed013375ab5