Module 01 · the front door

Capture

Evidence from anyone, anywhere — no app, no surveyor.

Priya has just dented her car. She is standing next to it, upset, with exactly one tool in her hand: her phone. Everything Mimir will ever know about this claim begins in the next three minutes — which is why Capture is the module we obsess over first. If the evidence is bad, every clever model downstream is clever about garbage.

What we're going to build

Multi-channel delivery

One capture request, many doors: a link by SMS, WhatsApp or email; an upload from the dashboard; or a straight API call from the client’s own app. The channel is pack/tenant config, not code.

Guided capture scripts

The pack scripts the session: which angles, which documents, in what order. Priya sees an outline to line her bumper up with — step 3 of 8, left side, hold steady. Scripts are versioned config, so a fleet pack can ask a completely different set of questions.

Capture-quality models

Real-time, on-device-cheap checks before submit: blur, glare, darkness, partial coverage, unreadable pages. A bad shot is rejected in the moment — when the re-take costs Priya five seconds, not a day of back-and-forth.

Consent, first and recorded

Consent copy (pack-supplied, Hindi & English) is shown before anything is collected, and stored with the case as part of the audit trail.

Sessions as first-class objects

Every capture is an ordered session on the case. A fleet client captures at handover and again at return — the compare question ("what changed?") needs sessions to be real objects, not loose files.

Time-boxed, resumable links

Links expire; sessions survive a dropped connection. A claimant on a patchy network must never lose their work.

The contract (platform — never changes)

In: a capture request (who, what script, which channel). Out: validated artifacts in the Evidence Store + a consent record + captured signals on the case. Sold per capture session.

What the pack supplies (per domain)

Capture script (angles, documents, order) · quality thresholds · consent copy · languages · link lifetime.

For engineers & architectsimplementation notes

POST /v1/cases/{id}/capture-link issues a signed, expiring token; the capture web app is a static PWA talking to File Ingest via presigned URLs — no files transit our API servers.
Quality gates run client-side first (cheap heuristics in WASM/JS), server-side second (authoritative) — the server never trusts the client verdict.
Sessions are append-only sub-streams of the case event log; a resumed session replays its state from events, so a dropped connection costs nothing.
Failure modes to design for: expired link mid-session (re-issue, keep session), duplicate submissions (idempotency key per artifact), oversized video (chunked upload + server-side transcode).

Open questions — for the room

Channel order: launch with SMS + WhatsApp, or is email enough for pilot insurers?
Quality models: build thin (blur/glare heuristics) or license a capture SDK for v1?
Video: require the short walkaround from day one, or photos-only for the first pack?
Offline / low-bandwidth mode: how much do we invest for Tier-2/3 India at Phase 1?

← PreviousDecide Next →Extract

Mimir · the Modules intelligence engine — module 01 of 07 · all docs