AiDR

Feature 04 · The assistant · Search in law

An assistant that knows one dispute and nothing else

It can tell you when the reply is due because ADR synced the step. It cannot cite another dispute, because that index is outside its reach. And what you ask it is yours — encrypted, invisible to the other side, expiring. Search in law opens beside it, already filtered to the seat’s jurisdiction.

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

01What you see

aiol · /case/assistant
AIOL dispute assistant: a conversation bound to case CR/001/26.
Captured from AIOL’s development instance, on its demonstration case. The assistant, inside the session.
aiol · /case/search-in-law — LKB
AIOL search in law for the dispute, seeded with the seat’s jurisdiction.
Search in law, seeded by the seat — sources a drafter can open, not sentences a model produced.

02How it is used

  1. Ask about the case — the timeline, a deadline, a document, what you have already run.
  2. Let it route — “analyse the expert report” opens Analytics with the document preselected.
  3. Search the law — the jurisdiction is pre-set from the seat; adjust it if the terms of reference says otherwise.
  • Your conversations are yours. The respondent sees no trace that they exist.
  • Role-aware. Claimant, respondent, counsel — the framing follows the seat you hold.

03Technically

  • Scope from the context. KernelContext: realm dispute, scope the dispute, principal the party. The chatbot's turn takes its scope from the context and its suggestion store from the caller — one implementation serves both realms.
  • Retrieval boundary. This dispute's document chunks and the law base. Another party's drafts and analyses are not in the namespace at all.
  • Private and expiring. Conversations are per party, messages encrypted at rest, with an expires_at; each turn writes an audit row without the content.
  • Routes, not links. It may offer only the case's own routes — there is nothing else to offer inside the realm.
Fact in an answerWhere it came from
“reply due 3 Aug 2026”the step ADR synced
“Art. 263 DOC”the law base, seeded with the seat
“your analysis of EXP-001”your own work products

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

Scene 1 of 4

Bound to exactly one dispute

The assistant lives inside the session, and the session is one dispute: the cookie names it, every request is checked against it, and there is no "my disputes" to switch to.

0:00 / 0:20