statute-analysis
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese⚠️ 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
法律层级
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.
理解法律来源的层级是法规分析的基础。
| 来源 | 制定主体 | 权威性 | 示例 |
|---|---|---|---|
| 宪法 | 主权体/人民 | 最高 | 美国宪法、欧盟条约 |
| 成文法规 | 立法机构 | 一级立法 | GDPR、《清洁空气法》、《AI法案》 |
| 行政规章 | 行政机关 | 授权立法 | FDA 21 CFR、FTC规则 |
| 规程 | 机关或法院 | 程序/解释性 | 《联邦民事诉讼规则》 |
| 指引文件 | 行政机关 | 无约束力，仅具说服力 | FDA指引文件、CNIL指南 |
| 判例法 | 法院 | 在管辖范围内具有约束力 | 最高法院先例 |
核心原则： 高阶来源优先于低阶来源。行政规章不得超越法规授权。指引文件不得创设未基于法规的新义务。
Preliminary Steps
前期步骤
Before interpreting any statutory provision, complete these checks:
- 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).
- Understand the regulatory ecosystem -- What regulations, rules, and guidance implement this statute? Map the full hierarchy.
- Browse the full structure -- Read the table of contents, definitions section, scope provisions, and transitional articles before diving into specific sections.
- Identify the definitions section -- Almost all statutes define key terms. These definitions override ordinary meaning.
- Check effective dates -- Different provisions may have different effective dates. Map the compliance timeline.
- 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).
解读任何法规条款前，请完成以下检查：
- 验证时效性与效力状态 — 这是当前生效版本吗？检查修正案、废止条款或日落条款。使用官方来源（政府公报、EUR-Lex、congress.gov）。
- 理解监管生态 — 哪些规章、规程和指引文件是本法规的配套实施文件？梳理完整的层级关系。
- 浏览整体结构 — 在深入具体章节前，先阅读目录、定义部分、范围条款及过渡条款。
- 定位定义章节 — 几乎所有法规都会定义关键术语。这些定义优先于普通含义。
- 核查生效日期 — 不同条款可能有不同的生效日期。梳理合规时间线。
- 明确自身角色 — 法规会根据读者的角色施加不同义务（例如，欧盟《AI法案》中的“提供者”vs“部署者”，GDPR中的“控制者”vs“处理者”）。
Tools
工具
Statute Keyword Analyzer
法规关键词分析器
Scans statute text for operative keywords and classifies obligations, permissions, conditions, and exemptions.
bash
undefined扫描法规文本，识别关键操作术语，并对义务、许可、条件及豁免进行分类。
bash
undefinedAnalyze a statute file
分析法规文件
python scripts/statute_keyword_analyzer.py --input statute.txt
python scripts/statute_keyword_analyzer.py --input statute.txt
Analyze with JSON output
生成JSON格式输出
python scripts/statute_keyword_analyzer.py --input regulation.txt --json
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..."
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
undefinedpython scripts/statute_keyword_analyzer.py --input statute.txt --output analysis.json
undefinedRequirement Classifier
要求分类器
Classifies statutory requirements by type, implementation team, enforcement mechanism, and penalty.
bash
undefined按类型、实施团队、执行机制及处罚方式对法规要求进行分类。
bash
undefinedClassify requirements from a JSON list
对JSON列表中的要求进行分类
python scripts/requirement_classifier.py --input requirements.json
python scripts/requirement_classifier.py --input requirements.json
Classify with JSON output
生成JSON格式输出
python scripts/requirement_classifier.py --input requirements.json --json
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"
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
---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" |
法规定义决定术语含义。注意定义中使用的动词：
| 动词 | 类型 | 含义 | 示例 |
|---|---|---|---|
| "means" | 穷尽式 | 定义完整，无其他含义适用 | "'Personal data' means any information relating to an identified or identifiable natural person" |
| "includes" | 示例式 | 定义仅提供示例，不限于所列内容 | "'Processing' includes collection, recording, organization, structuring..." |
| "does not include" | 排除式 | 明确将某些内容排除在范围外 | "'Consumer' does not include a natural person acting in a commercial or employment context" |
| "refers to" | 指向式 | 纳入外部定义 | "'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 |
| 术语 | 分类 | 法律效力 |
|---|---|---|
| shall | 强制性 | 创设义务，必须执行 |
| must | 强制性 | 在现代立法中与“shall”含义相同 |
| may | 许可性 | 创设许可，可选择执行 |
| may not | 禁止性 | 创设禁令 |
| and | 并列性 | 所列所有项均需满足 |
| or | 选择性 | 满足所列任意一项即可 |
| unless | 例外性 | 当条件满足时，规则不适用 |
| except | 例外性 | 将特定内容从规则中排除 |
| subject to | 条件性 | 规则适用，但受另一条款修改 |
| notwithstanding | 优先性 | 本条款优先于冲突条款 |
| provided that | 条件性 | 添加必须满足的要求 |
| if...then | 条件性 | 触发条件及相应后果 |
| upon | 时间触发 | 事件发生时需采取行动 |
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 |
这一区别决定了是否需要满足所有条件，还是仅需满足任意单个条件。
| 模式 | 解读方式 | 实际影响 |
|---|---|---|
| "A, B, and C" | 需满足全部三项 | 必须符合每一项要素 |
| "A, B, or C" | 满足任意一项即可 | 只需符合其中一项要素 |
| "A, B, and/or C" | 含义模糊 | 标记待澄清，结合上下文分析 |
| "both A and B" | 明确并列 | 必须同时满足两项 |
| "either A or B" | 明确选择 | 满足其中一项即可 |
| 序列逗号歧义 | 依赖上下文 | 运用整体法案规则保持一致性 |
Canons of Construction
法律解释准则
See for the complete 12-canon reference.
references/canons_of_construction.md完整的12项准则参考请见 。
references/canons_of_construction.mdQuick 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 liberally | Consumer protection, safety statutes |
| Rule of Lenity | Ambiguity favors the regulated party | Criminal or penalty provisions |
| 准则 | 核心规则 | 适用场景 |
|---|---|---|
| 一般术语准则 | 一般术语取普通含义 | 默认解读方式 |
| 明示排除默示准则 | 列明一项即排除其他 | 无兜底条款的具体列表 |
| 整体法案规则 | 解读条款需保持一致 | 章节间存在明显冲突 |
| 一致用法规则 | 同一术语含义始终一致 | 术语多次出现 |
| 差异含义规则 | 不同术语含义不同 | 使用相似但有区别的术语 |
| 无冗余准则 | 每个字词均有意义，无多余内容 | 试图将某些字词视为冗余时 |
| 同类解释准则 | 术语含义由其上下文关联项决定 | 列表中存在模糊术语 |
| 同类延伸准则 | 一般术语跟随特定术语，含义受限 | 出现“……及其他类似”的表述 |
| 有效解读准则 | 优先选择能赋予条款效力的解读 | 存在两种可能的解读方式 |
| 避免荒谬准则 | 拒绝荒谬的解读结果 | 字面解读会产生无意义的结果 |
| 救济性法规宽松解读准则 | 宽松解读救济性法规 | 消费者保护、安全类法规 |
| 从宽解释准则 | 模糊条款有利于被监管方 | 刑事或处罚类条款 |
Interpretation Sources
解读依据
When statutory text is ambiguous, consult sources in this order:
| Priority | Source | Weight | Where to Find |
|---|---|---|---|
| 1 | Statutory text itself | Controlling | Official gazette, codified law |
| 2 | Definitions section | Controlling | Usually first articles/sections |
| 3 | Legislative purpose (recitals, preamble) | Strong | Preamble, "Whereas" clauses |
| 4 | Canons of construction | Strong | Legal treatises, case law |
| 5 | Case law interpreting the provision | Strong-to-moderate | Court databases |
| 6 | Agency regulations implementing statute | Moderate | Agency websites, CFR |
| 7 | Agency guidance and FAQs | Persuasive only | Agency websites |
| 8 | Legislative history | Weak (varies by jurisdiction) | Congressional record, Hansard |
| 9 | Academic commentary | Persuasive only | Legal journals |
当法规文本存在歧义时，按以下优先级参考依据：
| 优先级 | 来源 | 权重 | 获取渠道 |
|---|---|---|---|
| 1 | 法规文本本身 | 具有约束力 | 官方公报、编纂法律 |
| 2 | 定义章节 | 具有约束力 | 通常位于开篇条款 |
| 3 | 立法目的（叙言、序言） | 权重高 | 序言、“鉴于”条款 |
| 4 | 法律解释准则 | 权重高 | 法律专著、判例法 |
| 5 | 解读该条款的判例法 | 权重高至中等 | 法院数据库 |
| 6 | 实施法规的行政规章 | 权重中等 | 机关网站、CFR |
| 7 | 行政指引及常见问题 | 仅具说服力 | 机关网站 |
| 8 | 立法历史 | 权重低（因司法管辖区而异） | 国会记录、Hansard |
| 9 | 学术评论 | 仅具说服力 | 法律期刊 |
Requirement Classification
要求分类
Every statutory requirement maps to an implementation category:
| Type | Description | Typical Owner | Example |
|---|---|---|---|
| Disclosure | Information must be provided to someone | Legal / Compliance | Privacy notice requirements |
| Operational | Process or procedure must exist | Operations / Compliance | Record-keeping obligations |
| Technical | System capability or safeguard required | Engineering | Encryption, access controls |
| UI/Design | User interface must include specific elements | Product / Design | Consent mechanisms, opt-out buttons |
| Organizational | Governance structure or role required | Management / HR | Appointing a DPO, board oversight |
| Documentation | Written records must be maintained | Legal / Compliance | Impact assessments, audit trails |
| Reporting | Information must be submitted to authority | Legal / Compliance | Breach notification, annual reports |
每项法规要求都对应一个实施类别：
| 类型 | 描述 | 典型负责方 | 示例 |
|---|---|---|---|
| 披露 | 需向特定对象提供信息 | 法务/合规部 | 隐私告知要求 |
| 运营 | 需建立流程或程序 | 运营/合规部 | 记录留存义务 |
| 技术 | 需具备系统能力或保障措施 | 工程部 | 加密、访问控制 |
| UI/设计 | 用户界面需包含特定元素 | 产品/设计部 | 同意机制、退订按钮 |
| 组织 | 需建立治理结构或角色 | 管理层/人力资源部 | 任命DPO、董事会监督 |
| 文档 | 需留存书面记录 | 法务/合规部 | 影响评估、审计轨迹 |
| 报告 | 需向主管机关提交信息 | 法务/合规部 | 数据泄露通知、年度报告 |
Cross-Jurisdictional Analysis
跨司法管辖区分析
When requirements from multiple jurisdictions apply:
- Map applicable jurisdictions -- Where are your users, your entity, and your data?
- Identify overlapping requirements -- Many frameworks share common obligations.
- Find the highest common denominator -- Design for the strictest requirement that satisfies all jurisdictions.
- Flag conflicts -- Where requirements genuinely conflict, document the conflict and seek legal advice.
- Check preemption -- Federal law may preempt state law; EU regulations may preempt member state law.
当多个司法管辖区的要求同时适用时：
- 梳理适用的司法管辖区 — 你的用户、实体及数据位于何处？
- 识别重叠要求 — 许多框架共享通用义务。
- 找到最高共同标准 — 按最严格的要求设计，以满足所有司法管辖区。
- 标记冲突点 — 若要求确实存在冲突，记录冲突并寻求法律建议。
- 核查优先效力 — 联邦法律可能优先于州法律；欧盟规章可能优先于成员国法律。
Enforcement Analysis
执行分析
For each statutory requirement, assess enforcement risk:
| Factor | Assessment Questions |
|---|---|
| Enforcement authority | Which agency enforces? How active are they? |
| Penalty types | Civil fines, criminal penalties, administrative sanctions? |
| Penalty severity | Fixed amounts, percentage of turnover, per-violation? |
| Cure periods | Is there a right to cure before penalties apply? |
| Private right of action | Can individuals sue for violations? |
| Enforcement history | Has this provision been actively enforced? |
| Regulatory guidance | Has the agency clarified enforcement priorities? |
针对每项法规要求，评估执行风险：
| 因素 | 评估问题 |
|---|---|
| 执行机关 | 由哪个机关执行？其执行活跃度如何？ |
| 处罚类型 | 是否有民事罚款、刑事处罚、行政制裁？ |
| 处罚严重程度 | 固定金额、营业额百分比、按违规次数计算？ |
| 整改期 | 处罚前是否有整改权利？ |
| 私人诉权 | 个人能否因违规提起诉讼？ |
| 执行历史 | 该条款是否被积极执行过？ |
| 监管指引 | 机关是否明确了执行优先级？ |
Reference Guides
参考指南
| Guide | Path | Description |
|---|---|---|
| Canons of Construction | | 12 canons with definitions, examples, and misapplication warnings |
| Statutory Structure | | How statutes are organized, effective dates, preemption, enforcement |
| 指南 | 路径 | 描述 |
|---|---|---|
| 法律解释准则 | | 12项准则，含定义、示例及误用警示 |
| 法规结构 | | 法规的组织方式、生效日期、优先效力、执行机制 |
Workflows
工作流程
Workflow 1: First Reading of a New Statute
流程1：新法规初读
- Browse the full table of contents and structure.
- Read the definitions section and scope provisions.
- Check effective dates and transitional provisions.
- Identify your role under the statute.
- Run on the full text.
scripts/statute_keyword_analyzer.py - Review the obligation/permission/exception map.
- Identify provisions that apply to your role.
- Validation: Definitions cataloged, role identified, key obligations listed.
- 浏览完整目录及结构。
- 阅读定义章节及范围条款。
- 核查生效日期及过渡条款。
- 明确自身在法规中的角色。
- 对全文运行 。
scripts/statute_keyword_analyzer.py - 审查义务/许可/例外映射表。
- 识别适用于自身角色的条款。
- 验证： 已梳理所有定义、明确角色、列出关键义务。
Workflow 2: Requirement Extraction and Classification
流程2：要求提取与分类
- Extract all provisions containing "shall," "must," or mandatory language.
- For each requirement, identify: who (subject), what (action), when (trigger/deadline), how (standard).
- Run on the extracted requirements.
scripts/requirement_classifier.py - Review the implementation matrix.
- Assign each requirement to an implementation team.
- Prioritize by enforcement risk and deadline.
- Validation: Every mandatory provision classified, assigned, and prioritized.
- 提取所有包含“shall”“must”或强制性表述的条款。
- 针对每项要求，明确：主体（谁）、动作（做什么）、触发条件/截止日期（何时）、标准（怎么做）。
- 对提取的要求运行 。
scripts/requirement_classifier.py - 审查实施矩阵。
- 将每项要求分配给对应实施团队。
- 按执行风险及截止日期排序优先级。
- 验证： 所有强制性条款均已分类、分配并确定优先级。
Workflow 3: Cross-Reference Resolution
流程3：交叉引用解析
- Identify all cross-references in the target provision ("subject to Article X," "as defined in Section Y").
- Read each referenced provision in full.
- Determine whether the cross-reference modifies, limits, or supplements the target provision.
- Check for circular references or chains (A references B which references C).
- Document the complete picture -- the target provision as modified by all cross-references.
- Validation: All cross-references resolved; no orphan references.
- 识别目标条款中的所有交叉引用（“受第X条约束”“如第Y节所定义”）。
- 完整阅读每个被引用的条款。
- 确定交叉引用是否修改、限制或补充目标条款。
- 检查是否存在循环引用或链式引用（A引用B，B引用C）。
- 记录完整内容 — 即经所有交叉引用修改后的目标条款。
- 验证： 所有交叉引用均已解析，无孤立引用。
Troubleshooting
故障排查
| Problem | Likely Cause | Resolution |
|---|---|---|
| Term not defined in statute | Legislature used ordinary meaning | Apply general-terms canon; check case law for judicial definitions |
| "And/or" ambiguity | Drafting imprecision | Check legislative history; apply whole-act rule; flag for legal review |
| Conflicting provisions | Later provision may override earlier | Check for "notwithstanding" clauses; apply later-in-time rule |
| Undefined threshold | Delegated to regulation | Check implementing regulations and agency guidance |
| Provision seems to have no effect | May be transitional or placeholder | Check effective dates and amendment history |
| Cross-reference to repealed section | Statute not updated after amendment | Check saving clauses; apply presumption against ineffectiveness |
| 问题 | 可能原因 | 解决方案 |
|---|---|---|
| 法规中未定义某术语 | 立法机构使用了普通含义 | 运用一般术语准则；核查判例法中的司法定义 |
| “And/or”含义模糊 | 起草不够精准 | 核查立法历史；运用整体法案规则；标记待法律审查 |
| 条款冲突 | 后出台的条款可能优先于先出台的 | 检查是否有“notwithstanding”条款；运用后法优先规则 |
| 阈值未定义 | 授权给规章明确 | 核查配套实施规章及机关指引 |
| 条款似乎无效力 | 可能是过渡性或占位条款 | 核查生效日期及修正案历史 |
| 引用已废止章节 | 法规修订后未更新 | 核查保留条款；运用避免无效解读的推定 |
Success Criteria
成功标准
| Criterion | Target |
|---|---|
| All defined terms cataloged | 100% of definitions section mapped |
| Obligations extracted | Every "shall/must" provision identified |
| Requirements classified | Each requirement has type, owner, enforcement, and priority |
| Cross-references resolved | No unresolved references remain |
| Enforcement risk assessed | Every material obligation has enforcement analysis |
| Implementation matrix complete | Requirements mapped to teams with timelines |
| 标准 | 目标 |
|---|---|
| 已梳理所有定义术语 | 100%覆盖定义章节内容 |
| 已提取所有义务 | 识别所有含“shall/must”的条款 |
| 已分类所有要求 | 每项要求均有类型、负责方、执行方式及优先级 |
| 已解析所有交叉引用 | 无未解决的引用 |
| 已评估所有执行风险 | 所有重大义务均已完成执行分析 |
| 实施矩阵完整 | 要求已映射至对应团队及时间线 |
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
反模式
| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Reading a section in isolation | Statutes are interconnected; isolated reading misses cross-references, definitions, and scope limitations | Always read definitions, scope, and cross-referenced provisions before interpreting |
| Treating guidance as law | Agency guidance is non-binding and can change; building compliance solely on guidance creates risk | Use guidance to inform interpretation but anchor compliance to statutory text |
| Ignoring "what the statute doesn't say" | Silence can mean permission, delegation, or an oversight; assuming the statute covers everything leads to compliance gaps | Affirmatively check: does the statute address this scenario? If not, analyze why and what fills the gap |
| Applying one jurisdiction's interpretation to another | "Personal data" in GDPR is not identical to "personal information" in CCPA; cross-pollinating definitions creates errors | Analyze each statute independently using its own definitions and interpretive framework |
| Skipping the definitions section | Statutory definitions override ordinary meaning; missing them leads to fundamental misreadings | Always read the definitions section first, before any substantive analysis |
| 反模式 | 失败原因 | 更佳方案 |
|---|---|---|
| 孤立阅读某章节 | 法规条款相互关联；孤立阅读会遗漏交叉引用、定义及范围限制 | 解读前始终先阅读定义、范围及交叉引用的条款 |
| 将指引文件视为法律 | 行政指引无约束力且可能变更；仅基于指引构建合规体系会产生风险 | 用指引辅助解读，但需以法规文本为合规核心 |
| 忽略“法规未提及的内容” | 沉默可能意味着许可、授权或疏漏；假设法规涵盖所有场景会导致合规缺口 | 主动核查：法规是否涉及该场景？若未涉及，分析原因及填补缺口的依据 |
| 将一个司法管辖区的解读套用至另一个 | GDPR中的“Personal data”与CCPA中的“personal information”含义不同；交叉套用定义会引发错误 | 独立分析每项法规，使用其自身定义及解读框架 |
| 跳过定义章节 | 法规定义优先于普通含义；遗漏定义会导致根本性误读 | 始终先阅读定义章节，再进行任何实质性分析 |
Tool Reference
工具参考
| Tool | Input | Output | Use Case |
|---|---|---|---|
| Statute text file or inline text | Obligation/permission/exception map | First pass analysis of any legislative text |
| List of requirements (text or JSON) | Implementation matrix with types, teams, enforcement | Converting statutory obligations to actionable implementation tasks |
| 工具 | 输入 | 输出 | 使用场景 |
|---|---|---|---|
| 法规文本文件或内联文本 | 义务/许可/例外映射表 | 对任何立法文本进行初步分析 |
| 要求列表（文本或JSON格式） | 含类型、负责团队、执行方式的实施矩阵 | 将法规义务转化为可执行的实施任务 |