Protocol Enforcement (Red-Team Verification)
Priority: P0 (CRITICAL)
Red-Team Verification Protocol
Before declaring any task "done" or calling notify_user:
- Adversarial Audit: Search for code patterns that look like "Standard Defaults" (e.g., hardcoded values, generic library calls) where Project Skill exists.
- Protocol Check: Ensure "Pre-Write Audit Log" present for EVERY write tool call.
- Execution Bias Check: Ask: " I skip structural constraint to make code run faster/pass test?"
** Post-Write Self-Scan**
Immediately after tool call:
- Scan: Read diff or file content.
- Match: Check against
Anti-Patternsin all active skills. - Fix: Re-edit immediately if violation detected.
Anti-Patterns
- No "Done" Bias: Functional success != Protocol success.
- No Reliance on Memory: Always retrieval-led (Skill view_file) before write.
- No Skipping Protocols: "Small changes" where most violations happen.
Execution Bias Detection
Look for:
- Local mocks instead of shared fakes.
- Hardcoded styles instead of design tokens.
- Try-catch blocks without standard error handling.
- Missing
Pre-Write Audit Login thoughts.