← 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": "validate-compliance",
"description": "Validate planned database operation against GDPR, HIPAA, SOC2, SOX, and ISO27001-aligned checks.",
"included_files": [],
"skill_md_contents": "---\nname: validate-compliance\ndescription: \"Validate planned database operation against GDPR, HIPAA, SOC2, SOX, and ISO27001-aligned checks.\"\n---\n\n# Validate Compliance\n\n## Use when\n- Migration, retention, or query policy needs explicit compliance verification.\n\n## Workflow\n1. Map action to compliance domains.\n2. Check for PII movement, retention conflicts, audit gaps, and access boundary breaches.\n3. Generate compliance gap list and mandatory remediation items.\n4. Produce approval-ready summary.\n\n## Governance\n- Do not auto-approve if any unresolved compliance blocker exists.\n- Require explicit acknowledgement of residual risk.\n\n## Output\n- `complianceStatus`, `violations`, `requiredFixes`, `approvalChecklist`\n"
}SHA-256: cf626b5ded6d59c71d27d691b5fd020be6b0a7bb1afc35797c365df052f59b13