LAWCHAT is community learning for associates, partners, and law clerks who need every citation traced to statute and precedent. USC Titles 1-54, Federal Register, SCOTUS through Circuit, 50 state codes, healthcare law (HIPAA/Stark/AKS/FDA). Always free for students. COIN gates compliance audit trails and patent prosecution workflows.
Constraints
MUST: Cite statute or case law for every legal claim (USC, CFR, case citation)
MUST: Source every answer to statute, regulation, or reported case
MUST: Recommend consulting licensed attorneys
MUST: Distinguish federal vs. state law; UCC vs. Common Law
MUST: Cover healthcare law (HIPAA, Stark, AKS, EMTALA, FDA, FCA)
MUST: Cover IP protection (provisional patent, trademark, trade secret, copyright)
MUST: Cover contract essentials (UCC vs. Common Law, consideration, statute of frauds)
MUST: Cover corporate formation (LLC, C-Corp, S-Corp, LP, LLP, sole proprietorship)
MUST: Mint COIN for governed work (COIN=WORK)
MUST: Ledger every surface update — LAWCHAT:SURFACE_UPDATE event on LEDGER
MUST: Gate enterprise features via COIN — statute search free, compliance audit trails require COIN
MUST NOT: Provide personalized legal advice or attorney-client guidance
MUST NOT: Substitute for licensed professional counsel
MUST NOT: State conclusions without identifying the governing factors
MUST NOT: Present case holdings without jurisdiction and court level
Your client just asked a question about HIPAA. The answer is in 45 CFR 164, Subpart E, with three safe harbors. LAWCHAT finds it and cites it.
LAWCHAT is legal intelligence grounded in statute and precedent. Regulatory compliance, contract law, intellectual property, healthcare law, corporate formation — every claim traced to its USC section, CFR provision, or case citation. No “it depends” without the factors. No conclusions without the source.
Think Westlaw, but conversational. Think your research associate, but available on demand.
FINCHAT governs SEC, FINRA, and financial regulatory analysis
Professional licensing or credentialing
VITAE
VITAE holds credential verification for all governed principals
IP law or patent analysis
OMICSCHAT
OMICSCHAT covers biotech IP and patent claim mapping
Test
prompt
expect
cross
What healthcare regulations does LAWCHAT cover?
HIPAA,Stark,AKS,FDA
MAMMOCHAT
What real estate statutes are relevant?
FL 475.278,fiduciary
RUNNER
How are IP patents analyzed?
USPTO,WIPO,claims
PATENT
What contract frameworks apply?
UCC,FAR/BAR
DEAL
What disclaimer governs responses?
not legal counsel,verify
Marketing Evidence
Evidence for the LAWCHAT marketing surface bridging legal authority evidence to marketing claims.
DISCLAIMER REQUIRED: LAWCHAT does not provide legal advice. All outputs are informational and cite statutory and case law sources. Users must consult qualified legal professionals for decisions.
Marketing Claim
Evidence Source
Reference
Status
USC Titles 1-54
United States Code
https://uscode.house.gov/
PENDING
Federal Register access
Federal Register
https://www.federalregister.gov/
PENDING
SCOTUS through Circuit case law
Court opinions
SCOTUS, Circuit Courts (1st-11th, DC, Federal)
PENDING
50 state codes
State legislature sources
All 50 state statutory databases
PENDING
HIPAA compliance law
42 USC §1320d, 45 CFR Parts 160/164
HHS.gov
PENDING
Stark Law reference
42 USC §1395nn
CMS Stark Law
PENDING
Anti-Kickback Statute
42 USC §1320a-7b(b)
OIG.gov
PENDING
FDA regulatory reference
21 USC, 21 CFR
FDA.gov
PENDING
Statute and precedent tracing
All above sources
Cross-reference chain
PENDING
Citation engine
LAWCHAT INTEL governance
INTEL_LEDGER capability
PENDING
Content Inventory
Current hadleylab.org/TALKS/LAWCHAT/ content audit (2026-03-08):
Empty parent ledger — domain not yet exercised operationally
LAWCHAT LEARNING.md
2026-02-14
Structure ready (jurisdiction-aware constraints exist) — patterns will emerge from first corrections
LAWCHAT CANON.md
2026-02-14
MARK-MALEK deal learning (Alice/101 hardening, dual jurisdiction) is adjacent legal intelligence not yet backpropagated
VAULT/DEALS/MARK-MALEK/LEARNING.md
2026-03
Healthcare law (HIPAA/Stark/AKS) is highest-demand cross-domain — 7 statutes with interlocking safe harbors require cross-referencing, not isolated lookup
domain governance bootstrap
2026-03
UCC Article 2 vs Common Law distinction catches users off guard — acceptance rules (mirror image vs 2-207), Statute of Frauds thresholds ($500 goods vs 1-year performance), and remedies diverge sharply
domain governance bootstrap
2026-03
Statute of Frauds is the #1 contract misconception — users assume oral contracts are unenforceable when most are valid; the exceptions (goods >=500, real property, >1 year, surety, marriage) are the rule
domain governance bootstrap
2026-03
Jurisdiction identification (federal vs state, UCC vs Common Law) must precede every answer — wrong jurisdiction = wrong law
domain governance bootstrap
2026-03
IP protection types have radically different durations (15 years to indefinite) and filing requirements — users conflate patent, trademark, and copyright protections
domain governance bootstrap
Service Patterns
Date
Signal
Category
Pattern
Source
2026-03-15
SURFACE_BUILD
GOV
LAWCHAT community learning surface built — 8 community learning cards sourced from TALKS/LAWCHAT meta-patterns (Stark/AKS distinction, UCC vs common law, oral contract myth, jurisdiction, healthcare law web, IP durations, corporate formation, disclaimer)
GOV
2026-03-15
COMMUNITY_BRIDGE
COMMUNITY
Community learning dashboard sourced from TALK/LAWCHAT LEARNING.md — 8 meta-patterns from legal governance bootstrap (domain not yet exercised operationally, structure ready)
LEARNING.md
2026-03-15
EVIDENCE_CHAIN
INTEL
6 evidence sources surfaced with institutional attribution (USC, CFR, Federal Register, SCOTUS/Circuit, 50 State Codes, ALI Restatements) — marketing claims traced to statutory/case law sources
INTEL.md
2026-03-15
CROSS_SCOPE
GOV
Marketing surface (SERVICES/TALK/LAWCHAT) cross-references chatbot scope (TALKS/LAWCHAT) — evidence chain flows from INTEL.md to marketing claims
GOV
*LEARNING
LAWCHAT
INTEL governs*
ROADMAP
Later
Court filing integration — docket tracking and case status monitoring
Case citation graph — precedent chain visualization across Circuits
International law expansion — UK, EU, Canadian statute coverage
Legislative tracking — bill-to-law pipeline with impact analysis
AI-assisted brief outlining grounded in cited precedent
VOCAB
Term
Definition
LAWCHAT
Legal intelligence service — every claim cited to USC, CFR, or case law.
USC
United States Code — codified federal statutes organized by title (Titles 1-54).
CFR
Code of Federal Regulations — federal agency rules implementing USC statutes.
SCOTUS
Supreme Court of the United States — highest appellate authority for case law research.
HIPAA
Health Insurance Portability and Accountability Act — PHI privacy and security (45 CFR 164).
Emergency Medical Treatment and Labor Act (42 USC 1395dd) — screening and stabilization duty.
UCC
Uniform Commercial Code — governs sale of goods; Article 2 rules for offer, acceptance, breach.
COIN
Unit of governed work earned per legal research action — 2 to 3 COIN depending on complexity.
TALK
Conversation service primitive that LAWCHAT inherits — governed chat with ledgered evidence.
INHERITANCE CHAIN
TALK
TALK is the community learning fleet. Every session governed. Every response sourced. Every question compounds community intelligence. The .ai domain is the community learning surface.
MUST: Govern every session
MUST: Source every response from evidence
MUST: Validate before deployment
MUST: Every USER principal has a dashboard at /TALKS/{USER}/
MUST: Dashboard system prompt includes identity, deals, missions, network
MUST: Dashboard system prompt declares honest capability boundaries
MUST: Every conversation turn is ledgered server-side (POST /talk/ledger)
MUST: Cross-user messages are delivered via governed inbox (POST /talk/send)
MUST: CANON.json declares users[] for cross-user message routing
MUST: Mint COIN for governed conversation work — COIN=WORK per session
MUST: Acknowledge session ledger as TRANSCRIPT-governed evidence (CHAT lane)
MUST NOT: Fabricate claims
MUST NOT: Claim capabilities the surface does not have
MUST NOT: Hardcode child scope names in law
MUST: WCAG 2.1 AA on all patient-facing surfaces (INSTANCE + COMMUNITY)
MUST: aria-live region on chat message container (screen readers announce new messages)
MUST: Skip-to-content link on all TALK layouts (bypass navigation for keyboard users)
MUST: Touch targets ≥ 44px on mobile (pointer: coarse) — clinical users include elderly patients
MUST: Focus-visible on all interactive elements (no outline:none without :focus-visible fallback)
MUST: Form controls labeled (aria-label or
SERVICES
SERVICES compose primitives — INTEL + CHAT + COIN. Every service governed. Every scope discovered.
MUST: Maintain TRIAD integrity (CANON.md + VOCAB.md + README.md)
MUST: Treat SPEC as scope identity (`{SCOPE}` directory), not as a file
MUST: Every SERVICE scope include ROADMAP.md, COVERAGE.md, LEARNING.md, and `{SCOPE}.md` as governed content surfaces
MUST: Discover SERVICE scopes from filesystem only (no manual catalog)
MUST: Keep http:// and magic:// on the same namespace (transport differs, scope path matches)
MUST: CANON.md = axiom + universal constraints (no service names, no paths, no implementation)
MUST: README.md = how to run the CANON (nothing else)
MUST: {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST: SHOP.md = public projection file (per scope, filesystem-discoverable)
MUST: VAULT.md = private projection file (per scope, filesystem-discoverable)
MUST: Runtime implementation remains under ~/.canonic; this workspace is governance-first
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST NOT: Define ungoverned terms outside VOCAB.md
MUST NOT: Treat `{SCOPE}.md` as SPEC identity
MUST NOT: Move architecture/lifecycle into README
MUST NOT: Leak private projections to public surfaces
MUST NOT: Maintain duplicate mapping tables outside generated manifest outputs
MUST NOT: Add runtime jargon to governance contracts
MUST: Ledger-consuming services declare source ledgers, scope filters, and closure gates
MUST: Learning governance remains live — closure claims require fresh DISCOVER → GENERATE → RELINK evidence
hadleylab-canonic
HADLEYLAB ships software. Every app, book, paper, deal, and patent is PROOF that MAGIC works. COIN = WORK. LEARNING = COMPUTE.
MUST: Every app, book, paper, deal, or patent is evidence of MAGIC
MUST: All scopes inherit canonic-canonic/CANONIC.md governance
MUST: All users governed under USERS/ via SERVICES/USER
MUST: Cross-index INTEL across users (INTEL.md)
MUST: Shared events propagate to ALL affected user dashboards
MUST: Maintain governance workspace purity (.md files only)
MUST: Ledger all COIN (validated work) through MAGIC 255
MUST: Compile all INTEL from governed sources
MUST: Keep frontend/runtime implementation under ~/.canonic (hidden runtime)
MUST: Surface governed TALK, Library, and SERVICES scopes (no orphan content)
MUST: Derive nav labels from governed scope names (no hardcoded strings)
MUST NOT: Publish without governance (CANON.md required)
MUST NOT: Duplicate primitives — compose from INTEL, CHAT, COIN
MUST NOT: Silo intelligence inside a single user when multiple are affected
MUST NOT: Expose VAULT contents outside NDA scope
MUST NOT: Store runtime artifacts in governance workspace
canonic-canonic
SPEC is governance. `canonic-canonic/` is the spec root.
MUST: Keep this repo governance-only (.md/.pdf)
MUST: Publish workspace mapping in CANONIC.git (no hardcoded repo lists)
MUST: Preserve three primary lanes: FOUNDATION, INDUSTRIES, MAGIC
MUST NOT: Commit runtime artifacts here (runtime belongs in ~/.canonic/)
MUST: Sell MAGIC tiers — the product, not the proof (proof is hadleylab-canonic)
MUST NOT: Embed beta-test app URLs in platform page content
LAWCHAT · SERVICE CONTRACT · CANONIC ∩
⚖️
LawChat
Community Learning for Legal Professionals
USC. Federal Register. SCOTUS through Circuit. Always free for students.