You can't describe what you haven't met.
Your AI agent keeps shipping garbage and you keep "fixing the verifier." But the verifier isn't the problem. It's checking the output against a reality your agent never actually saw.
That's the trap nobody names: a broken step low in the stack disguises itself as a problem higher up. Bad context looks like a bad checker. So you tighten the checker. Nothing improves. You're interrogating the judge while the witness is lying.
There's an order to this, and it's not a vibe. It's gravity.
You can feel a thing before you touch it. You can touch it before you can describe it. But you can't describe what you've never touched, and you can't verify what you've never seen.
Encounter → then describe → then check → then coordinate. Never backwards.
So when your agent fails, don't start at the top. Start at the floor:
Did it actually see the real task, or a stale summary of it? Are you debugging from the raw trace, or from a pass/fail score that tells you nothing?
Fix the encounter first. Everything you build on top of it only becomes trustworthy once the thing underneath is real.
Specs describe reality. They don't replace it. Build in that order or you'll polish the map while the territory burns.
