missing-brain-first

A brain-first validation gate requires internal context to be processed before any external API calls are made. This enforces governance and safety by ensuring lookups are context-aware and preventing unsafe actions or data leaks.

To enforce compliance checks before external API calls, implement a deterministic external-call flow with an explicit brain-check hook. This ensures internal-context data precedes lookup attempts and provides visibility during safety audits.

Skipping internal context before external data fetches causes unsafe outcomes because lookups bypass brain-first checks, leading to uncontextualized decisions. This lack of guardrails in skill execution risks data leaks and unsafe actions.

To handle safe fallbacks during risk assessments, configure deterministic external-call flows with safe fallback handling. This prevents data leaks and ensures safety when external lookups fail or lack required brain-first validation context.

Yes, you can use brain-first guardrails for security auditing. They provide auditing visibility by requiring internal-context data before lookup attempts, helping identify and flag non-compliant skills that skip brain context before external data fetches.