AiDR

The walk-through

Every feature, shown three ways

A screen as it really is, the steps someone takes on it, and what it is made of — on every page, in that order. Chapters follow the life of a case; the first one is the systems that join ADR to its analysis platform.

Chapter 01

Systems — how ADR and AIOL hold one case together

A case lives in ADR; its analysis in AIOL. Four patterns join them: facts, people, one document, bytes.

01Systems01 / 04

Pattern 01 · Facts

Every change to a case reaches AIOL, in order, exactly once

A transactional outbox announces each case change the moment it is committed — no button, no export, no nightly job.

ONE TRANSACTIONa document is filedits event is writtenOUTBOXseq 1 · dispute.createdseq 2 · document.filedseq 3 · …ONE WORKERsigns · sends in orderretries with backoffpauses on a defectAIOLdedups on event_idA change that rolls back leaves noevent. An event exists exactlywhen the fact does.
01Systems

The chapter in thirty seconds · play, pause, step, full screen

Scene 1 of 7

One case, two platforms

A case lives in ADR. Its analysis lives in AIOL. Two systems, two databases — joined so that neither has to take the other’s word for anything.

0:00 / 0:33

Chapter 02

AIOL on the dispute — the workbench a party crosses into

The other side of “Open in AIOL”: read-only where ADR is the authority, private where a party’s own work begins.

02AIOL on the dispute01 / 07

Feature 01 · The cockpit

The dispute, as AIOL received it

A session born from the record and kept in step with it: stage, timeline, parties, exhibits, warnings — read-only where ADR is the authority.

AIOL case lifecycle cockpit: synced case file banner, stage 4 of 5, procedural timeline, warnings.
02AIOL on the dispute