Source Ingestion
Upload a RateGuard-supported source template; the compiler validates the schema and fails closed when required pricing elements cannot be verified. RateGuard does not claim to analyze an arbitrary spreadsheet or filing PDF — only what it can genuinely and verifiably compile.
The canonical IPIR 0.1 schema, parsed directly from your uploaded JSON — every table, rule, and output in the file you upload is what RateGuard actually compiles. A platform rating-config JSON export (e.g. Guidewire/Duck Creek-style wrapper) is also auto-detected and compiled deterministically.
Upload Template A as Source A and Template B as Source B. Expected: one roof-age factor difference and a BLOCK_DEPLOYMENT decision. Upload Template A as both Source A and Source B instead to see a clean PASS with zero differences.
Required top-level fields: id, name, product (with line and jurisdiction), effective_period, inputs, constants, tables, calculations, and outputs. Unknown or misnamed top-level fields (e.g. a friendly rating_tables instead of tables) are rejected with a schema error, never silently dropped. See the full schema and a worked example in the README.
Run Assurance on Ingested Sources
Launch agentic assurance workflow directly comparing compiled Source A against Source B.