Insurance schema packs
Each supported line has document profiles, field contracts, normalization rules, evidence expectations, conflict states, export mapping, and benchmark requirements.
FastScript
Control Layer
LLMs made documents readable. FastScript makes insurance documents reliable.
FastScript is the control system inside PolDex. It turns model reads into schema-bound, evidence-backed insurance data with conflicts, abstention, validation, exports, and stable API behavior.
The moat is not one prompt or one model. The moat is the growing insurance control layer: schema packs, evidence discipline, conflict logic, benchmark corpora, and delivery rails that compound across every document family PolDex supports.
Why It Exists
Models read documents. FastScript decides what becomes system truth.
Insurance extraction cannot stop at text. Policy data needs source authority, line-specific field contracts, missing-value handling, conflict handling, and audit-ready evidence.
Evidence normalizer
FastScript converts raw model reads into cited facts with page, form, section, source text, confidence, and provenance so downstream systems can audit every important value.
Conflict graph
Insurance documents disagree. Declarations, COIs, endorsements, schedules, and requirements packets can all state different versions of a fact. FastScript keeps the disagreement visible instead of flattening it away.
Adjudication rules
Line-specific rules decide when a value is accepted, when it is unresolved, when evidence is too weak, and when a human or downstream system should review the output.
Provider abstraction
Foundation models are readers inside the system, not the customer-facing contract. FastScript keeps provider routing internal so PolDex can improve models without changing customer output shape.
Benchmark gate
New schemas and major behavior changes are tied to corpus targets, required-field scoring, evidence checks, and a release gate before accuracy claims are made publicly.
Owned Assets
The part competitors cannot replace with a model switch.
A competitor can call the same foundation models. They still need insurance-specific schemas, adjudication, evidence design, benchmark material, operational rails, and years of production edge cases.
| Asset | Why it compounds |
|---|---|
| Schema memory | Every supported line adds PolDex-owned field definitions, document profiles, extraction states, and export contracts. |
| Evidence discipline | The engine is trained to preserve what supported a fact, not just the fact itself. |
| Insurance conflict logic | Coverage truth is often conditional. FastScript represents conflicts, unresolved values, and authority differences explicitly. |
| Operational rails | Credits, estimates, webhooks, batch states, signed artifacts, and connector events all sit around the same controlled output. |
| Benchmark corpus | Each schema family accumulates public and private evaluation material that makes behavior harder to copy over time. |
| Interface reuse | API, processor, MCP, CLI, proof, playground, intake, email intake, and connectors all call the same contract. |
Execution Path
The extraction path stays stable while the reader layer improves.
Customer-facing behavior is controlled by FastScript. Underlying model routing can change without changing the API, processor, CLI, MCP, or export contracts.
01
Classify
Identify schema fit, document profile, source type, page structure, and whether the input belongs to a live or future insurance family.
02
Read
Use model readers to extract candidate facts, spans, tables, clauses, schedules, and endorsement signals.
03
Normalize
Map candidates into canonical field names, money/date/entity formats, truth states, and evidence records.
04
Adjudicate
Resolve supported values, preserve conflicts, abstain when evidence is weak, and mark unresolved fields without guessing.
05
Package
Return stable JSON and derive CSV, XLSX, ZIP, webhooks, signed links, connector events, and agent artifacts from the same truth source.
Output Contract
One controlled result powers every PolDex surface.
Same truth source
API, processor, playground, live proof, intake links, email intake, MCP, CLI, webhooks, and connector events all consume the same FastScript-controlled output contract.
Same artifact set
JSON is the source of truth. CSV, XLSX, ZIP files, signed links, and connector payloads are derived from that same result instead of being separately interpreted.
Same safety posture
Estimates, held credits, completed jobs, failed jobs, retries, deletion, and exports sit around the same controlled extraction behavior.
Boundary
What FastScript is not.
Raw LLM output
FastScript does not expose raw completion text as the product.
Generic OCR
FastScript assumes text extraction is only the first step; insurance truth comes from schema and evidence control.
Workflow lock-in
FastScript sits under API and processor surfaces. Customers keep their own AMS, CRM, spreadsheet, agent, or workflow tool.
One-off prompt
The behavior is versioned, benchmarked, and routed through reusable schema contracts instead of ad hoc prompts.
FastScript is the compounding part of PolDex.
Every schema, benchmark, customer document family, conflict rule, and evidence pattern strengthens the control layer behind the public API.