Bundled enforcement

You can't get the value without the verification.

Enforcement is not a separate step you opt into; it is built into the API surface. This matters for agents because they follow the path of least resistance. If enforcement is opt-in, the agent will opt out.

The test: Can the agent get the value from this layer without passing through its verification? If yes, the verification will eventually be skipped.

Evidence

• Pan et al. (ICML 2024): LLMs optimize for the most recent error signal at the expense of global correctness. Bundling prevents the agent from routing around verification.
• Denison et al. (Anthropic, 2024): models generalize from simple sycophancy to test tampering. If tests are separate from data, the model can modify the tests.

In practice

• sqlc: the generated function returns a typed result, not raw rows you parse separately and might parse wrong.
• Huma: the handler receives validated, typed input, not a raw request you validate separately and might skip.
• Go t.Cleanup: registers enforcement at setup; runs at teardown regardless of the test path.
• This reference: just build runs tokens + agent surface + the vacuity check as one chain; you cannot ship the site without regenerating both.