statute-analysis

What this skill does

> **⚠️ EXPERIMENTAL** — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.

# Statute Analysis

Production-ready framework for reading, interpreting, and applying statutes, regulations, and rules. Covers the full lifecycle from identifying the legal hierarchy through extracting actionable requirements and mapping implementation obligations.

---

## Table of Contents

- [Legal Hierarchy](#legal-hierarchy)
- [Preliminary Steps](#preliminary-steps)
- [Tools](#tools)
- [Core Interpretation Techniques](#core-interpretation-techniques)
- [Canons of Construction](#canons-of-construction)
- [Interpretation Sources](#interpretation-sources)
- [Requirement Classification](#requirement-classification)
- [Cross-Jurisdictional Analysis](#cross-jurisdictional-analysis)
- [Reference Guides](#reference-guides)
- [Workflows](#workflows)
- [Troubleshooting](#troubleshooting)
- [Success Criteria](#success-criteria)
- [Scope and Limitations](#scope-and-limitations)
- [Anti-Patterns](#anti-patterns)
- [Tool Reference](#tool-reference)

---

## Legal Hierarchy

Understanding the source hierarchy is the foundation of statutory analysis.

| Source | Created By | Authority | Example |
|--------|-----------|-----------|---------|
| Constitution | Sovereign/people | Supreme | U.S. Constitution, EU Treaties |
| Statute | Legislature | Primary legislation | GDPR, Clean Air Act, AI Act |
| Regulation | Executive agency | Delegated authority | FDA 21 CFR, FTC rules |
| Rule | Agency or court | Procedural/interpretive | Federal Rules of Civil Procedure |
| Guidance | Agency | Non-binding, persuasive | FDA guidance documents, CNIL guides |
| Case law | Courts | Binding within jurisdiction | Supreme Court precedent |

**Key principle:** Higher sources override lower sources. Regulations cannot exceed statutory authority. Guidance cannot create new obligations not grounded in statute.

---

## Preliminary Steps

Before interpreting any statutory provision, complete these checks:

1. **Verify currency and status** -- Is this the current, in-force version? Check for amendments, repeals, or sunset clauses. Use official sources (government gazettes, EUR-Lex, congress.gov).
2. **Understand the regulatory ecosystem** -- What regulations, rules, and guidance implement this statute? Map the full hierarchy.
3. **Browse the full structure** -- Read the table of contents, definitions section, scope provisions, and transitional articles before diving into specific sections.
4. **Identify the definitions section** -- Almost all statutes define key terms. These definitions override ordinary meaning.
5. **Check effective dates** -- Different provisions may have different effective dates. Map the compliance timeline.
6. **Identify your role** -- Statutes impose different obligations depending on the reader's role (e.g., "provider" vs "deployer" in the EU AI Act, "controller" vs "processor" in GDPR).

---

## Tools

### Statute Keyword Analyzer

Scans statute text for operative keywords and classifies obligations, permissions, conditions, and exemptions.

```bash
# Analyze a statute file
python scripts/statute_keyword_analyzer.py --input statute.txt

# Analyze with JSON output
python scripts/statute_keyword_analyzer.py --input regulation.txt --json

# Analyze inline text
python scripts/statute_keyword_analyzer.py --text "The controller shall implement appropriate technical measures..."

# Save analysis report
python scripts/statute_keyword_analyzer.py --input statute.txt --output analysis.json
```

### Requirement Classifier

Classifies statutory requirements by type, implementation team, enforcement mechanism, and penalty.

```bash
# Classify requirements from a JSON list
python scripts/requirement_classifier.py --input requirements.json

# Classify with JSON output
python scripts/requirement_classifier.py --input requirements.json --json

# Classify inline requirement
python scripts/requirement_classifier.py --text "Controllers must provide data subjects with a privacy notice at the point of collection"

# Generate implementation matrix
python scripts/requirement_classifier.py --input requirements.json --output matrix.json
```

---

## Core Interpretation Techniques

### Definitions Analysis

Statutory definitions control meaning. Pay attention to the verb used:

| Verb | Type | Meaning | Example |
|------|------|---------|---------|
| "means" | Exhaustive | The definition is complete; no other meaning applies | "'Personal data' means any information relating to an identified or identifiable natural person" |
| "includes" | Illustrative | The definition provides examples but is not limited to them | "'Processing' includes collection, recording, organization, structuring..." |
| "does not include" | Exclusion | Explicitly carves out items from scope | "'Consumer' does not include a natural person acting in a commercial or employment context" |
| "refers to" | Pointer | Incorporates an external definition | "'Harmonised standard' refers to a European standard as defined in Regulation (EU) No 1025/2012" |

### Operative Keywords

| Keyword | Classification | Legal Effect |
|---------|---------------|-------------|
| **shall** | Mandatory | Creates an obligation; must be done |
| **must** | Mandatory | Same as "shall" in modern drafting |
| **may** | Permissive | Creates permission; optional |
| **may not** | Prohibitive | Creates a prohibition |
| **and** | Conjunctive | All listed items required |
| **or** | Disjunctive | Any listed item sufficient |
| **unless** | Exception | Negates the rule when condition is met |
| **except** | Exception | Carves out specific items from the rule |
| **subject to** | Conditional | Rule applies but another provision modifies it |
| **notwithstanding** | Override | This provision prevails over conflicting provisions |
| **provided that** | Condition | Adds a requirement that must be satisfied |
| **if...then** | Conditional | Trigger condition and consequence |
| **upon** | Temporal trigger | Action required when event occurs |

### Conjunctive vs Disjunctive Analysis

This distinction determines whether ALL conditions must be met or ANY single condition suffices.

| Pattern | Reading | Practical Impact |
|---------|---------|-----------------|
| "A, B, and C" | All three required | Must satisfy every element |
| "A, B, or C" | Any one sufficient | Satisfy any single element |
| "A, B, and/or C" | Ambiguous | Flag for clarification; analyze context |
| "both A and B" | Explicitly conjunctive | Must satisfy both |
| "either A or B" | Explicitly disjunctive | Satisfy one |
| Serial comma ambiguity | Context-dependent | Apply whole-act rule for consistency |

---

## Canons of Construction

See `references/canons_of_construction.md` for the complete 12-canon reference.

### Quick Reference

| Canon | Core Rule | When to Apply |
|-------|----------|---------------|
| General-Terms Canon | General terms get general meaning | Default interpretation |
| Expressio Unius | Expressing one thing excludes others | Specific lists without catchall |
| Whole-Act Rule | Interpret provisions consistently | Apparent conflicts between sections |
| Consistent Usage | Same term = same meaning throughout | Term appears multiple times |
| Meaningful Variation | Different terms = different meanings | Similar but distinct terms used |
| Surplusage Canon | Every word has meaning; no redundancy | Tempted to treat words as surplus |
| Noscitur a Sociis | Words known by their associates | Ambiguous term in a list |
| Ejusdem Generis | General follows specific = limited | "...and other similar" patterns |
| Against Ineffectiveness | Prefer reading that gives effect | Two possible readings |
| Avoiding Absurdity | Reject absurd outcomes | Literal reading produces nonsensical result |
| Remedial Statutes | Construe liberall