LAW
SERVICE CONTRACT · VIEW: GOV
Axiom
Example
Constraints
MUST: Cite statute, regulation, or case law for legal claims MUST: Distinguish binding authority from persuasive authority MUST NOT: Present legal information as legal advice
COVERAGE: 255/255
SPEC
Domain Declaration
LAW = LEGAL_STANDARD × CANONIC
= Structure(legal) × (C1, C2, Temporal, Relational, C5)
= owned legal vertical
Lattice Formula
LAW = C1 ∩ C2 ∩ Temporal ∩ Relational ∩ C5
= PATENT (#57)
Legal is typically PATENT-level (no structural standard) because:
- C1: Legal claims must be stated precisely
- C2: Evidence must support claims
- Temporal: Timing is critical (statutes of limitation, filing dates)
- Relational: Jurisdiction determines applicable law
- C5: Courts and agencies enforce
Structure varies by practice area (no universal legal data standard).
Axioms
1. Jurisdictional Primacy
Legal validity is determined by applicable jurisdiction. All legal work MUST identify governing law.
Example: A contract between a California company and a Texas company must specify which state’s law governs disputes. “This Agreement shall be governed by the laws of the State of Delaware.”
2. Evidentiary Foundation
Legal claims MUST be supported by admissible evidence.
Example: A patent infringement claim must include claim charts mapping accused product features to patent claim elements, with documentary evidence for each mapping.
3. Temporal Precision
Legal matters are time-bound. Deadlines MUST be tracked and met.
Example: A provisional patent application establishes priority date. The non-provisional MUST be filed within 12 months. Missing this deadline destroys patent rights.
4. Chain of Custody
Evidence MUST maintain documented chain of custody.
Example: Digital evidence in litigation must show: who collected it, when, how it was preserved, who accessed it, and that it remains unaltered. Any break in chain challenges admissibility.
5. Adversarial Integrity
Legal work product MUST withstand adversarial scrutiny.
Example: A patent application must disclose all known prior art. Failure to disclose material prior art can render the patent unenforceable (inequitable conduct).
Subdomains
| Subdomain | Practice Area | Formula | Description |
|---|---|---|---|
| Intellectual Property | Patents, Trademarks, Copyright | 5 governance checks | IP protection |
| Corporate | Entity Formation, Governance | BUSINESS | Business structure |
| Contracts | Agreements, Licensing | (#30) | Binding arrangements |
| Litigation | Disputes, Enforcement | 5 governance checks | Court proceedings |
| Regulatory | Compliance, Licensing | 5 governance checks | Agency oversight |
| Employment | Labor, Benefits | 5 governance checks | Workforce governance |
Regulatory Mapping
| Framework | Lattice | Scope |
|---|---|---|
| Patent Law (35 USC) | 5 governance checks | Invention protection |
| Copyright Law (17 USC) | 5 governance checks | Creative works |
| Trademark Law (15 USC) | 5 governance checks | Brand protection |
| Contract Law (UCC) | — | Commercial transactions |
| Corporate Law (State) | — | Entity governance |
| Securities Law (33/34 Act) | 5 governance checks | Capital markets |
| Antitrust Law (Sherman/Clayton) | 5 governance checks | Competition |
Example: Patent Prosecution Vertical
DECLARE(Patent) = USPTO_RULES × CANONIC
Where:
USPTO provides Structure:
- Application format (specification, claims, drawings)
- Filing requirements (fees, declarations)
- Prosecution procedures (office actions, responses)
- Maintenance (fees, corrections)
CANONIC provides Governance:
- C1: Claims in CANON.md (patent claims)
- C2: Proof in COVERAGE.md (prior art analysis)
- Temporal: Priority dates, deadlines
- Relational: Continuation/divisional hierarchy
- C5: USPTO examination
Result:
Patent = BUSINESS
Lifecycle:
IDF — Initial disclosure
Disclosure — Public/private boundary
Provisional — Filed with proof
Filed — Full application
Patent — Granted with enforcement
Example: Contract Management Vertical
DECLARE(Contract) = CONTRACT_LAW × CANONIC
Where:
Contract Law provides Structure:
- Offer and acceptance
- Consideration
- Terms and conditions
- Signatures
CANONIC provides Governance:
- C1: Contract terms as claims
- Relational: Party relationships, jurisdiction
- C6: Template conformance
Result:
Contract = (#30)
Lifecycle:
Draft — Terms with structure
Negotiation — Parties, boundaries
Execution — Signed (evidence)
Active — Dated, bounded
Enforced — Breach remedies
Validators
| Validator | Checks | Example Failure |
|---|---|---|
| C1 | Legal claims precisely stated | Ambiguous contract term |
| C2 | Evidence supports claims | Patent claim without support |
| Temporal | Deadlines tracked and met | Missed filing deadline |
| Relational | Jurisdiction identified | No governing law clause |
| C5 | Enforcement mechanism exists | Unenforceable provision |
Live Proof — Hadley Lab
| Product | Domain | Standards | URL |
|---|---|---|---|
| LawChat | Legal literacy | Jurisdiction-aware + sourced + non-advisory | hadleylab.org/chat/lawchat/ |
LawChat demonstrates MAGIC 255 governance applied to legal information. Not legal advice — legal literacy. Every answer jurisdiction-tagged and source-cited. Same INTEL + CHAT + COIN composition as the clinical AI suite.
Application
To create a CANONIC legal vertical:
- Identify practice area (IP, corporate, contracts, etc.)
- Create scope with CANON.md inheriting /LAW/
- Define legal claims as axioms
- Document evidence in COVERAGE.md
- Track temporal elements (deadlines, dates)
- Specify jurisdiction in Relational bounds
- Define enforcement mechanisms
Result: Owned legal vertical with complete audit trail.
LEARNING
ROADMAP
VOCAB
| Term | Definition |
|---|---|
| CCPA | Governed term in this scope vocabulary. |
| COPPA | Governed term in this scope vocabulary. |
| CPA | Governed term in this scope vocabulary. |
| CPRA | Governed term in this scope vocabulary. |
| CTDPA | Governed term in this scope vocabulary. |
| ESI | Governed term in this scope vocabulary. |
| EU | Governed term in this scope vocabulary. |
| FCA | Governed term in this scope vocabulary. |
| FDA | Governed term in this scope vocabulary. |
| FRAP | Governed term in this scope vocabulary. |
| FRCP | Governed term in this scope vocabulary. |
| FRE | Governed term in this scope vocabulary. |
| GDPR | Governed term in this scope vocabulary. |
| GPL | Governed term in this scope vocabulary. |
| HHS | Governed term in this scope vocabulary. |
| HIPAA | Governed term in this scope vocabulary. |
| IP | Governed term in this scope vocabulary. |
| LAW | Governed term in this scope vocabulary. |
| MIT | Governed term in this scope vocabulary. |
| OCR | Governed term in this scope vocabulary. |
| PCT | Governed term in this scope vocabulary. |
| PI | Governed term in this scope vocabulary. |
| UCC | Governed term in this scope vocabulary. |
| UCPA | Governed term in this scope vocabulary. |
| USC | Governed term in this scope vocabulary. |
| VCDPA | Governed term in this scope vocabulary. |
INHERITANCE CHAIN
INDUSTRIES
INDUSTRY is the variable. SERVICE = PRIMITIVE(s) + INDUSTRY. Each vertical defines INTEL, CHAT, COIN.
MUST: Every INDUSTRY wires INTEL + CHAT + COIN MUST: Standards mapped to governance dimensions MUST: LANGUAGE cascades from MAGIC — no per-industry DESIGN.md MUST NOT: Create INDUSTRY without SERVICE proof
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
FOUNDATION
SPEC = {SCOPE}. The LANGUAGE. The v0 discovery.
MUST: LANGUAGE defines all governance primitives MUST: Every scope inherits from FOUNDATION MUST: Triad (CANON.md + VOCAB.md + README.md) in every scope MUST NOT: Define terms outside VOCAB.md MUST NOT: Hardcode outside the kernel SHOULD: Vocabulary closure — every term resolves to a definition