Version three
The compared read
A gap in coverage is a fact about paper. It becomes real when someone says what it costs. So the headline is total uncovered exposure, in dollars, and the discipline is that every dollar in it is provable from the documents.
Designed, not built.
The two provable parts
- Retained exposure. What the insured pays before any coverage responds. The deductible or self-insured retention, read from the declarations and cited to the page it was printed on.
- Gap exposure. Structural holes in the program. The space between one layer’s exhaustion and the next layer’s attachment, and an underlying policy that a schedule names, with a stated limit, that is not in the file.
Both are arithmetic over values the assemble step already produces, and both are citable. No model performs the arithmetic, which is what makes the figure reproducible rather than merely plausible.
Where the dollars stop
This boundary is load bearing, and it is the difference between a credible number and an overclaim.
- Provable from the documents: uncovered structure. Retained dollars below attachment, structural space between layers, a scheduled policy that is absent. These are facts about the program.
- Not provable from the documents: predicted loss. What a claim would actually cost requires exposure data this system does not have and is not being given.
So the claim is that here is your uncovered exposure, proven from your own documents. It is never here is your liability in the sense an actuary would use the word. Claims entered by a user are that user’s facts, carried and displayed as theirs. The system does not forecast.
Where this goes next
Stated as direction, not as plan.
- Work-type attribution. Answering whether a specific scope is uncovered requires reading what endorsements and exclusions do to coverage, which this build does not do and does not pretend to.
- Loss runs ingested rather than typed. The program schema already carries the fields they would fill.
- Read-only connections to document stores. Policy packages are large and moving them is the real friction. If the documents already live somewhere the system can reach, fetch them at the source.
Done when
The design is presented with the narrative, and everything on this page is labeled as designed rather than built.