For the juvenile-dependency appellate attorney working to a deadline
Turn a Record on Appeal into a working case you can cite with confidence.
Other tools read documents. Amicus OS is built for one document: the Record on Appeal. It
takes the box of PDFs the court sends you and turns it into a deadline-ordered list of
your matters, a cited chronology, side-by-side reading, and a drafting outline — then
checks every citation in your brief against the actual record. When it can't verify a
cite, it tells you. It will not make one up.
Six things, each working on your real record today, inside a running deployment.
Your portfolio, by deadline
Every matter ordered by what's due first — the writ due Friday sits above the brief due next month. The clock is part of the case.
A cited chronology
Every event in the record placed in order, each one tied to the verified page:line it came from. Nothing lands on the timeline that can't point to a page.
Read it side by side
Open a transcript and its analysis together. Highlight a passage, attach a note, mark it for review, and tie it to its place on the timeline.
Cite-check against the record
Paste a draft. Amicus OS confirms each record cite resolves to a real page in your record, and flags the ones it can't — it never silently corrects your brief.
A drafting outline
A bar-numbered skeleton that keeps every cited passage attached to its record source. It scaffolds the structure; you write the brief and sign every paragraph.
It refuses to fabricate
When Amicus OS can't ground a statement in a real page of your record, it discards it. It never invents a case, a page, or a holding to fill a gap.
The two things a dependency lawyer can't afford to get wrong
A research platform or a brief-drafting add-in generates an answer and then asks you to
verify it; Amicus OS shows you nothing it can't already prove against your record, so
there's nothing to catch after the fact.
Sealed records never reach a model
A CCT report, a §827 packet, a
§730 evaluation — the material you are legally bound to
protect stays encrypted while it sits at rest, and is never sent to any AI model,
public or private. When an AI assistant is involved at all, the prompt is built inside
your deployment from redacted excerpts and public legal authority; the sealed material
and the minor's identifying details never leave the boundary. No other tool in this
space will tell you where the line is, because no other tool is built knowing a
minor's confidentiality is on it.
Limit, in the same breath
In the default hosted setup, we hold the encryption key for your organization — that
keeps every other firm out of your case, but it does not mean you are the only one who
can ever decrypt it. Keys that only you hold are the on-premises setup, which we have
specified but not yet built.
Every step it takes is on a signed record you can re-check
Amicus OS keeps an append-only, signed log of every step it completes — every cite it
checked, every record it opened, every refusal. If anyone alters that log, the check
refuses to show the rows and tells you it's been broken.
Limit, in the same breath
We call that tamper-evident, not a court-certified chain of custody, and we make no
admissibility claim — but when you need to show your work, the work is there, signed,
in order, and yours to verify.
On security: Amicus OS is built and operated by one person, and we'll tell you
exactly that. We don't carry a SOC 2 report yet, and we won't display a badge we haven't
earned. What we can show you is the architecture — sealed material that never reaches a
model, a signed record you can re-check, and one firm's case that can never reach
another's — and we'll walk you through all of it on the call.
The difference: it would rather refuse than guess.
Other tools treat your record as text to search. Amicus OS treats the Record on Appeal
as the thing itself — a working case you read, cite, and check against. Most tools that
read documents will confidently fill a gap. Amicus OS does the opposite. Every fact it
surfaces has to point to a real page in your record. The ones it can't ground, it throws
away — they never reach your chronology, your draft, or any AI model. Below is a
concrete example: seven statements Amicus OS generated while reading a record, then
discarded, because it could not cite a page for any of them.
A tool that flags the citation it couldn't verify is worth more to you than one that
passes all of them and is wrong about one.
DISCARDED7 statements · no page citation in this record
Statements Amicus OS discarded — no record citation
Statement it generated
Why it was dropped
minor was placed with maternal grandmother
no page
father failed a drug test
no page
mother completed her parenting class
no page
the social worker visited weekly
no page
minor was enrolled in therapy
no page
father attended visitation
no page
mother relapsed
no page
This is an illustration of how the citation-grounding check behaves, run on a
built-out example record (In re T.A.). It is not a live run, and it is not a real
case.
Amicus OS is built for the California juvenile-dependency appellate attorney working a
writ or appeal to a hard deadline — often the only lawyer on the case. It speaks your
vocabulary: Record on Appeal, RT and CT cites,
§366.26, the Table of Authorities, a signed PDF.
It's also for the dependency appellate project or public-defender appellate unit that
wants every attorney on the same citation-grounded footing — the conversation works the
same whether you're solo or a unit.
Another practice area would need its own hearing checklists, issue templates, and indexed
authority, which we have not built — so we are not going to tell you Amicus OS covers a
different docket today.
What it doesn't do — yet, or ever
Doesn't yet — named plainly, never "coming soon"
Full statute and case-law citation resolution is active work, not complete. What it
does today it does out loud: it shows you exactly which cites it could verify and
which it couldn't, instead of passing them all and letting you find out at the
panel. On our 30-citation test fixture, about 70% resolve
against authority we've indexed today. The rest come back flagged, not faked.
A drag-and-drop browser upload isn't built yet — today the record comes in through a
command-line tool, which is why we load your first one with you, on a call, rather
than leave you at a prompt.
Keys that only you hold (on-premises) — specified and ratified, not yet built.
Pattern detection across your own portfolio — queued, not built.
Never — by design
It won't write your brief — it outlines and checks; you write.
It won't watch the docket for you — no automatic court monitoring.
It won't reach another firm's case — no federation, no cross-firm sharing, ever.
No self-serve signup — getting onto a deployment is a conversation.
A vendor that tells you up front what it can't do is a vendor you'll take a call with.
Start a conversation
Tell us who you are and what you're working on, and we'll get back to you to set up a
call. We load your first record with you on that call — you point us at the folder of
PDFs, we bring it in together, and you watch the citation check refuse or resolve on your
own work before anything is bought. This form starts that conversation; it doesn't create
an account or put a record in by itself.