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/canons_of_construction.md
View on GitHub# Canons of Statutory Construction
Complete reference for the 12 core canons used in statutory interpretation, organized by type. Each canon includes definition, explanation, example, and common misapplications.
---
## Table of Contents
- [Interpretation Priority](#interpretation-priority)
- [Textual Canons](#textual-canons)
- [General-Terms Canon](#1-general-terms-canon)
- [Negative-Implication Canon (Expressio Unius)](#2-negative-implication-canon-expressio-unius)
- [Whole-Act Rule](#3-whole-act-rule)
- [Consistent Usage Presumption](#4-consistent-usage-presumption)
- [Meaningful Variation](#5-meaningful-variation)
- [Surplusage Canon](#6-surplusage-canon)
- [Associated Words (Noscitur a Sociis)](#7-associated-words-noscitur-a-sociis)
- [Ejusdem Generis](#8-ejusdem-generis)
- [Purpose Canons](#purpose-canons)
- [Presumption Against Ineffectiveness](#9-presumption-against-ineffectiveness)
- [Avoiding Absurdity](#10-avoiding-absurdity)
- [Remedial Statutes Liberal Construction](#11-remedial-statutes-liberal-construction)
- [Rule of Lenity](#12-rule-of-lenity)
- [Interpretation Sources Hierarchy](#interpretation-sources-hierarchy)
- [Applying Canons in Practice](#applying-canons-in-practice)
- [Canon Conflicts](#canon-conflicts)
---
## Interpretation Priority
Before applying canons, follow this priority order:
| Priority | Source | Authority |
|----------|--------|-----------|
| 1 | Plain text of the statute | Controlling -- if clear, no further interpretation needed |
| 2 | Statutory definitions section | Controlling -- overrides ordinary meaning |
| 3 | Legislative purpose (recitals, preamble) | Strong indicator of intent |
| 4 | Canons of construction | Framework for resolving ambiguity |
| 5 | Case law interpreting the provision | Binding within jurisdiction |
| 6 | Agency regulations | Moderate authority (deference varies by jurisdiction) |
| 7 | Agency guidance and FAQs | Persuasive only, not binding |
| 8 | Legislative history | Weak to moderate (varies by jurisdiction) |
| 9 | Academic commentary | Persuasive only |
**Key principle:** Canons are tools for resolving genuine ambiguity. They do not override clear statutory text.
---
## Textual Canons
### 1. General-Terms Canon
**Definition:** Words are to be understood in their ordinary, everyday meaning unless the statute provides a specific definition or the context clearly indicates a technical meaning.
**Explanation:** When a statute uses general terms without defining them, interpret those terms according to their common, accepted meaning. If the statute includes a definitions section, those definitions control -- even if they differ from ordinary usage.
**Example:**
- Statute says "vehicle" without defining it: interpret as any conveyance (car, truck, motorcycle, bicycle).
- Statute defines "vehicle" as "any motorized conveyance": the definition excludes bicycles even though ordinary meaning might include them.
**Common misapplication:** Applying technical or specialized meaning to a term when the statute uses it in its general sense, or vice versa. Always check the definitions section first.
---
### 2. Negative-Implication Canon (Expressio Unius)
**Definition:** The expression of one thing implies the exclusion of others. When a statute lists specific items without a catchall phrase, unlisted items are excluded.
**Explanation:** If the legislature specifically enumerated certain items, the deliberate choice to list those items and not others implies that the omitted items were intentionally excluded. This canon is strongest when the list appears exhaustive.
**Example:**
- Statute grants tax exemption to "hospitals, schools, and churches": museums are excluded.
- Statute applies to "dogs, cats, and ferrets": hamsters are excluded.
**Common misapplication:** Applying this canon to illustrative lists (those using "including" or "such as") rather than exhaustive lists. A list introduced by "including but not limited to" does not trigger this canon.
| List Type | Signal Words | Expressio Unius Applies? |
|-----------|-------------|-------------------------|
| Exhaustive | "means," "the following," "limited to" | Yes |
| Illustrative | "includes," "such as," "including but not limited to" | No |
| Ambiguous | No signal words | Context-dependent; proceed with caution |
---
### 3. Whole-Act Rule
**Definition:** A statute should be interpreted as a coherent whole. Individual provisions should be read in harmony with the entire statute, not in isolation.
**Explanation:** Every provision exists within a larger framework. When one section appears to conflict with another, prefer the interpretation that harmonizes both provisions. The statute's overall structure, purpose, and design inform the meaning of individual parts.
**Example:**
- Section 10 says "data must be deleted after processing." Section 15 says "records must be retained for 5 years." Read together: transactional data is deleted after processing, but legally required records are retained. The provisions address different categories.
**Common misapplication:** Cherry-picking a single provision that supports a desired outcome while ignoring other provisions that limit or qualify it. Always read cross-references, exceptions, and related sections.
---
### 4. Consistent Usage Presumption
**Definition:** When the same word or phrase is used in different parts of a statute, it presumptively carries the same meaning throughout.
**Explanation:** Legislatures are presumed to use language consistently. If "personal data" is defined in Article 3 and appears in Articles 5, 6, and 9, it carries the same meaning in all three articles unless the statute explicitly provides otherwise.
**Example:**
- GDPR defines "processing" in Article 4(2). Every use of "processing" throughout the regulation carries that definition.
- If a statute uses "shall" in one section and "must" in another without distinguishing them, they are presumed synonymous.
**Common misapplication:** Assuming consistent usage across different statutes. The same word may have different definitions in different legislative instruments (e.g., "personal data" in GDPR vs "personal information" in CCPA).
---
### 5. Meaningful Variation
**Definition:** When the legislature uses different words or phrases in related provisions, the variation is presumed intentional and meaningful.
**Explanation:** If two adjacent sections use different terms, assume the legislature chose those different terms deliberately. "Shall inform" is different from "shall notify." "Reasonable" is different from "appropriate."
**Example:**
- Article 33 requires "notification" to the supervisory authority within 72 hours. Article 34 requires "communication" to data subjects "without undue delay." Different words, different obligations, different timelines.
- A statute uses "employee" in Section 3 and "worker" in Section 4. These are presumed to describe different groups.
**Common misapplication:** Treating meaningful variation as mere stylistic choice. While drafting imperfections exist, the default presumption favors intentional variation.
---
### 6. Surplusage Canon
**Definition:** Every word in a statute is presumed to have meaning. Courts should avoid interpretations that render any word or phrase superfluous.
**Explanation:** If an interpretation makes certain words unnecessary or redundant, that interpretation is disfavored. The legislature is presumed not to have included meaningless language.
**Example:**
- Statute requires "clear and prominent" disclosure. "Clear" and "prominent" must mean different things -- "clear" relates to comprehensibility, "prominent" relates to visibility.
- If "appropriate technical and organizational measures" could be read as just "appropriate measures," the words "technical and organizational" are not surplus -- they specify the type of measures required.
**Common misapplication:** Taking the canon too far and manufacturing distinctions where none exist. Some statutory language is genuinely duplicative for emphasis or clarity.
---
### 7. Associated Words (Noscitur a Sociis)
**Definition:** Ambiguous words are interpreted in light of the words around them. A word's meaning is informed by its neighbors.
**Explanation:** When a word is ambiguous, look at the other words in the same list, sentence, or provision. The context of surrounding terms narrows the ambiguous word's meaning.
**Example:**
- Statute prohibits "guns, pistols, revolvers, and other dangerous weapons." The phrase "other dangerous weapons" is limited by its association with firearms -- it likely means other projectile weapons, not kitchen knives.
- A provision applies to "banks, credit unions, and similar financial institutions." "Similar financial institutions" is limited by association with deposit-taking entities.
**Common misapplication:** Using associated words to narrow a term that the legislature clearly intended to be broad. If the list is explicitly illustrative ("including but not limited to"), the associated-words canon has less force.
---
### 8. Ejusdem Generis
**Definition:** When a general term follows a list of specific terms, the general term is limited to items of the same kind as the specific terms.
**Explanation:** This is a specific application of the associated-words canon. A catchall phrase ("and other similar...") following a list of specifics is constrained by the nature of the listed items.
**Example:**
- "Automobiles, trucks, motorcycles, and other vehicles" -- "other vehicles" likely means motorized road vehicles, not aircraft or boats.
- "Fraud, embezzlement, theft, and other dishonest acts" -- "other dishonest acts" is limited to acts similar in nature to fraud, embezzlement, and theft.
**Common misapplication:** Applying ejusdem generis when there is no common genus. If the listed items are diverse and share no common characteristic, the general term may genuinely be broad.
| Scenario | Listed Items | General Term | Ejusdem Generis Applies? |
|----------|-------------|-------------|-------------------------|
| Common genus exists | "dogs, cats, hamsters" | "and other animals" | Yes -- likely means domestic pets |
| No common genus | "land, money, vehicles, intellectual property" | "and other assets" | Weak -- items too diverse to constrain |
| Explicit breadth | "any device or technology" | n/a | No -- no specific list to constrain |
---
## Purpose Canons
### 9. Presumption Against Ineffectiveness
**Definition:** Between two possible readings of a statute, prefer the one that gives the provision actual legal effect over the one that renders it meaningless or ineffective.
**Explanation:** Legislatures do not enact provisions intended to have no effect. If one interpretation makes a provision operational and another makes it a dead letter, choose the operational reading.
**Example:**
- A requirement to "implement appropriate security measures" can be read as either (a) a substantive obligation requiring actual security controls, or (b) a vague aspiration with no enforceable content. Prefer reading (a).
**Common misapplication:** Using this canon to expand a provision beyond its natural scope simply to give it "more" effect. The canon prevents nullification, not expansion.
---
### 10. Avoiding Absurdity
**Definition:** A statute should not be interpreted to produce absurd or unreasonable results if a sensible alternative interpretation exists.
**Explanation:** If the literal reading of a statute produces an outcome that no reasonable legislature would have intended, courts may depart from the literal text in favor of a reasonable interpretation. This canon is applied sparingly.
**Example:**
- A statute requires breach notification "within 72 hours of becoming aware of the breach." Literal reading might mean 72 hours from the moment any employee notices anything unusual. Reasonable reading: 72 hours from when the organization reasonably confirms a notifiable breach has occurred.
**Common misapplication:** Using "absurdity" as a cover for disagreeing with the statute's policy. The canon addresses genuinely irrational outcomes, not outcomes the reader finds undesirable.
---
### 11. Remedial Statutes Liberal Construction
**Definition:** Statutes designed to protect consumers, employees, the public, or other vulnerable groups should be construed liberally to advance their protective purpose.
**Explanation:** Consumer protection, environmental, and safety statutes are read broadly to achieve their remedial goals. Ambiguities are resolved in favor of the protected class.
**Example:**
- GDPR is a data protection statute. Ambiguities about scope should generally be resolved in favor of protecting data subjects.
- Employment discrimination statutes are construed broadly to cover more situations, not fewer.
**Common misapplication:** Applying liberal construction to override clear statutory limitations. Even remedial statutes have defined scope -- liberal construction operates within that scope, not beyond it.
---
### 12. Rule of Lenity
**Definition:** In criminal statutes or provisions imposing penalties, ambiguity is resolved in favor of the person subject to the penalty.
**Explanation:** When a penal provision is genuinely ambiguous -- where two reasonable readings exist -- the less punitive reading applies. This reflects the principle that individuals should have fair notice of what conduct is prohibited.
**Example:**
- A statute imposes fines for "unauthorized processing." If it is genuinely unclear whether a specific type of processing is "unauthorized," the ambiguity should be resolved against finding a violation.
**Common misapplication:** Invoking lenity when the statute is not genuinely ambiguous, or applying it to civil regulatory provisions that are not penal in nature.
| Provision Type | Lenity Applies? |
|---------------|----------------|
| Criminal sanctions | Yes |
| Administrative fines | Yes (in most jurisdictions) |
| Civil liability | Generally no |
| Regulatory obligations | Generally no |
| Injunctive relief | Generally no |
---
## Interpretation Sources Hierarchy
When canons alone do not resolve ambiguity, consult external sources in this order:
| Source | Use When | Reliability |
|--------|----------|-------------|
| Statutory text (other provisions) | Always -- the best context is the statute itself | Highest |
| Recitals / Preamble | Purpose is unclear from operative text | High for EU law; moderate elsewhere |
| Implementing regulations | Statute delegates detail to regulations | High within delegated authority |
| Case law | Courts have interpreted the provision | High within jurisdiction |
| Agency guidance | Agency has published interpretation | Moderate -- persuasive, not binding |
| Legislative history | Text is genuinely ambiguous | Low in textualist jurisdictions; moderate in purposivist |
| Academic commentary | Novel question with no authoritative guidance | Low -- persuasive only |
---
## Applying Canons in Practice
### Step-by-Step Process
1. **Read the plain text.** If clear and unambiguous, stop. The plain text controls.
2. **Check the definitions section.** Statutory definitions override ordinary meaning.
3. **Read surrounding provisions.** Apply the whole-act rule.
4. **Identify the ambiguity.** Precisely articulate what is unclear and why.
5. **Apply relevant canons.** Usually, more than one canon will be relevant.
6. **Check for canon conflicts.** Canons may point in different directions.
7. **Consult external sources.** Case law, regulations, guidance, in priority order.
8. **Document your reasoning.** Record which canons you applied and why.
---
## Canon Conflicts
Canons can conflict. When they do, use this resolution framework:
| Conflict | Resolution |
|----------|-----------|
| Textual canon vs textual canon | Weight both; consider which has stronger textual support |
| Textual canon vs purpose canon | Textual canons generally prevail; purpose canons are tiebreakers |
| Expressio unius vs ejusdem generis | Determine whether the list is exhaustive (expressio unius) or followed by a catchall (ejusdem generis) |
| Consistent usage vs meaningful variation | Determine whether the legislature used different terms deliberately or carelessly |
| Surplusage vs absurdity | If giving every word meaning produces absurdity, absurdity canon prevails |
| Lenity vs remedial statute | Context-dependent: penal provisions get lenity, protective provisions get liberal construction |
**Overarching principle:** No single canon is dispositive. Canons are interpretive tools, not rigid rules. The strongest interpretation is one supported by multiple canons pointing the same direction.
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 |