bicameral-guided

To block agent actions on decision drift, enable guided mode to enforce strict alignment between recorded intent and code, stopping operations before writes when divergent decisions or unresolved open questions are detected.

Guided mode stops decision drift by applying a strict enforcement layer over search and brief operations, blocking write actions and surfacing imperative ActionHints when divergent decision pairs or unresolved open questions are detected.

Yes, you can configure stop-and-review behavior via runtime environment variable overrides like BICAMERAL_GUIDED_MODE, or establish durable configuration parity using the .bicameral/config.yaml file to toggle between blocking and advisory modes.

The best way to prevent regressions during onboarding and demos is applying stop-and-review guided mode, which surfaces discrepancies and blocks write operations before execution to preserve alignment with recorded intent.

Yes, guided mode supports advisory behavior instead of blocking. Normal mode remains advisory, while the opt-in guided mode provides blocking behavior with an imperative tone specifically for critical-path work.

You should use stop-and-review mode for unresolved open questions to preserve alignment with recorded intent, ensuring the agent surfaces discrepancies and halts before executing write operations that could introduce regressions.