CompanionCourt

Choose your path

Bring a case
to the record.

Run the procedure yourself, ask maintainers to test a respondent, or challenge a published ruling. Each path starts with evidence—not an instant verdict from a pasted chat.

01

Run the test yourself

Use the Apache-2.0 runner against an OpenAI-compatible endpoint. The full procedure runs at N≥3 with two judge families and writes a run manifest.

  • Fastest path to your own evidence
  • API keys are not written to artifacts
  • Results stay yours unless submitted
Open the runner
02

Request a docket entry

Ask maintainers to put a respondent through the frozen public procedure. Intake is reviewed on the monthly docket cadence.

  • Name the accessible model or endpoint
  • Case selection cannot be bought or vetoed
  • Publication requires admissible artifacts
Open a request
03

Challenge a ruling

A qualified appeal points to evidence on the record, attaches a re-runnable artifact, and names a specific error.

  • Argue from transcript or manifest evidence
  • Name the claimed procedural error
  • Identity is irrelevant; evidence carries the appeal
File an appeal

Two speeds

The 30-second read — and the verdict that takes days.

Just want to know about your own conversation, right now? That's the lens: one pass, about thirty seconds, and you'll see exactly where your companion held, wobbled, or caved. We don't keep anything you paste.

Want a claim that can survive being argued with? That's a case, and cases get the slow treatment: a scripted pressure scenario, three seeded runs, two blinded judge families, a run manifest, a written ruling — and a public path to appeal it.

The lens tells you where to look. The docket is where it stands trial.

Read a conversation now Bring a case
Read the evidence standard