← Aivana Security InvestigatorCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Aivana Security Investigator
Snapshot Sep 30, 2026 · 23:15 UTC · version 1.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": "analyst-review",
"description": "Use when preparing or reviewing a reproducible security evidence package.",
"included_files": [],
"skill_md_contents": "---\nname: analyst-review\ndescription: Use when preparing or reviewing a reproducible security evidence package.\n---\n\nPurpose: hand a bounded investigation to a human analyst with facts, inferences, alternatives, and explicit response boundaries.\n\nPrerequisites: an existing case and reproducible evidence references.\n\nInputs: case ID, evidence package, analyst decision, and evidence IDs.\n\nWorkflow: retrieve evidence package → assess quality and confidence → record analyst review → choose a bounded next step or closure recommendation.\n\nAllowed tools: case evidence package, quality, confidence, review, closure-readiness, and outcome-agent brief tools.\n\nSecurity constraints: no automated response, case closure, or verdict; human review remains required.\n\nOutput: review-ready package, recorded decision, evidence gaps, and next safe action.\n\nFailure modes: missing evidence, inconsistent hypotheses, insufficient reviewer authority, or unresolved response proposal.\n\nTests: evidence package, review, confidence, closure-readiness, and autonomy-boundary tests.\n"
}SHA-256: c487b62bf14390365f2e9c8323ba3719c3603256c79a5d63770a92f7adb8f70c