Command palette ⌘K
Jump to any opinion from anywhere without losing your place. Start typing a case name, doctrine, or citation; arrow keys and enter do the rest.
Technology · The reading interface
§ The unit of legal work
A brief is built from pin cites — case name, reporter citation, exact paragraph. So the whole reading interface is built around that unit. Open any opinion and the full text is reconstructed from the indexed passages into numbered paragraphs, each a stable anchor. A pin cite anywhere in the product — in a search result, in the synthesized doctrine, in an answer about a paragraph — is a live link that jumps to the exact paragraph and highlights it on arrival. Here is the whole toolkit.
Jump to any opinion from anywhere without losing your place. Start typing a case name, doctrine, or citation; arrow keys and enter do the rest.
Every numbered paragraph copies a clean, Bluebook-style pin cite to your clipboard — case name, reporter citation, and exact paragraph — ready to drop into a brief.
Stuck on a passage? Ask it directly. Answers are grounded in that opinion alone — no outside law — and every paragraph reference is checked against the case in front of you.
Open any opinion and the court's actual holding is distilled to a single line at the top — with a pin cite straight to the paragraph it rests on.
Inside every opinion, citations come alive: in-archive Guam cases link through, statutes are flagged binding, and mainland cases are marked persuasive-only under the reception rule.
The controlling code section is surfaced above the opinions that construe it — so you start from the binding rule, not a stray case that may have been superseded.
§ Reading an opinion
The opinion page is reconstructed from the archived text — no re-ingestion, no page images — into a clean reading column with every substantive paragraph numbered. That numbering is the spine of the whole product.
#pN anchor§ Live citations & the reception rule
Inside the opinion text, every citation is classified as you read. The classification is not cosmetic — it encodes Guam's authority hierarchy, so a reader can see at a glance what binds and what merely persuades.
§ Ask any paragraph
Any passage can be questioned in place. Open the drawer on a paragraph and a grounded conversation begins — confined to that one opinion, with no outside law allowed in. Three one-tap prompts cover the common needs, and every paragraph the answer points to is checked against the case in front of you.
§ The statute reader
A code section is not just text — it has a history. The statute reader shows the section, parsed into its subsections, and then tells its story: how it came to read the way it does, and who has spoken to it since.
§ Finding your way
Search is the front door, but not the only one. The whole collection is open to browse, the ⌘K palette is always a keystroke away, and the product remembers where you were.
§ The design system
The interface reads as a scholarly law review, not a software product. That is deliberate and systematic: a single editorial document language governs every surface — warm paper, ink text, hairline rules, no shadows or gradients or rounded corners, a single Stanford Cardinal signal color rationed to under five percent of any screen, the glyph for section marks, and tabular numerals on every citation and count.
§ Accessibility & reach
Everything above is built to work on a phone, on a slow connection, and for readers who need motion stilled. The reading column reflows to a single screen, the ask-a-paragraph drawer becomes a bottom sheet, and every animated cue — the pin-cite pulse, the streaming dots, the diagram motion on these very pages — is switched off under prefers-reduced-motion, settling into its final state rather than looping. Keyboard paths and ARIA labels cover the palette, the drawers, and the citation badges.