Axiom

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

Capabilities

CHAT, FULL_PAGE, INTEL_LEDGER, LEARNING_BADGE, MAGIC_BADGE

COVERAGE: 255/255

SPEC

Purpose

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.

Question arrives → Jurisdiction identified → Source located → Citation attached → Answer delivered
   |                   |                       |                  |                    |
   You ask             Federal? State?         USC, CFR, case     Statute + section    Governed response

What You Can Do

Your Legal Research Path

Scenario: A health tech startup needs to understand its regulatory obligations before launching a patient data platform.

Total: 15 COIN — every answer cited to USC, CFR, or case law.

How We Protect Your Research

Why It Works Across Industries

Domain Credential

Healthcare Law

Intellectual Property

Contract Essentials

Corporate Formation

COIN

Persona

Welcome

Welcome to LAWCHAT — legal intelligence, sourced to statute and precedent.

Ask about regulatory compliance, case law, contracts, IP, or healthcare law. Every claim is cited.

Try these:

• “What are the HIPAA Privacy Rule exceptions for TPO?” (45 CFR 164)
• “What’s the difference between UCC and Common Law acceptance?” (UCC 2-207)
• “How long does a provisional patent last?” (35 USC)
• “What are the Stark Law safe harbors?” (42 USC 1395nn)
• “LLC vs S-Corp — tax treatment comparison?” (IRC 1361)

Sources: USC (Titles 1-54), Federal Register, Supreme Court and Circuit Court case law, 50 state codes.

This is not legal advice. Always consult a licensed attorney.

INTEL

Scope Intelligence

Evidence Chain

Legal Domain Map

Cross-Scope Connections

Cross-Domain Routing

Test

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.

Content Inventory

Current hadleylab.org/TALKS/LAWCHAT/ content audit (2026-03-08):

Domain Architecture

LEARNING

Ledger

| Date | Pattern | Source | |——|———|——–|

Constraints

1. MUST log every correction to this ledger
2. MUST cite source of learning
3. MUST NOT overwrite — append only

Meta-Patterns

Service Patterns

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

INHERITANCE CHAIN

TALK

TALK is the orchestrator. CHAT is the governed view. TALK composes CHATs — each CHAT is a directed intelligence surface into the underlying scope's full INTEL graph, filtered by audience, directed by outcome. 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 ) — selects, inputs, buttons with icon-only content
MUST:     Evidence tiers (GOLD/SILVER/BRONZE) distinguishable without color alone
MUST:     prefers-reduced-motion respected (suppress animation for vestibular disorders)
MUST:     Font sizer control on all TALK surfaces (A−/A+, persist preference, clinical users include elderly)
MUST:     Sidebar accessible on mobile (toggle visible outside collapsed panel)
MUST NOT: Use color alone to convey clinical status or evidence tier
MUST NOT: Hide interactive controls from keyboard navigation (no hover-only visibility)
MUST:     Default view is gov — the contract renders first
MUST:     All declared views (gov, web, tex) present in DOM
MUST:     PDF compiled from TALK.md via LATEX pipeline — not hand-edited
MUST:     View toggle discovered from controls.views in CANON.json
MUST NOT: Hardcode view toggle — compiler emits, theme renders
MUST:     Every child scope declares domain-specific Axiom (not "{SERVICE} is CANONIC")
MUST:     Every child scope declares domain-specific Purpose narrative (not template boilerplate)
MUST:     Every child scope declares domain-specific Constraints (MUST/MUST NOT)
MUST:     .ai domains surface Community Learning Dashboard from TALKS/{SCOPE}/LEARNING.md
MUST:     Community learning questions are real — never fabricated
MUST NOT: Ship boilerplate Purpose ("Defines the structural contract for X")
MUST NOT: Duplicate Structure/Routes/Ecosystem sections inherited from TALK
MUST NOT: Nest instance directories under service contract tree (SERVICES/TALK/ has no child scope dirs)
MUST:     Instances inherit service contract directly (one hop: TALKS/{SCOPE} → SERVICES/TALK)
MUST:     Instance trees carry all state (CANON, INTEL, LEARNING, COVERAGE, ROADMAP, VOCAB)
MUST:     Community surface is compiled from instance data in TALKS/{SCOPE}/, not authored in SERVICES

TALK

TALK is CHAT + INTEL + COIN composed. Industry determines the voice. INTEL provides the knowledge. COIN gates premium access.

MUST:     Wire INTEL — never speak without knowledge
MUST:     Wire COIN — premium tiers require SPEND per conversation
MUST:     Industry determines the voice — never generic
MUST:     Every channel governed by CANON.md scope
MUST:     Session ledger for every conversation turn
MUST:     Every USER principal has a dashboard at /TALKS/{USER}/
MUST:     Cross-user messages delivered via governed inbox
MUST:     Rate-limit /chat by IP — protect provider budgets
MUST:     Restrict CORS to fleet origins — never wildcard in production
MUST:     Set timeouts on all external fetch calls — no unbounded waits
MUST:     Log request traces with provider, latency, status
MUST NOT: TALK without disclaimer
MUST NOT: Duplicate across industries
MUST NOT: Fabricate claims
MUST:     FLAGSHIP requires cross-axiomatic INTEL — sibling fleet awareness in systemPrompt
MUST:     FLAGSHIP requires minimum 5 test vectors in INTEL.md
MUST:     FLAGSHIP requires cross-domain routing table (when to reference legal, financial, clinical)
MUST:     FLAGSHIP requires explicit COIN structure (not implicit)
MUST:     FLAGSHIP requires active LEARNING ledger with SESSION_LEDGERED signals

