It refuses to make something up.
Below is In re T.A. — a built-out example Record on Appeal — taken through the real product step by step, ending on the citation check declining a cite it cannot ground. It is written out rather than filmed: the recording is being re-cut and is not on the site right now. The record is a worked example, not a real client matter. No real client, sealed, or personal material appears anywhere on this site.
What it does on this record
Each step in text, with the limit stated where there is one.
-
1 — The caseload
The firm's matters, grouped by where each one stands — records still being read, an opening brief filed and awaiting the response, briefing done and waiting on the court. Each carries its own deadline, the thing due first on top. Then we open In re T.A.
-
2 — The loaded record
Eighteen volumes of clerk's and reporter's transcript — the full record, spanning eighteen months. The confidential volumes are marked sealed: they show by type and date only. Their contents stay closed. In the app, a Reveal is a deliberate, logged action.
Sealed
-
3 — A mark on the record
At 3 CT 2, the agency's report claims reasonable services were provided. Counsel selects the line and ties a note to the reasonable-services issue.
-
4 — The contradiction
At 3 RT 1, the agency's own witness concedes there was no contact for three months. Same issue, opposite fact — both passages now marked, each note traveling with its page. The record disagreeing with itself, both sides cited.
-
5 — The cited chronology
The record in order, every event tied to the page it came from. Where the record never makes a finding the law requires — the ICWA inquiry here — Amicus OS flags the gap instead of filling it in.
-
6 — Run the citation check
Before filing, counsel pastes the draft and runs a citation check against this case's own record and authority. It checks what's there; it never rewrites the brief.
-
7 — The refusal
The tool declines to write a citation it cannot ground. What that looks like is below, verbatim.
-
8 — Cross-firm isolation
Open another matter — In re R.M. — and you see only its record; the first case never bleeds in. Each firm's records live in that firm's own workspace, kept apart from every other firm's on the same server — cross-firm access is refused at the boundary, not just hidden from view. Sealed records are encrypted at rest and never reach any model; in the default hosted setup the encryption key for your firm is held by us — keys held only by the firm are the on-premises setup, not yet built.
The refusal — the conversion moment
The tool declines to write a citation it cannot ground.
“Match” here means the pinpoint resolves to a real page in this record, and the authority is on file in this case. It is not a misquote check. It is not a good-law or Shepardize check.
In the same breath: about 70% of citations resolve on our 30-citation test fixture. Full statute and case-law resolution doesn't yet.
No AI reaches the verdict.
The citation check returns the refusal and a signed record of every attempt — it never fabricates a pass. Cross-firm access is refused at the boundary, not just hidden from view.
What this walkthrough does not cover: it ends on cross-firm isolation. It does not cover the signed-record verifier re-checking the chain. “It won't obscure” is true and shipped — the verifier refuses to expose a tampered record, and you can re-check the whole chain — but this page doesn't prove that, and we won't present something as shown when it isn't. See the Reference for that guarantee, stated from the code.
It refuses to make something up, and says so plainly. If that's the bar you hold your tools to, that's worth a conversation.