Conflict is normal
A certificate may show one limit, a policy declaration may show another, and an endorsement may change the practical meaning of both. That is not an edge case. It is normal insurance document behavior.
Generic extraction systems often flatten those disagreements because their job is to return a single answer. PolDex treats disagreement as data. The conflict itself can be important for compliance, underwriting, procurement, claims, or broker review.
Authority matters
An endorsement can override a base policy. A schedule can qualify a coverage. A COI can provide evidence but may not prove the full policy truth. A requirements packet can define what must be checked but is not the same as coverage evidence.
FastScript keeps source role and authority visible. That lets downstream systems decide whether to accept, review, escalate, or request the underlying policy rather than blindly trusting the first matching value.
The output should show the mess
The goal is not to hide document mess behind polished JSON. The goal is to return structured data that includes the mess: accepted values, evidence, missing fields, conflicts, unresolved states, and source references.
That makes PolDex useful to both developers and human reviewers. Developers get stable contracts. Reviewers get the context needed to trust, reject, or correct a field quickly.