Methodology
How the intelligence works
The rule is simple in principle and strict in practice: retrieve from primary sources, verify the authority path, audit the filing risk, and hold external action behind review gates.
9,427,210
Court opinions on record
1,900,000+
Primary-source passages
18,124,047
Citation references
87,085
Cross-references
Verification spine
Retrieved and verified from primary sources
The hosted workspace keeps legal work close to the record. It does not treat fluent text as authority. The source path, treatment status, forum fit, and filing posture remain visible until the work is ready for review.
Retrieve
Primary sources first
It opens the statute, the court rule and the opinion themselves — along with what your own file already holds — before it will assert anything.
Verify
Six questions about every citation
Does the case exist. Does it actually say the words it is quoted for. Does it fit the point being made. Has it been overruled since. Does it bind your court. And is anything still unresolved.
Audit
Read before you file
The right court, standing, proof of service, the format that court demands, every citation, every exhibit — and whether anything is missing.
Approve
Nothing leaves silently
Research moves as fast as you do. Anything served, filed, or sent to a client stops and waits for a person to approve it.
The engine
Research architecture behind the workspace
Some layers are visible in the hosted product today. Others are engine-side methodology that powers retrieval, doctrine mapping, and gap research. Public claims are separated accordingly.
Complete source retrieval
The engine combines passage search, citation-chain search, holdings, maxims, documents, parties, facts, and evidence into one research path.
Doctrine maps under review
Primary sources expand doctrine maps over time. New understanding is promoted only through controlled research and verification paths.
Matter record graph
Matter facts, evidence, entities, authorities, and procedural posture are represented as a graph so legal conclusions can be traced back to their factual and legal anchors.
Forum-aware authority
Authority is weighted by court, jurisdiction, treatment, and procedural context. A strong source in one forum may be weak or inapposite in another.
Strategic research without overclaiming
Research may study judge, forum, and doctrine patterns. The hosted platform presents those ideas as methodology unless a specific workflow is verified in the product.
Gap research queue
When authority is missing, conflicting, or unsupported, the engine queues the gap for research instead of filling it with unsupported language.
The disciplines
Built to refuse, not merely to produce
A system that can only generate will hand you a finished document and tell you nothing about whether it survives. These are the standards the engine holds itself to on every matter it touches. They are stated here; how each is implemented is not.
A summary is not a reading
No headnote, search result, digest or model recollection is treated as having read a case. An authority reaches your paper only after its full text has been read and recorded. Where a source cannot be reached, it is marked unreached and cited by no one.
Every answer carries its coverage
A result is never a bare value: it states what was searched and what was not. An empty search returns unknown, never "nothing found", and no clean verdict may stand beside an unfinished one. The distinction between we looked and found nothing and we did not finish looking is enforced where the record is written, not left to judgement.
The argument is tested against what defeats it
A separate pass searches for the authority that ends the proposition, in the language courts use when they refuse. Retrieval tuned to find agreement will find agreement; the adverse pass is required, and what it surfaces is dispositioned by a person rather than cleared by the tool.
The forum decides the form
Requirements that look interchangeable are not. A verification one court prescribes is defective in the next, and the difference is a returned paper. Every instrument is measured against the rule of the court it is going to, read from that rule’s own text.
The engine is permitted to refuse
A finished paper is measured on the page the way it will be measured at the counter. A draft that fails does not leave, and an examination that could not complete is never recorded as an examination that passed. A system that can only produce cannot protect you.
Nothing is trusted until it is proven
Every safeguard ships only after it has been proven against the defect it exists to catch, on material it was not built from. Passing is not evidence that a check works; catching is.
1,003
safeguards standing behind the engine
884
proven against the defect each exists to catch
613
proven on material that was complete, well-formed and incorrect
The matter
A case is a record, not a folder of documents
Research is the visible half. The rest is holding a matter so that every assertion has a source behind it, every date sits on one chronology, and the work owed next is known before a deadline discovers it for you.
The matter, held whole
Papers, evidence, service, governing law and every date in one record, with the work that needs a decision named in a sentence rather than buried in a folder.
Fact to source, or not at all
Every factual assertion resolves to a primary source — an exhibit under a cryptographic digest, a message identifier, a court record. An assertion with no source behind it is marked as such and does not enter a draft unremarked.
One record of what happened
Filings, service, correspondence, rulings and deadlines land on a single chronology as they occur, anchored to the evidence that proves each one. A filing does not pass without its event on that record.
Parties and their connections
People, entities and the relationships between them are held across matters, not inside one. A fact established in one proceeding is visible from every other — which is precisely what a per-matter filing system can never do.
Discovery, in both directions
What may be demanded, and what is owed when discovery is served on you — the side where a missed step is irreversible. Response clocks, the form an objection must take to survive, what withholding requires and what is waived by silence differ by forum, and are read from each forum’s own rules rather than generalised from one.
Exhibits that survive scrutiny
Each exhibit is hashed at collection, numbered, its custody recorded, and checked against the index the brief actually cites — so the page a court is sent to is the page that is there.
Discovery is carried for 7 forums on both sides, each read from that forum’s own rules — including 4 in which party-to-party discovery is not available as of right, a fact the engine states rather than drafting a request that cannot be made.
None of this was designed in advance of use. It runs on live litigation, and every standard above exists because the work demanded it.
Verified now
Capability claims stay inside the evidence
These capabilities are safe to feature because they are backed by code paths, public constants, or implemented workflow surfaces.
- 1,900,000+ primary-source passages and 9,427,210 court opinions on record
- 1,178 maxims of equity and 16 doctrine argument chains traced to their sources
- 18,124,047 citation references and 87,085 cross-references
- Citation verification, quote checks, good-law review, and negative-treatment signals
- 100-point filing audit for jurisdiction, standing, service, formatting, citations, and completeness
- Court-agnostic filing-ready DOCX/PDF packets with exhibits and approval gates
- Assisted electronic submission for supported portals: federal CM/ECF and New York NYSCEF; certified-mail fallback elsewhere
Research boundary
Published research is not repackaged as platform capability
LAW publishes research in public corpus theory, doctrine mapping, and structural legal analysis. Those papers may report experimental measurements. The product does not present those measurements as guaranteed outcomes, litigation predictions, or automatic filing power.
Published research stays separate
Doctrine-cluster experiments, pre-consensus signal studies, dormant rights research, and manufactured precedent maps stay in the research series unless a hosted workflow separately proves the behavior.
Platform claims stay evidence-backed
Public capability language is limited to the corpus, verification spine, filing packet workflows, review gates, and supported e-submission portals that are backed by this codebase.
Outputs remain review-gated
Research notes, drafts, citations, and packets are retrieved and verified from primary sources - not treated as final authority - and remain subject to user and professional review.
Institution-grade control
Fast research, slow release, visible authority
LAW can accelerate retrieval, mapping, drafting, and audit preparation. It does not remove the duty to verify. It keeps the source record, review state, and filing authorization in the workflow so unsupported work is stopped before it leaves the workspace.