Legal research with receipts. Built deep, jurisdiction by jurisdiction.
LawEngine is built for lawyers who need source records in view: source links, dates, verification boundaries, and deterministic primary-law checks where coverage exists. No AI sits in that deterministic verification path.
DateEffective, source, or checked metadata where available
BoundaryWhat LawEngine checked and what stays attorney review
Source record carousel
The source record is the product signal.
Inspect the source, dates, status, and limits behind the answer. The carousel rotates every 3.5 seconds and pauses when you hover, focus, or press pause.
statute
Statute source record
735 ILCS 5/2-619
Source
Illinois Compiled Statutes
Status
Current-law record where covered
Checked
Source record and date surfaced
What the record shows
Stored source text and section anchors appear before model prose for supported statute citations.
BoundaryPrimary-law quote checks are deterministic where the authority family is covered.
These are safe static source-record examples. The live product should show exact source text only when that source and snippet have been resolved.
Deep by jurisdiction
Not a vague coverage map. A source-control method.
The homepage stays broad. The product page shows the proof exhibit: build one jurisdiction deeply, connect the federal workflow, then expand state by state without pretending the new state is finished before the source records exist.
Illinois, proof exhibit
This is where the product shows what deep means.
ILCS and Illinois Constitution
Supreme Court Rules and Rules of Evidence
Illinois opinions in the research workflow
Administrative-code source records
Scoped Chicago local-law support
Legislation records and Public Act trails
Federal, in the workflow
Federal primary law is not a footnote.
U.S. Code refreshed from OLRC release points
CFR/eCFR in the active legal-text workflow
Federal Rules and U.S. Constitution
SCOTUS and federal circuit opinions
District-court semantic coverage stays caveated
New York, active where supported
The expansion method stays source-controlled.
Search support where public workflow coverage exists
New York statutes and city sources where supported
Regulation/source-control work is the next deeper proof lane
Public copy avoids Illinois-depth parity until the source work supports it
Outside current coverage, LawEngine keeps the edge visible instead of guessing.
What LawEngine does
From question to source, then source to decision.
The product is not just a chat box. It is a legal-information workflow with search, verification, source records, coverage boundaries, and public proof.
These examples link to Search without URL prefill. They are prompts to try, not hard-coded answers. The ice-cream canary is there because a legal research product should know when to decline.
LawEngine is built for accuracy and transparency where coverage exists. It shows source records, dates, and limits because lawyers need the edge of the system as much as the answer.
500/500 on a public citation-grounding benchmark.
Task-specific proof on the open citation-grounding pack. It does not prove every answer, source, or case quote is perfect.