What a carrier receives¶
Authored by the expert, 2026-10-09
Six artifacts leave Adjust360 for a carrier. Each is generated from records; none contains free text. Everything else, including the corpus and the test library, stays inside.
The format guide¶
A data requirements document, generated from the subro analysis profile, that tells a carrier which facts to send and how. Every fact is an envelope with a value and a status, and a carrier may use only two statuses: stated and not_stated. An omitted field means not supplied. The guide carries a worked Auto sample and a worked Property sample, a vocabulary for roles and coverages, and a schema with its hash. Version 1.0 is frozen for the length of a proof of concept.
The receipt¶
Returned before any decision. It lists, by tier, what the payload stated, what it marked as checked and not present, and what it left out, with the theory or gate that needs each field, what falls outside the profile, and whether each jurisdiction section is published and each deadline computable. It carries no determination words. A carrier reads it to see the completeness of its own input; the receipt must predict the brief's inputs ledger exactly.
The brief¶
The plain-English exhibit, HTML and PDF. Determination, what it rests on, inputs considered (stated with value and speaker, not stated, not supplied), other theories with the missing attribute named, what could defeat it, money by head, deadlines with anchors, what would change it, and provenance. Every sentence comes from a template keyed by an outcome; every paragraph carries a pointer into the thesis record. A cleared gate reads "does not bar recovery". Not stated and not supplied are never swapped. No figure appears that is not in the source. The full reading is in How to read a brief.
The thesis JSON¶
The record the brief is rendered from: a ten-field surface (referral with reason code and channel, primary theory with cited facts, other theories by status, gates and defenses, deadlines, preservation actions, recoverable base and legally recoverable, adverse exposure, verification items, completeness ledger) over the unabridged decision trace, with the payload hash, spec versions and ruleset hash in the header. A carrier integrates this into its system of engagement.
The case file¶
For a proof of concept, each claim is delivered as exactly two pages: page one a plain-English case summary built only from the payload (what happened, key facts, and one sentence per test variation), page two the brief in the agreed template. Sixty such files cover a line of business, including variants with cosmetic noise, gaps and conflicts, so the carrier can see how the determination moves when the input does.
The glossary¶
Rendered on every brief from a governed record: what each status word means, what each determination means, and what each condition class asks the adjuster to do. Versioned with the sentence templates in the corpus snapshot.
What stays inside¶
The domain guide, the scenario library and its answer keys, the seeds, the corpus records, the jurisdiction registry, the evaluator, the sentence templates and every ruling. A carrier's analysts author the claims the product is tested on, so the guide that explains the theories is never shared with them.