One submission, end to end
A submission takes four days to reach a decision, and nobody can say which of those days was the underwriter's.
Nine steps, and two people who need different things from the same record. Read it top to bottom — there is nothing to click.
Two people, one record
The spine
Brian, underwriter
receives, assesses, decides
The parallel track
Michael, broker
submits, then waits
Brian and Michael are illustrative [P]. We have not yet run real underwriters through this, and every stage below names the use cases behind it — a journey that cannot name its use case is fiction.
[P: to be calibrated]illustrative personas, not measured behaviour
Projected target — not yet independently verified.
The nine steps
Plate 01
built and running(shipped)A submission arrives
An email lands with three attachments. They are read where they land, so nobody opens a spreadsheet to retype what a broker already typed once.
- an email, three attachments: proposal form · schedule of values · five years of claims experience
- The receipt Michael gets is hash-chained, so it is not a claim about when the submission arrived — it is a record your own systems cannot contradict.
Michael sees
Michael sees ● received, 11:04. He did not have to ask.
UC003 · UC095
Plate 02
built and running(shipped)What we read, and where we read it
Every field that enters the record arrives with the document it came from, the page it was on, and how sure the reading was. Where the reading is weak it goes to a person rather than being rounded up.
- declared sum insured · proposal.pdf, page 2 · 0.98
- property count · schedule.xlsx, tab S1 · 0.99
- prior losses, three years · experience.pdf, page 1 · 0.61 ⚠ routed to a person
- Nothing enters the record unattributed. You can open the source at the exact page.
Michael sees
Michael sees ● in triage — and if something cannot be read, he is told WHICH page, not "please resubmit".
UC011
Plate 03
built and running(shipped)Is it complete, and do we want it
Completeness and appetite are settled before the work starts. A fast decline is a service, not a failure — it comes back with the appetite reason attached.
- accept · decline · refer — argued by seats that do not share an evidence slice, and ruled by a named human
- The appetite reason travels with the answer, so the next submission can be shaped rather than guessed at.
Michael sees
Michael sees ● declined — and why. A decline that names the appetite reason is worth more to him than a slow maybe.
UC016 · UC021
Plate 04
built and running(shipped)What we pulled in to help
Guidelines, comparable risks, prior submissions and wordings arrive cited and linked back to their source — never presented as something the system remembered.
- guidelines · comparable risks · prior submissions · wordings
- Every external call is logged into the thread with its provenance, so a citation is something you can open rather than something you take on trust.
- Two seats may not argue from the same slice of evidence. Overlapping slices are refused, because agreement between two readers of one document is not corroboration.
Michael sees
Michael sees ● no action needed.
UC025 · UC027
═ control layer ═
Plate 05
built and running(shipped)A control stops it, and says which
Four controls run before anything moves. One of them stops it, names itself, and tells you what would clear it. Nothing moves until it does.
- data quality · passed
- sanctions · passed
- exposure · passed
- completeness · STOPS IT
- It is not a flag you can wave away. The agreement predicate is computed, not learned, and the straight-through lane runs through it too — there is no route around it for the easy ones.
Michael sees
Michael sees ● one thing needed — a named request with what would clear it, filed against the record. Not a phone call. Not a chase. A thing with a name and a next step.
UC019 · UC040
Plate 06
built and running(shipped)You price it. We do not.
What was retrieved and what was generated never share a region of the screen — one is cited and linked to its source, the other is marked as written. You can override anything here, and the override captures your reason.
- WHAT WE RETRIEVED · cited, linked to source
- WHAT WE WROTE · marked as generated
- These two can never share a region.
- The ruling is captured at a durable waitpoint with its reasons, and the reason becomes a number somebody watches.
Michael sees
Michael sees ● terms received. What came back is a decision a person owns, not a number a model produced.
UC028 · UC035
Plate 07
designed, not built(designed, not built)Terms issued
Terms, subjectivities and conditions leave as one record. Where a line sits outside your authority, the referral is a waitpoint with a named approver rather than an email thread.
- terms · subjectivities · conditions
- What is designed and not built is the corridor that carries this into the broker’s own system as a live record. Today the terms leave as a document, and Michael’s "no re-keying" is a design.
Not built yet: A2A migration from the spec version our endpoint conforms to (v0.3.0) to the current one (v1.0.0), plus the party model, claim-state synchronisation and conflict surfacing.
Michael sees
Michael sees ● ready to present. No re-keying — the fields are already his.
UC023 · UC079
Plate 08
built and running(shipped)Bound — and the evidence is already there
A second named human arms the bind, and the evidence for it is already assembled, because it assembled while you worked.
- extracted data · with provenance
- retrieved evidence · with citations
- control results · pass · fail · fix
- approvals · who, and when
- overrides · with the reason
- We call this an evidence bundle. That is a courtroom word, not an insurance one — we borrowed it on purpose. It assembles as you work. Nothing is compiled afterwards, because a set of documents assembled after the fact is a reconstruction, and every regulator knows it.
Michael sees
Michael sees ● bound, with documents — and the customer’s own page goes live the same moment, as a projection of the same log.
UC031 · UC093
═ control layer ═
Plate 09
designed, not built(designed, not built)It keeps watching after you bind
Four things are meant to stay under watch after the decision rather than surface at the annual review: how accurately documents are being read, how often controls fail, how often people override, and where referrals cluster.
- extraction accuracy drift
- control failure rates
- how often people override
- referral patterns
- If underwriters keep overriding the same control, the control is wrong or it is being routed around. Either way somebody should know, so it belongs on a board rather than in a habit.
- The stores and the alert taxonomy are built. Nothing is reading them yet, and an empty watcher renders as an empty watcher.
Not built yet: Drift-detection logic. The alert taxonomy and the stores exist; the detection does not.
Michael sees
Michael sees ● silence, unless something needs him — a subjectivity coming due, a renewal window opening.
UC058 · UC069 · UC098
What is not built yet
2 of these nine steps are designed and not built. They are marked on the plates above rather than in a footnote, because a run of nine ticks is the first thing an experienced buyer disbelieves.
- Plate 07 · Terms issued
A2A migration from the spec version our endpoint conforms to (v0.3.0) to the current one (v1.0.0), plus the party model, claim-state synchronisation and conflict surfacing.
- Plate 09 · It keeps watching after you bind
Drift-detection logic. The alert taxonomy and the stores exist; the detection does not.