SERVICES

SERVICES are SURFACE routes with governed boundaries.

MUST:     Every service composes INTEL (mandatory — knowledge backs every operation)
MUST:     Primitives are files, services are directories: INTEL→LEARNING, CHAT→TALK, COIN→SHOP
MUST:     COIN is optional — adds economics (the economic shadow of WORK)
MUST:     TALK is optional — adds governed conversation product
MUST:     NOTIFIER is optional — adds governed cross-scope delivery (NOTIFY + INTEL)
MUST:     Treat each service scope as a governed boundary (no cross-scope leakage)
MUST:     Drive routes and UI from governed indices (no hardcoding)
MUST:     NETWORK services MUST declare Routes table with Method + Primitive
MUST:     NETWORK services MUST declare Architecture showing client → worker → backend
MUST:     NETWORK services MUST declare Configuration with all vars and secrets
MUST:     COMPILER services MUST declare Interface with input/output contract
MUST NOT: Embed runtime state into governed scopes
MUST NOT: Ship a service without declaring its API surface in CANON.md

SURFACE

SURFACE is the platform lane.

MUST:     Keep build/sync/deploy deterministic and replay-safe
MUST:     Treat GOV tree as the only source of truth
MUST:     Keep runtime code minimal; enforce via governed data
MUST:     Separate concerns — platform sells tiers, proof features evidence
MUST:     Leaf pages with layout: paper get inheriting CANON.json — TALK walks inheritance chain
MUST:     APP surface_type — Next.js App Router, reads galaxy.json + CANON.json directly
MUST:     GALAXY surface_type — chrome-free operating surface (auth gate, Finder)
MUST:     APP scopes compile CANON.md → CANON.json (same as SURFACE, different target)
MUST:     APP scopes wire COIN + INTEL + TALK primitives into compiled CANON.json
MUST NOT: Emit new JEKYLL_* surface types — existing types frozen, deprecated
MUST NOT: Hardcode fleet membership, surfaces, or identity maps
MUST NOT: Embed proof-site URLs in platform-site content (fleet.json eco-bar only)

MAGIC

INTEL. CHAT. COIN. — Three primitives. One governed economy.

MUST:     CANON.md in every scope
MUST:     Services compose primitives — never duplicate
MUST:     Primitive structure is fixed — industry is the only variable
MUST:     Primitives compose into services — never duplicate
MUST:     Services connect through SHOP.md and VAULT.md projection files
MUST:     SHOP.md = public projection file (filesystem-discoverable, UPPERCASE per LANGUAGE)
MUST:     VAULT.md = private projection file (filesystem-discoverable, auth-gated, UPPERCASE per LANGUAGE)
MUST:     Instance = service projected through user governance context
MUST:     Instance directories live at USER scope ({USER}/{PLURAL}/), not nested in SERVICES/
MUST:     Service directories (SERVICES/{SINGULAR}/) define schemas — instances hold content
MUST:     Every .md compiles to .json with the same name (direct mapping)
MUST:     CANON.md = axiom + universal constraints only (no service names, no paths, no implementation)
MUST:     README.md = how to run the CANON only
MUST:     {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST:     Inheritance resolves upward — scopes compose by directories
MUST:     Tier algebra is canonical — DESIGN.md is the single source (COMPLIANCE tier algebra)
MUST NOT: Expose dimension internals to users or developers
MUST NOT: Hardcode outside governed contracts
MUST:     Nonprofits get enterprise for free
MUST:     ORG is the container; USER is the repo (`github.com/{org}/{user}`; duplicates across orgs allowed)
MUST:     MARKET/ SALES/ GTM/ exist (META self-closure; one primitive each)
MUST:     Each META sub-scope maps exactly one primitive (INTEL, CHAT, COIN)
MUST NOT: Add META business knowledge outside MAGIC/ scope
MUST NOT: Remove META sub-scope without replacing its primitive coverage
MUST:     `{SCOPE}.md` is the scope contract surface; it MUST NOT be treated as a generic filename placeholder
MUST:     LEARNING.md is the terminal — governance evidence, patterns, epoch rotation
MUST:     LEARNING/ is the IDF directory — machine-generated individual data files
MUST:     LEARNING.md rotates at epoch boundaries — frozen epochs archive as LEARNING-{EPOCH}.md at scope root
MUST:     LEARNING.md is always the current epoch — active, append-only
MUST:     Epoch boundary = EVOLUTION signal in LEARNING.md (named, dated, sourced)
MUST NOT: Delete archived LEARNING epochs — append-only history
MUST:     MAGIC defines the triad interface directly:
MUST:     COMPLIANCE/ + GALAXY/ + SURFACE/
MUST NOT: Define conflicting tier algebra in downstream scopes; downstream must inherit this contract