Registry coverage is not enough
A schema registry is useful because it tells developers what the platform intends to support. But a registry alone is not proof. The hard work is turning a schema from a named contract into a reliable extraction surface.
PolDex makes that difference explicit with maturity states. Hardened means the schema passed a named real-document benchmark. The current public universe is fully hardened: 56 schemas, 100+ documents per schema, and 99%+ benchmarked accuracy.
The proof gate
For each schema, PolDex built a corpus of real public documents, added source-verifiable labels, extracted required fields with evidence, scored exact labels and evidence, fixed misses, and only then promoted the schema.
The gate is intentionally repetitive. Every insurance line needs the same discipline: documents, labels, evidence, benchmark, regression, and public status. The repetition is what turns the platform into infrastructure rather than a collection of demos.
What hardening creates
Hardening creates schema memory. It teaches FastScript aliases, field locations, document roles, source authority, normalization patterns, and abstention rules for that line of insurance.
The result is a product that gets harder to copy with every schema. Competitors can copy a claim. They cannot instantly copy the labeled corpus, rule history, release behavior, and evidence memory behind the claim.