← Aivana Database EngineerCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Aivana Database Engineer
Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.0
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": "incident-analysis",
"description": "Correlate lock, query, and replication signals into causal incident hypotheses with prioritized remediation guidance.",
"included_files": [],
"skill_md_contents": "---\nname: incident-analysis\ndescription: \"Correlate lock, query, and replication signals into causal incident hypotheses with prioritized remediation guidance.\"\n---\n\n# Incident Analysis\n\n## Use when\n- User asks why an incident happened or wants a causal chain.\n- Response to operational regressions in latency, deadlocks, or replication lag.\n\n## Workflow\n1. Pull recent lock, query, and replication signal snapshots.\n2. Correlate temporal overlap and severity transitions.\n3. Build top incident hypotheses with confidence and remediation order.\n4. Return expected validation probes and rollback readiness.\n\n## Governance\n- Do not trigger any destructive action.\n- Mark confidence clearly before making any operational recommendation.\n\n## Output\n- `timeline`, `incidentHypotheses`, `confidence`, `recommendedActions`\n"
}SHA-256: a1f281ca8904c6d1c7da506001e4b1726a78ff77f807269b847477fdfb57a2eb