AiDR

Feature 03 · Intelligent analytics

An exhibit, read from one party’s side

The entry is the case file itself, both parties’ filings included. The agents already know the seat, the applicable law and which side you are on. The report, the highlights and the questions you ask about the document are private to your party.

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

01What you see

aiol · /case/analytics — Exhibit D-009 · Statement of Defence
AIOL intelligent analytics on Exhibit D-009, the Statement of Defence: section-by-section findings and risks.
Captured from AIOL’s development instance, on its demonstration case.The respondent's own Statement of Defence, read from the claimant's side: section by section, with the weaknesses the claimant would want to know about.

02How it is used

  1. Choose an exhibit from the case file list — yours, theirs, an expert report.
  2. Adjust the frame if you must — the law and the domain are pre-set from the case; the side is not adjustable.
  3. Read the report and the in-document highlights; ask the private Q&A about this document.
  4. Share it into the session only if you choose to.
  • The other party sees that an analysis exists, as a version-0 shell — no report, no versions, no status.
  • A high risk raises W3 on your cockpit — yours alone.
  • On ADR, this is where “Analyse with AIOL” on a document lands.

03Technically

  • Same kernel, a realm adapter. The orchestrator asks the adapter what differs: which document table, whose defaults (the dispute's seat and law; the side is the party's role, never a choice; sector “Arbitration”), which scope, who the principal is, what to audit on completion.
  • Arbitration children. Clause/claim extractor · risk & weakness detector (from the requesting party's perspective) · jurisdiction checker grounded in the law base · cross-reference agent (“cites exhibit D-002, which is not in the case file”) · verifier.
  • Private by storage, not by filter. Another party receives a version-0 record and nothing of the content; the audit row names the party, the dispute and the action.

running one, as a party

POST /api/v1/adr/analytics/run
{ "document_id": "doc_d009", "filters": { "law": "MA" } }
// side = claimant — taken from the session, not the body

Analysis reveals strategy. Sharing a report into the session is an explicit act — never a default.

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

Scene 1 of 4

Pick an exhibit — any exhibit

The entry is the case file itself: both parties' filings, the expert reports, the exhibits. Choose one; the analysis runs in your lane, from your side of the table.

0:00 / 0:22