Claims operations at a motor insurer
The question people ask: what is the procedure for this claim, who does it, what does the coverage say, and was that true on the day of the incident?
What feeds the graph: the operations handbook, procedure documents, bulletins that amend them, regulatory notices, and what claims leads say in conversation when a figure changes before the document does.
What the graph holds
| Class | For example |
|---|---|
Policy, Coverage, Endorsement |
Policy P-1001, its collision cover, the endorsement that changed it |
Claim, Incident, Vehicle, Party |
Claim C-5001, the single-vehicle impact it arises from, who filed it |
Role, Procedure, Task |
the claims adjuster, first notice of loss intake, the intake task on C-5001 |
Assessment, Decision, Payment, Recovery |
the repair estimate, coverage confirmed, the indemnity payment, salvage proceeds |
Regulation, Document |
what governs a procedure, and the document each fact cites |
Twenty-seven relations connect them: a claim claims_under a policy and claims_against a coverage, a task follows a procedure and is assigned_to a role, a decision authorizes a payment. Typed attributes hold a claim's state as an enum and an incident's date as a date, and the check refuses a value of the wrong kind.
A cited answer
=== Collision [Coverage] (coverage.collision.v2) ===
status=current · as_of=2026-04-01 · valid_from=2026-04-01 · source_doc=2026-04-01-collision-deductible
Damage to the insured vehicle from impact, subject to a deductible of 750 dollars since 2026-04-01.
Evidence:
- 2026-04-01-collision-deductible statement 1: "The collision deductible went up to 750 dollars on the first of April."
Asked --as-of 2026-03-01, the same question returns the earlier fact with its own source. A regulator's question about a March incident gets the March answer.
How it is used
- The handler opens the explorer and follows a claim from incident to payment, each step with the document that says so.
- The claims lead corrects a figure in conversation; the capture skill makes it a dated source and the pipeline supersedes the old fact.
- An agent answers a handler's question through the query tools, citing the procedure section, and refuses to invent what the graph does not hold.
- Compliance asks what was true on a date, and gets the fact that was current then.
The commands and the skills
oto init --name "Meridian Claims" --ontology auto-claims --project claims
cp ~/docs/claims/* claims/inbox/ && oto ingest --project claims
oto survey --project claims
# the build-knowledge-base skill, or one proposal per document by hand
oto curate apply --project claims --by "<you>" && oto build --project claims
oto serve --project claims --http 8765
Skills: build-knowledge-base, capture, curate, query-knowledge. Tutorials: from a document to a cited answer and a correction made in conversation run on exactly this domain.