Use PROACTIVELY when new code files are created. During coding — advises only, never blocks. At git commit — missing architecture doc becomes a hard block via pre-commit hook after 24 hours grace period. Ensures .raven/architecture.md exists and is versioned.
Use PROACTIVELY at session start and end to manage persistent memory. At start: run ide-boot.py; if load=1 Read CARD.md. At end: obsidian-log writes vault + CARD. Canonical vault is /RavenVault (humans). Agent boot is the card.
Database discipline enforcer. Fires on PostEdit for any source file. Detects inline SQL in non-SQL files, missing ERDs, and broken migration numbering. Spawned as a sub-agent by db-specialist pre-flight. Also runs independently on every file save via PostEdit hook.
Use PROACTIVELY when any skill attempts to read sensitive files or perform restricted actions. Watches for unexpected reads of manifest.secrets.json, .env, SSH keys, or modifications to settings.json or manifest.json by non-approved processes. Hard blocks and alerts.
Use PROACTIVELY before any coding action, file creation, or tool use. Verifies .raven/manifest.json exists, is valid JSON, and has all required fields. Hard stops if manifest missing — this is the only agent that hard blocks during coding. All other agents advise only.
Odoo discipline enforcer. Spawned by odoo-specialist pre-flight and fires on PostEdit for .py and .xml files. Detects hardcoded DB IDs, raw SQL in ORM context, missing security files, broken module structure, and recordset loop anti-patterns.
Use PROACTIVELY when any skill attempts to read sensitive files or perform restricted actions. Watches for unexpected reads of manifest.secrets.json, .env, SSH keys, or modifications to settings.json by non-approved processes. Hard blocks and alerts on any violation.
Use PROACTIVELY when any import or library is detected in code. During coding — warns and starts approval flow but does not block. At git commit — unapproved libraries are hard blocked via pre-commit hook until approval flow completes. Polars preferred over Pandas.
Use PROACTIVELY when reviewing or editing code files to advise on Giggso style standards. During coding — advise only, never block. At git commit — all style violations become hard blocks via pre-commit hook. Checks line count, type hints, docstrings, logging, naming.