LawOne AI

I built the foundation of a legal-information research platform so users can organize jurisdictions and search with clear source labeling — not legal advice, and not a finished commercial product yet.

In developmentPhases A–H documentedDemo data labeled
A–H
Documented phases
50+
State/territory catalog (Phase H)
6
UI screenshots published
0
Live LLM/Auth claims

Problem solved

Legal research materials are fragmented across jurisdictions. Teams need organized search with honest source labeling.

What I built

A Next.js platform foundation with research UI, search filters, change-monitoring UI, assistant scaffolding, and a national catalog framework — with demonstration data labeled in-product.

Technologies used

Next.js, TypeScript, Tailwind, Vitest, Supabase schema foundations.

Why this matters to an employer

You get someone who can document and ship product foundations carefully — with clear disclaimers, labeled demo data, and no over-claims about live LLM or Auth.

Verified outcome

Phases A–H documented. 6 UI screenshots published. Explicit constraints: no live LLM, no live Auth/Stripe in public claims; catalog ≠ ingested law. Status: in development — not a finished commercial product.

Architecture diagram of LawOne AI system topology

System topology architecture diagram.

Architecture diagram of LawOne AI phases A through H

Documented build phases.