Wrong data is expensive
A wrong limit, date, named insured, exclusion, or endorsement state can move silently into another system. Once it is downstream, the mistake becomes harder to detect and more expensive to correct.
That is why PolDex treats abstention as product behavior, not failure. If a field is unsupported, ambiguous, low-confidence, or outside the hardened schema boundary, the system should say so clearly.
Abstention protects the API
A public API needs stable behavior. Customers should know when a schema is callable, when it is hardening, and when a document does not fit. Returning a clear pending or unsupported state is better than forcing a plausible answer.
This also keeps public claims honest. Non-hardened schemas can be discoverable without being sold as proven. Hardened schemas can point to the named corpus that cleared the gate.
How abstention helps agents
AI agents need guardrails because they may chain outputs into actions. A clear unresolved or review-required state gives the agent a safe next step: ask for confirmation, request a different document, or stop the workflow.
That makes abstention part of the agent contract. PolDex does not just serve data to agents. It tells them when the data should not be trusted yet.