For the Head of Field Operations

Your adjuster is standing in the loss, with no signal, and the decision cannot wait for the drive home.

What comes back is a folder of photographs with no context, typed up hours later from memory, and a decision that was really made at the kerbside and reverse-justified at a desk. When that decision is disputed a year on, the part everyone wants — what was seen, in what order, on what authority, and what the customer was told at the door — was never captured in the first place.

One device, three postures, one thread

Foldedone hand

today

The docket. Today’s decisions ranked, swipeable, workable with the phone shut and one hand on a ladder. Each row already carries its verdict state.

designed, not built

Unfoldedtwo panes

thread

dissent

The whole argument, opened. The thread on one pane, the structure of the disagreement on the other — the same view the chair rules from at a desk.

designed, not built

Tabletopfacing the insured

CERTIFICATE

adjuster controls

The certificate turned toward the customer at the door, with the adjuster’s controls on the near half. What was explained is part of the record, not a recollection.

designed, not built

REFUSED

OFFLINE_NO_COMPUTE

There is no signal, so the gate cannot run — and the bench will not tell the adjuster a ruling has been made.

What is captured offline is a signed intent: the adjuster's judgement, the evidence, the time and the authority it was made under, cryptographically bound at the kerbside. It becomes a ruling when it reaches the gate and a named human's authority is checked against it. Selling this as an offline decision would mean either running a weaker gate in the field and calling it the same gate, or letting an unchecked ruling take effect — and we would rather the adjuster know which one they are holding.

the Fold client — designed, not built

SYNC IS A PROOF OBLIGATION, NOT A HOPE

A completed sync emits a receipt that can be checked independently: what was carried, what was accepted, what was rejected and why. Field products in this category advertise offline capture and sync-on-reconnect; what their users complain about is not knowing whether it worked.

[P] Illustration of a designed surface, not a screenshot: the client does not exist yet, and the wireframes above are drawn from the component library rather than captured from a device. The capture rails underneath it do exist — sandbox-first document intake and the three-tier text-recognition cascade are observed at NX/services/nexus-fileprocess/api/src/orchestration/SandboxFirstOrchestrator.ts and NX/services/nexus-graphrag/src/processors/ocr/ocr-cascade.ts.

The mechanism, in three lines

The surface with no incumbent: a folding-phone bench that captures provenance with the artefact, works offline, and treats an offline ruling as a signed intent rather than a ruling.

First

Provenance is captured with the artefact

The photograph, the time, the place, the device and the person are bound together at capture, in isolation, before anything reaches the record. Provenance added afterwards is testimony, not evidence.

Then

The posture changes what is shown, not what is true

Folded is triage, unfolded is the argument, tabletop is the conversation with the customer. All three read and write the same thread — there is no field version of the decision.

Finally

Offline produces intent, not authority

An offline ruling is signed, queued and labelled as an intent until the gate has run and a named human’s authority has been checked. The adjuster always knows which one they are holding.

designed, not built(designed, not built)This is the least built of the nine, and the page leads with that rather than burying it.

0field products in our surveyed set that document a folding-phone posture[D]

4capture methods the field has split into — sketch, photogrammetry, aerial and laser — unified by none of them[D]

sandbox-firstevery captured artefact is processed in isolation before it reaches the record[O]◆

3postures the bench is designed around [P: to be calibrated][P]⧖

The posture count describes a design, [P: to be calibrated] — the client that would render it is not built, and this page shows drawings rather than screenshots.

The first two figures come from our own review of the major field-adjusting products across four app storefronts and their public documentation (accessed 19 August 2026). They are an absence of evidence, not evidence of absence: we found no documented foldable or dual-screen support and no product unifying the four capture methods, which is a statement about what is published, not a claim about what exists. A vendor may have shipped this and not written it down, and we would rather say that than claim a whitespace we cannot verify. The capture rails are our own code, at NX/services/nexus-fileprocess/api/src/orchestration/SandboxFirstOrchestrator.ts.

The honest limit

WHAT THIS DOES NOT DO YET

The Fold client itself.

CAT Simulation Book a 20-min demo Change Control & A2A