A specification bypass is a code change made without first changing the governing specification. Occasional bypasses may be acceptable early in specification-driven development; repeated bypasses suggest the specification process is too slow or features are too large to specify cleanly. section 3.4.2
Treat bypasses as a qualitative signal that the specification has stopped being where change happens. Revise the specification and regenerate the implementation; then check whether the same kind of intent gap recurs. section 3.4.2
Figure 3.4 The SDD governance operating loop involves observing gaps between intent and implementation and correcting them by revising the specification and regenerating the implementation. We then attribute the gap in the specification to where the intent was lost in the SDD workflow to improve it, and we confirm the improvement is working when the same class of gap stops recurring.

The governance loop shows how to trace gaps between intent and implementation back to the point where intent was lost. section 3.4.2
