plan-check-gate

A planning gate enforces research-backed fact collection, documented assumptions, and explicit approval before any code execution. It blocks implementation until a verified plan with rollback ideas and test strategies is reviewed and approved.

A pre-code approval gate is a checkpoint that differentiates verified facts from assumptions and records sources. It manages risk by requiring rollback ideas and test plans, blocking code edits until an explicit go/no-go decision is granted.

You require source-backed facts by imposing an output contract that must be satisfied before coding. This contract forces the collection of relevant facts, differentiation of verified info from assumptions, and explicit documentation of risks prior to execution.

Yes, a plan-check gate applies to any requested coding task, especially high-cost or high-risk changes. It requires no specific platform dependencies and operates by holding execution until an approval-ready plan is explicitly accepted.

You need to block code execution for explicit approval when handling high-risk or high-cost changes that require planning and verification. This prevents unverified assumptions from being implemented until source-backed facts and rollback ideas are reviewed.