Statute Analysis

Legal Hierarchy

Understanding the source hierarchy is the foundation of statutory analysis.

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.

# 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.

# 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:

Operative Keywords

Conjunctive vs Disjunctive Analysis

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

Canons of Construction

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

Quick Reference

Interpretation Sources

When statutory text is ambiguous, consult sources in this order:

Requirement Classification

Every statutory requirement maps to an implementation category:

Cross-Jurisdictional Analysis

When requirements from multiple jurisdictions apply:

1. Map applicable jurisdictions -- Where are your users, your entity, and your data?
2. Identify overlapping requirements -- Many frameworks share common obligations.
3. Find the highest common denominator -- Design for the strictest requirement that satisfies all jurisdictions.
4. Flag conflicts -- Where requirements genuinely conflict, document the conflict and seek legal advice.
5. Check preemption -- Federal law may preempt state law; EU regulations may preempt member state law.

Enforcement Analysis

For each statutory requirement, assess enforcement risk:

Reference Guides

Workflows

Workflow 1: First Reading of a New Statute

1. Browse the full table of contents and structure.
2. Read the definitions section and scope provisions.
3. Check effective dates and transitional provisions.
4. Identify your role under the statute.
5. Run scripts/statute_keyword_analyzer.py on the full text.
6. Review the obligation/permission/exception map.
7. Identify provisions that apply to your role.
8. Validation: Definitions cataloged, role identified, key obligations listed.

Workflow 2: Requirement Extraction and Classification

1. Extract all provisions containing "shall," "must," or mandatory language.
2. For each requirement, identify: who (subject), what (action), when (trigger/deadline), how (standard).
3. Run scripts/requirement_classifier.py on the extracted requirements.
4. Review the implementation matrix.
5. Assign each requirement to an implementation team.
6. Prioritize by enforcement risk and deadline.
7. Validation: Every mandatory provision classified, assigned, and prioritized.

Workflow 3: Cross-Reference Resolution

1. Identify all cross-references in the target provision ("subject to Article X," "as defined in Section Y").
2. Read each referenced provision in full.
3. Determine whether the cross-reference modifies, limits, or supplements the target provision.
4. Check for circular references or chains (A references B which references C).
5. Document the complete picture -- the target provision as modified by all cross-references.
6. Validation: All cross-references resolved; no orphan references.

Troubleshooting

Success Criteria

Scope & Limitations

In scope: Reading and interpreting statutory text, extracting requirements, classifying obligations, applying canons of construction, mapping enforcement risk.

Out of scope: Providing legal advice, predicting court outcomes, drafting legislation, interpreting case law holdings, constitutional analysis.

Disclaimer: This skill provides a structured methodology for statutory analysis. It does not constitute legal advice. Always consult qualified legal counsel for binding interpretations.

Anti-Patterns

Tool Reference