Import: Statute Analysis (Rafal Fryc)
What it does
This import adapter migrates a statute-analysis skill modelled on the Rafal Fryc methodology into the mini-claude-for-legal standard format. The Fryc methodology is a structured approach to legislative text: it treats a statute or regulation as a formal system, tracing definitions through their references, mapping the applicability scope before interpreting substantive obligations, and surfacing interpretive conflicts between provisions.
This methodology is particularly valuable for civil-law jurisdictions where statutes are the primary source of law (France, Lebanon, UAE Civil Code, EU Regulations) — unlike common-law jurisdictions where case law often fills the gaps that civil codes leave open.
Import config
| Field |
Source mapping |
Default if absent |
analysis_mode |
Legacy mode |
full (definition + scope + obligations + cross-references) |
definitional_chain |
Legacy trace_definitions boolean |
true |
cross_reference_map |
Legacy map_xrefs boolean |
true |
applicability_scope |
Legacy check_scope boolean |
true |
conflict_check |
Legacy check_conflicts boolean |
true |
output_format |
Legacy format |
statute_analysis_memo |
jurisdiction |
Legacy jurisdiction |
FR (Fryc's primary) |
language |
Legacy lang |
fr |
Dry-run preview
IMPORT PREVIEW — statute-analysis-rafal-fryc
Source shape : Statute analysis (Fryc methodology)
Mode : full
Definitional chain : traced
Cross-references : mapped
Applicability scope: checked
Conflict check : enabled
Language : French
Jurisdiction : France (civil law; override for other jurisdictions)
Output : statute_analysis_memo
Fryc analysis methodology (post-import)
Step 1 — Applicability scoping
Before analysing what the statute requires, determine who it applies to:
- Personal scope: which persons, entities, or roles does the statute address? What are the thresholds (e.g. company size, turnover, number of employees)?
- Material scope: which activities, transactions, or subject matter does it cover?
- Territorial scope: which geographic locations or establishments does it reach?
- Temporal scope: when did it enter into force? Are there transitional provisions? Has it been amended?
Step 2 — Definitional chain tracing
Statutes define key terms, but definitions reference other definitions. The Fryc approach traces the complete definitional chain:
DEFINED TERM → definition → references to OTHER defined terms
→ traces each referenced term in turn
→ flags circular definitions (common in EU regulations)
Example (GDPR): "personal data" → "identified or identifiable natural person" → "identifiable" → "identification by reference to an identifier" → back to "identifiers" (non-exhaustive list)
Step 3 — Obligation mapping
For each substantive provision:
- Who is the obligated person? (controller, processor, employer, operator)
- What is the obligation? (must, shall, is required to)
- What are the conditions? (triggers, thresholds, exceptions)
- What is the consequence of non-compliance? (penalty, sanction, nullity, liability)
Step 4 — Cross-reference mapping
Identify internal and external cross-references:
- Internal: "as defined in Article X", "subject to Article Y"
- External: references to other statutes, EU instruments, implementing regulations
- Flag any reference to a provision that has been repealed, amended, or is pending
Step 5 — Interpretive conflict identification
- Are there two provisions that apply to the same situation but point in different directions?
- Does a later provision override an earlier one (lex posterior)?
- Does a specific provision override a general one (lex specialis)?
- Are there gaps (situations the statute does not address) that must be filled by analogy or judicial construction?
Output schema
STATUTE ANALYSIS MEMO
Instrument : [statute name, number, date]
Jurisdiction : [jurisdiction]
Analysis date : [date]
1. APPLICABILITY SCOPE
Personal scope : [who it applies to]
Material scope : [what it covers]
Territorial scope: [where it applies]
In force since : [date]; last amended: [date]
2. KEY DEFINITIONS
[Term] : [definition + chain trace]
...
3. OBLIGATION MAP
[Party] must [obligation] when [conditions] under Art [X]
Penalty for non-compliance: [consequence]
...
4. CROSS-REFERENCES
Internal: [list]
External: [list; flag repealed/amended]
5. INTERPRETIVE ISSUES
[Conflict or gap description]
Recommended approach: [interpretation method]
Jurisdictional notes
| Jurisdiction |
Civil-law interpretation rules |
| France |
Code Civil Art 4: judge cannot refuse to decide even if law is silent; systematic interpretation preferred |
| Lebanon |
Code of Obligations (French-inspired); Arabic and French versions both official |
| UAE Civil Code |
Federal Law 5/1985; good faith (Art 246) central; Arabic prevails over English |
| EU Regulations |
Teleological and comparative interpretation across 24 official languages; CJEU rulings binding |
| Poland |
Constitutional Tribunal doctrine; EU law primacy since accession |
Failure modes
| Error |
Likely cause |
Resolution |
definition_chain_circular |
Statute has circular definitions |
Flag and note; trace as far as possible |
cross_reference_broken |
References to repealed provisions |
Flag as "REPEALED — verify current equivalent" |
applicability_unclear |
Statute silent on scope |
Apply ejusdem generis / in dubio mitius as appropriate |
jurisdiction_mismatch |
Fryc (civil law) methodology applied to common law statute |
Note differences; statute interpretation rules differ |
Related skills
- [[import-legal-risk-assessment-zacharie-laik]]
- [[import-contract-review-anthropic]]
- [[import-legal-simulation-patrick-munro]]
- [[kb-gdpr-data-protection]]
- [[import-legal-risk-assessment-anthropic]]
1---2name: import-statute-analysis-rafal-fryc3description: Use when migrating the Rafal Fryc statute-analysis methodology into the mini-claude-for-legal format. This adapter preserves structured legislative text analysis — section-by-section decomposition, applicability scoping, definitional chain tracing, and cross-reference mapping — mapped into the standard skill model. Strong for civil-code jurisdictions (France, Lebanon, UAE onshore, Poland) and EU regulatory instruments. Triggers on import of any statute-analysis skill attributed to the Fryc approach.4license: MIT5metadata:6 id: import.statute-analysis-rafal-fryc7 category: import8 jurisdictions: [FR, LB, UAE, EU, PL, __multi__]9 priority: P310 intent: [__import__, statute-analysis, legislative-analysis, migration, civil-law]11 related: [import-legal-risk-assessment-zacharie-laik, import-contract-review-anthropic, import-legal-simulation-patrick-munro, kb-gdpr-data-protection]12 source: https://skillmd.com/skills/sboghossian-mini-claude-for-legal/import-statute-analysis-rafal-fryc13 upstream: Louis — HAQQ Legal AI (github.com/sboghossian/mini-claude-for-legal)14 version: "1.0"15---1617# Import: Statute Analysis (Rafal Fryc)1819## What it does2021This import adapter migrates a **statute-analysis skill modelled on the Rafal Fryc methodology** into the `mini-claude-for-legal` standard format. The Fryc methodology is a structured approach to legislative text: it treats a statute or regulation as a formal system, tracing definitions through their references, mapping the applicability scope before interpreting substantive obligations, and surfacing interpretive conflicts between provisions.2223This methodology is particularly valuable for civil-law jurisdictions where statutes are the primary source of law (France, Lebanon, UAE Civil Code, EU Regulations) — unlike common-law jurisdictions where case law often fills the gaps that civil codes leave open.2425## Import config2627| Field | Source mapping | Default if absent |28|---|---|---|29| `analysis_mode` | Legacy `mode` | `full` (definition + scope + obligations + cross-references) |30| `definitional_chain` | Legacy `trace_definitions` boolean | `true` |31| `cross_reference_map` | Legacy `map_xrefs` boolean | `true` |32| `applicability_scope` | Legacy `check_scope` boolean | `true` |33| `conflict_check` | Legacy `check_conflicts` boolean | `true` |34| `output_format` | Legacy `format` | `statute_analysis_memo` |35| `jurisdiction` | Legacy `jurisdiction` | `FR` (Fryc's primary) |36| `language` | Legacy `lang` | `fr` |3738## Dry-run preview3940```41IMPORT PREVIEW — statute-analysis-rafal-fryc42Source shape : Statute analysis (Fryc methodology)43Mode : full44Definitional chain : traced45Cross-references : mapped46Applicability scope: checked47Conflict check : enabled48Language : French49Jurisdiction : France (civil law; override for other jurisdictions)50Output : statute_analysis_memo51```5253## Fryc analysis methodology (post-import)5455### Step 1 — Applicability scoping56Before analysing what the statute requires, determine who it applies to:57- **Personal scope**: which persons, entities, or roles does the statute address? What are the thresholds (e.g. company size, turnover, number of employees)?58- **Material scope**: which activities, transactions, or subject matter does it cover?59- **Territorial scope**: which geographic locations or establishments does it reach?60- **Temporal scope**: when did it enter into force? Are there transitional provisions? Has it been amended?6162### Step 2 — Definitional chain tracing63Statutes define key terms, but definitions reference other definitions. The Fryc approach traces the complete definitional chain:6465```66DEFINED TERM → definition → references to OTHER defined terms67 → traces each referenced term in turn68 → flags circular definitions (common in EU regulations)69```7071Example (GDPR): "personal data" → "identified or identifiable natural person" → "identifiable" → "identification by reference to an identifier" → back to "identifiers" (non-exhaustive list)7273### Step 3 — Obligation mapping74For each substantive provision:75- Who is the **obligated person**? (controller, processor, employer, operator)76- What is the **obligation**? (must, shall, is required to)77- What are the **conditions**? (triggers, thresholds, exceptions)78- What is the **consequence** of non-compliance? (penalty, sanction, nullity, liability)7980### Step 4 — Cross-reference mapping81Identify internal and external cross-references:82- Internal: "as defined in Article X", "subject to Article Y"83- External: references to other statutes, EU instruments, implementing regulations84- Flag any reference to a provision that has been repealed, amended, or is pending8586### Step 5 — Interpretive conflict identification87- Are there two provisions that apply to the same situation but point in different directions?88- Does a later provision override an earlier one (lex posterior)?89- Does a specific provision override a general one (lex specialis)?90- Are there gaps (situations the statute does not address) that must be filled by analogy or judicial construction?9192## Output schema9394```95STATUTE ANALYSIS MEMO9697Instrument : [statute name, number, date]98Jurisdiction : [jurisdiction]99Analysis date : [date]1001011. APPLICABILITY SCOPE102 Personal scope : [who it applies to]103 Material scope : [what it covers]104 Territorial scope: [where it applies]105 In force since : [date]; last amended: [date]1061072. KEY DEFINITIONS108 [Term] : [definition + chain trace]109 ...1101113. OBLIGATION MAP112 [Party] must [obligation] when [conditions] under Art [X]113 Penalty for non-compliance: [consequence]114 ...1151164. CROSS-REFERENCES117 Internal: [list]118 External: [list; flag repealed/amended]1191205. INTERPRETIVE ISSUES121 [Conflict or gap description]122 Recommended approach: [interpretation method]123```124125## Jurisdictional notes126127| Jurisdiction | Civil-law interpretation rules |128|---|---|129| France | Code Civil Art 4: judge cannot refuse to decide even if law is silent; systematic interpretation preferred |130| Lebanon | Code of Obligations (French-inspired); Arabic and French versions both official |131| UAE Civil Code | Federal Law 5/1985; good faith (Art 246) central; Arabic prevails over English |132| EU Regulations | Teleological and comparative interpretation across 24 official languages; CJEU rulings binding |133| Poland | Constitutional Tribunal doctrine; EU law primacy since accession |134135## Failure modes136137| Error | Likely cause | Resolution |138|---|---|---|139| `definition_chain_circular` | Statute has circular definitions | Flag and note; trace as far as possible |140| `cross_reference_broken` | References to repealed provisions | Flag as "REPEALED — verify current equivalent" |141| `applicability_unclear` | Statute silent on scope | Apply ejusdem generis / in dubio mitius as appropriate |142| `jurisdiction_mismatch` | Fryc (civil law) methodology applied to common law statute | Note differences; statute interpretation rules differ |143144## Related skills145146- [[import-legal-risk-assessment-zacharie-laik]]147- [[import-contract-review-anthropic]]148- [[import-legal-simulation-patrick-munro]]149- [[kb-gdpr-data-protection]]150- [[import-legal-risk-assessment-anthropic]]