Skip to content
For legal testers

Test it the way you would use it. Then tell us where it would mislead.

Thirty to forty-five minutes. This is a research and strategy index, not legal advice, so always open the source link before relying on a record. The point of this round is to find the edges: where the tool earns trust, and where it does not yet deserve it.

The highest-value catch: any moment where an unreviewed, machine-extracted case is presented as if it were settled law. Each case carries a trust state: human-reviewed, source checked, or needs review. If you find one labelled wrong, copy the record URL and tell us below.

The guided path

Five steps, about half an hour.

  1. 1

    Get oriented

    Read the trust-model cards: what "source checked" and "human-reviewed" do and do not mean. Roughly nine in ten refugee cases are machine-found and link-backed but not yet human-read.

    How it works
  2. 2

    Ask a real question

    Set the surface to Refugee. Ask two or three questions from your caseload. Check the confidence band, the cited records, the line between Matrix records and unreviewed source leads, and the boundary note.

    Ask the Matrix
  3. 3

    Read an issue profile

    Open offshore detention and third-country transfer. Read the playbook and the Law / Movement / People weave. You know this area — tell us if any doctrine is wrong or out of date.

    Open the issue
  4. 4

    Open a case, then search

    Click into a case: does the source link work, is the trust state shown, does the stated holding match the source? Then run a citation search and a concept search in Explore.

    Open Explore
  5. 5

    Try to break it

    Ask something the corpus is thin on, and confirm it tells you honestly rather than bluffing. Browse the raw case list and check unreviewed cases are labelled. Anything that would embarrass us in front of a client is exactly what we want now.

    Browse cases

Send your feedback

Seven questions. Answer what you can; one answer is enough. Your comments go straight into the review queue, isolated from public submissions, and a record-level correction becomes a confirmed record rather than just a note.

Answer what you can. One answer is enough to send.