In AI-assisted software engineering pipelines, there is a clear boundary between what compilers can verify and what requires semantic understanding.
For everything syntactic and structural — formatting ( gofmt ), static analysis ( go vet ), race-condition testing ( go test -race ), and vulnerability scanning ( govulncheck ) — deterministic gates are unbeatable. Either the code compiles and passes tests, or the gate halts the pipeline with exit code 1 .
But what happens when a pipeline gate depends on semantics ?
"Does this diff touch authentication logic or cryptographic surface area?"
"Which specialized skill should handle this SQL migration failure: data-model , migration-reviewer , or dev-implementation ?"
"On a scale from 0 to 10, how well does this handoff report satisfy our architectural invariants?"
For the past two years, the industry's default answer has been "LLM-as-a-Judge" : sending a massive prompt to a slow, generative reasoning model (System 2) and hoping it outputs "Yes" or picks a…