borghei/Claude-Skills / legal/statute-analysis
statute-analysis
VerifiedStatute and regulation interpretation framework. Use when reading statutes, classifying requirements, analyzing operative keywords, applying canons of construction, or mapping compliance obligations from legislative text.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.9 KB |
| references/canons_of_construction.md | markdown | 16.4 KB |
| references/statutory_structure.md | markdown | 15.7 KB |
| scripts/requirement_classifier.py | script | 14.1 KB |
| scripts/statute_keyword_analyzer.py | script | 14.7 KB |
references/statutory_structure.md
View on GitHub# Statutory Structure Reference
How statutes and regulations are organized, read, and navigated. Covers structural hierarchy, definitions sections, effective dates, preemption, cross-references, enforcement, and the "what the statute doesn't say" checklist.
---
## Table of Contents
- [Structural Hierarchy](#structural-hierarchy)
- [Finding and Reading Definitions](#finding-and-reading-definitions)
- [Effective Dates and Transitional Provisions](#effective-dates-and-transitional-provisions)
- [Amendments and Consolidated Versions](#amendments-and-consolidated-versions)
- [Preemption Analysis](#preemption-analysis)
- [Cross-Reference Tracking](#cross-reference-tracking)
- [Common Threshold Types](#common-threshold-types)
- [Enforcement Analysis](#enforcement-analysis)
- [What the Statute Does Not Say](#what-the-statute-does-not-say)
---
## Structural Hierarchy
Statutes follow a nested hierarchy. Understanding this structure is essential for precise citation and navigation.
### US Federal Statutes (United States Code)
| Level | Label | Example |
|-------|-------|---------|
| Title | Major subject area | Title 15 -- Commerce and Trade |
| Chapter | Subdivision of title | Chapter 98 -- CAN-SPAM |
| Subchapter | Subdivision of chapter | Subchapter I -- General Provisions |
| Section (§) | Individual provision | § 7702 -- Definitions |
| Subsection | Lettered subdivision | § 7702(a) |
| Paragraph | Numbered subdivision | § 7702(a)(1) |
| Subparagraph | Lettered sub-subdivision | § 7702(a)(1)(A) |
| Clause | Roman-numeral subdivision | § 7702(a)(1)(A)(i) |
### US Federal Regulations (Code of Federal Regulations)
| Level | Label | Example |
|-------|-------|---------|
| Title | Subject area | Title 16 -- Commercial Practices |
| Chapter | Agency | Chapter I -- Federal Trade Commission |
| Subchapter | Topic area | Subchapter C -- Regulations |
| Part | Specific regulation | Part 312 -- COPPA Rule |
| Subpart | Subdivision of part | Subpart A -- General Provisions |
| Section (§) | Individual provision | § 312.2 -- Definitions |
### EU Legislation
| Level | Label | Example (GDPR) |
|-------|-------|----------------|
| Recitals | Interpretive context (numbered) | Recital (26) -- Anonymous data |
| Chapter | Major division | Chapter II -- Principles |
| Section | Subdivision of chapter | Section 1 -- Transparency |
| Article | Individual provision | Article 5 -- Principles relating to processing |
| Paragraph | Numbered subdivision | Article 5(1) |
| Point/Letter | Lettered subdivision | Article 5(1)(a) |
| Sub-point | Roman numeral | Article 5(1)(a)(i) |
### UK Legislation
| Level | Label | Example |
|-------|-------|---------|
| Part | Major division | Part 2 -- General processing |
| Chapter | Subdivision of part | Chapter 2 -- The GDPR |
| Section | Individual provision | Section 6 -- The applied GDPR |
| Subsection | Numbered subdivision | Section 6(1) |
| Paragraph | Lettered subdivision | Section 6(1)(a) |
| Schedule | Supplementary material | Schedule 1 -- Special categories of personal data |
---
## Finding and Reading Definitions
### Where Definitions Appear
| Statute Type | Typical Location | Example |
|-------------|-----------------|---------|
| US federal statute | First section of the chapter/title | 15 USC § 7702 (CAN-SPAM definitions) |
| US federal regulation | First section of the part | 16 CFR § 312.2 (COPPA definitions) |
| EU regulation | Early articles (usually Art. 2-4) | GDPR Art. 4 (26 definitions) |
| UK statute | Interpretation section near the end | Data Protection Act 2018 s.3-5 |
### Definition Types
| Signal | Type | Scope |
|--------|------|-------|
| "'X' means..." | Exhaustive | The definition is complete; no other meaning applies |
| "'X' includes..." | Illustrative | Examples listed but meaning extends beyond them |
| "'X' does not include..." | Exclusion | Specific items removed from scope |
| "'X' refers to..." | Pointer | Incorporates a definition from another source |
| "For the purposes of this Section..." | Scoped | Definition applies only to specified provisions |
| "Unless the context otherwise requires..." | Contextual | Definition is default but can be overridden by context |
### Reading Strategy
1. **Read definitions first** before reading substantive provisions.
2. **Map defined terms** to their operative provisions.
3. **Check for scoped definitions** -- some terms are redefined for specific sections.
4. **Note incorporated definitions** -- terms defined by reference to other instruments.
5. **Watch for undefined terms** -- apply the general-terms canon (ordinary meaning).
---
## Effective Dates and Transitional Provisions
### Effective Date Patterns
| Pattern | Meaning | Example |
|---------|---------|---------|
| "This Act enters into force on [date]" | All provisions effective on stated date | Simple effective date |
| "This Regulation shall apply from [date]" | EU pattern: enters into force 20 days after publication but applies from later date | GDPR: entered into force May 2016, applied from May 2018 |
| Phased effective dates | Different provisions effective at different times | EU AI Act: prohibited practices Feb 2025, high-risk Dec 2027 (as amended in 2026) |
| "Within [X] months of entry into force" | Delegated acts or implementing measures due by deadline | Agency must publish rules within 12 months |
| Sunset clause | Provision expires on stated date | Temporary measures, emergency powers |
### Transitional Provisions
| Type | Purpose | Example |
|------|---------|---------|
| Grandfathering | Existing activities continue under old rules | "Systems placed on the market before [date] remain subject to [old requirement]" |
| Grace period | Time to achieve compliance | "Entities shall comply within 24 months of entry into force" |
| Phase-in | Gradual application by category | Small enterprises: 36 months; large enterprises: 24 months |
| Saving clause | Preserves rights/obligations from prior law | "Proceedings commenced under [old law] shall continue under [old law]" |
### Compliance Timeline Construction
1. Identify the statute's entry-into-force date.
2. List each provision with its specific effective date (if phased).
3. Identify any transitional provisions that modify timing.
4. Check for delegated acts with their own timelines.
5. Map deadlines to a calendar and assign compliance owners.
---
## Amendments and Consolidated Versions
### Types of Amendments
| Type | Effect | How to Identify |
|------|--------|----------------|
| Textual amendment | Replaces specific words in the original | "In Article X, replace 'Y' with 'Z'" |
| Insertion | Adds new provisions | "After Article X, insert Article X-a" |
| Repeal | Removes provision entirely | "Article X is repealed" |
| Substitution | Replaces entire section | "For Article X, substitute the following" |
### Finding Current Law
| Jurisdiction | Consolidated Source | Notes |
|-------------|-------------------|-------|
| US federal | United States Code (uscode.house.gov) | Official codification; updated regularly |
| US regulations | eCFR (ecfr.gov) | Updated daily; not official but authoritative |
| EU | EUR-Lex consolidated text | Marked "only for reference"; check latest OJ for amendments |
| UK | legislation.gov.uk | Shows amendments with tracked changes |
**Warning:** Always verify you are reading the current, in-force version. Citing repealed or amended provisions is a common error.
---
## Preemption Analysis
Preemption determines which law controls when multiple jurisdictions overlap.
### US Federal-State Preemption
| Type | Definition | Example |
|------|-----------|---------|
| Express preemption | Federal statute explicitly preempts state law | "No State shall maintain... any requirement different from" |
| Implied preemption (field) | Federal scheme is so comprehensive it occupies the entire field | Immigration law |
| Implied preemption (conflict) | Compliance with both federal and state law is impossible | State law requires what federal law prohibits |
| Floor preemption | Federal law sets a minimum; states may go higher | CCPA exceeds federal privacy protections |
| Ceiling preemption | Federal law sets a maximum; states may not exceed | Federal banking regulations |
### EU Preemption
| Instrument | Preemptive Effect |
|-----------|-------------------|
| Regulation | Directly applicable; generally preempts conflicting member state law |
| Directive | Sets minimum standards; member states transpose with possible additions |
| Regulation with member state margin | Regulation but explicitly allows member state variation (e.g., GDPR Art. 9(4)) |
### Preemption Checklist
1. Does the statute contain an express preemption clause? (Read it carefully -- scope matters.)
2. Does the statute contain a savings clause preserving other laws? (Common in consumer protection.)
3. Is the federal scheme comprehensive enough to imply field preemption?
4. Can an entity comply with both laws simultaneously?
5. Does the statute set a floor or a ceiling?
---
## Cross-Reference Tracking
### Types of Cross-References
| Type | Example | Interpretation |
|------|---------|---------------|
| Definitional | "as defined in Article 4" | Imports the definition |
| Qualifying | "subject to Article 23" | Another provision limits or modifies this one |
| Supplementing | "in addition to the requirements of Article 9" | Both provisions apply cumulatively |
| Override | "notwithstanding Article 15" | This provision prevails over Article 15 |
| Conditional | "where Article 6(1)(a) applies" | Triggered only when the referenced condition exists |
| External | "as referred to in Directive 2001/95/EC" | Imports requirements from a different instrument |
### Cross-Reference Resolution Process
1. Read the target provision.
2. Identify every cross-reference within it.
3. Read each referenced provision in full.
4. Classify each cross-reference (qualifying, supplementing, override, etc.).
5. Check for chains: does the referenced provision reference yet another?
6. Document the complete picture: the target provision plus all modifications.
7. Watch for circular references -- they exist and create genuine ambiguity.
---
## Common Threshold Types
Many statutes create obligations that apply only when certain thresholds are met.
| Threshold Type | Examples | Analysis |
|---------------|---------|----------|
| Revenue/turnover | "Businesses with annual revenue exceeding $25 million" (CCPA) | Determine calculation method (gross vs net, calendar vs fiscal year) |
| Volume | "Processes personal data of 100,000+ consumers annually" (CCPA) | Determine counting methodology |
| Employee count | "Employers with 50 or more employees" (FMLA) | Check if part-time counts; check geographic scope |
| Entity type | "Financial institutions," "covered entities" | Read the definition precisely; check for exclusions |
| Geographic | "Entities established in the Union" or "offering goods to EU residents" | Both establishment and targeting tests may apply |
| Data type | "Special categories of personal data" (GDPR Art. 9) | Exhaustive list -- only the enumerated categories qualify |
| Risk level | "High-risk AI system" (EU AI Act Art. 6) | Follow the classification decision tree precisely |
### Conjunctive vs Disjunctive Thresholds
| Statute Pattern | Reading | Impact |
|----------------|---------|--------|
| "Revenue > $25M AND processes data of > 100K consumers" | Must meet BOTH thresholds | Narrower scope |
| "Revenue > $25M OR processes data of > 100K consumers" | Must meet EITHER threshold | Broader scope |
| "Revenue > $25M, and processes data of > 100K consumers, or derives 50%+ of revenue from selling data" | First two conjunctive, third disjunctive | Parse structure carefully |
---
## Enforcement Analysis
For each statutory requirement, assess enforcement risk using these factors.
### Enforcement Authority
| Factor | Questions to Ask |
|--------|-----------------|
| Which agency enforces? | Primary regulator and any concurrent enforcement authority |
| How active is the agency? | Enforcement actions per year, budget, staffing trends |
| Is there a dedicated enforcement unit? | Specialized teams signal enforcement priority |
| What enforcement tools exist? | Investigation, subpoena, administrative proceedings, litigation |
### Penalty Types
| Type | Characteristics | Examples |
|------|----------------|---------|
| Civil fines | Administrative penalties; no criminal record | GDPR: up to EUR 20M or 4% of turnover |
| Criminal penalties | Prosecution, imprisonment, criminal record | US: willful violations of certain statutes |
| Administrative sanctions | Orders, bans, suspensions | Cease processing orders, license suspension |
| Private right of action | Individuals can sue directly | CCPA: $100-$750 per consumer per incident |
| Injunctive relief | Court-ordered cessation of conduct | Temporary or permanent injunctions |
### Enforcement Risk Matrix
| Factor | Low Risk | Medium Risk | High Risk |
|--------|----------|-------------|-----------|
| Enforcement history | Few or no actions | Regular actions in the area | Active enforcement campaign |
| Penalty severity | Low fixed fines | Material fines | Revenue-based penalties |
| Private right of action | No | Limited | Broad with statutory damages |
| Cure period | Extended cure period | Short cure period | No cure period |
| Regulatory guidance | Clear and favorable | Ambiguous | Unfavorable or absent |
---
## What the Statute Does Not Say
A critical part of statutory analysis is identifying what the statute omits. Silence can mean permission, delegation, oversight, or ambiguity.
### 10-Point Checklist
| # | Check | Why It Matters |
|---|-------|---------------|
| 1 | **Does the statute define this term?** | If not defined, ordinary meaning applies -- which may be broader or narrower than expected |
| 2 | **Does the statute address this specific scenario?** | If the statute is silent on a scenario, it may be permissible, delegated to regulation, or an oversight |
| 3 | **Is there an explicit exception for this activity?** | Absence of an exception may mean the general rule applies -- or that the legislature did not contemplate the activity |
| 4 | **Does the statute specify a method or standard?** | Silence on method may mean any reasonable method is acceptable |
| 5 | **Does the statute set a numerical threshold?** | Absence of a threshold may mean the obligation applies universally or that threshold is delegated |
| 6 | **Does the statute name an enforcement authority?** | No named enforcer may mean general enforcement powers or no enforcement mechanism |
| 7 | **Does the statute provide a private right of action?** | Silence on private action generally means no private right (courts will not imply one) |
| 8 | **Does the statute address cross-border application?** | Silence on extraterritoriality creates uncertainty -- analyze based on jurisdiction principles |
| 9 | **Does the statute address conflicts with other laws?** | No preemption or savings clause creates ambiguity about which law prevails |
| 10 | **Does the statute provide for future regulatory development?** | Delegation clauses signal that key details will come in later regulations |
### Interpreting Statutory Silence
| Possible Meaning | How to Determine | Action |
|-----------------|-----------------|--------|
| Permission | Expressio unius: specific prohibitions listed, this activity not among them | Document reasoning; monitor for future amendments |
| Delegation | Statute grants agency authority to "prescribe rules" or "establish requirements" | Check for implementing regulations |
| Oversight | Legislature did not consider this scenario | Flag as gap; seek analogous provisions or guidance |
| Intentional ambiguity | Legislature could not agree on specifics | Document ambiguity; seek case law or agency interpretation |
| Deference to other law | Another body of law already covers this | Identify the applicable law |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |