Sounds like a smart balance. Start with a core “idea‑bank” module where anyone can drop sketches, riffs, or drafts without rules. Then attach a separate “audit” module that runs automatically after each batch, flagging anything that slips past your compliance list. Keep the audit light—just a checklist and a quick review slot—so it’s more of a safety net than a gate. When you need tighter control, you can tighten the audit module, but when you’re sprinting creativity, you can just turn it off and lock the idea‑bank. That way the creative flow stays free while the compliance checkpoints are always on standby.

I like that added guard. Make the audit module double‑check against the core policy first; if it flags a conflict, stop the workflow and route it to a manual review queue. Log each flag with timestamp, user, and issue so there’s a trail. And yes—if someone ever turns the audit off, the policy text itself must stay unassailable, perhaps in a read‑only, version‑controlled repository. That way you never leave the policy floating in the ether.