AiDR

Feature 07 · The predictive engine

One estimate, the same for both parties, hidden from the tribunal

The report rests on the record — the exhibits from the sync, the timeline, the facts, comparable passages from the law base — and only that. Every citation is verified against its source; confidence is measured, not declared. Both parties see the same report. The tribunal sees none of it.

  1. 01 · What you see
  2. 02 · How it is used
  3. 03 · Technically
  4. 04 · The explainer

01What you see

aiol · /case/predictive — Report v3 · run at Pleadings
AIOL predictive engine report v3: party assessment with probabilities, strengths, weaknesses and the confidence index.
Captured from AIOL’s development instance, on its demonstration case. Version 3, flagged stale because a new expert report was filed since; the banner states the rule: symmetric, and the tribunal does not have access.

02How it is used

  1. Open it — the first open runs version 1 on the record as it stands.
  2. Read both sides — probability and range per party, strengths, weaknesses, gaps, precedents with their relevance.
  3. Watch for “stale” — an exhibit added or a stage moved marks the report stale and raises W4.
  4. Re-run — the next version joins the evolution chart; earlier ones stay readable.
  • From ADR, “Case Prediction · Predictive Engine” opens this screen.
  • Not advice, not a decision — the disclaimer travels with the report.

03Technically

  • One report per dispute. dispute_predictions: the same for every party — the open decision in the design resolved for symmetry — and a 403 for the arbitrator; nothing of it in the tribunal's cockpit.
  • Inputs are the record, only. Exhibits from the sync (never scratch files — the report is shared, and would leak them), the timeline, the facts, comparable passages from the law base.
  • Verified, then scored. One model call; the verifier keeps a citation only if its quote is in the cited source; the confidence index derives from record completeness, precedents found and citations verified.
  • Immutable versions. Each stamped with the stage and the record it saw; a record event since marks it stale on read.

the version series — the evolution chart

v1 · Appointment      · 58 %
v2 · Terms of reference · 64 %
v3 · Pleadings        · 68 %   stale — EXP-001 filed since

as the arbitrator

GET /api/v1/adr/prediction
403  · the tribunal keeps full command of its decision

04The explainer · play, pause, step, full screen

Scene 1 of 4

What the estimate rests on — and only that

The record: the exhibits from the sync, the timeline, the dispute's facts, and comparable passages from the law base. Never a party's scratch files — the report is shared, and would leak them to the other side.

0:00 / 0:22