Statute Briefer (MAPS + RULES)
Produce structured statute/Act briefs that (a) map the architecture of the entire statute/Act and (b) express operative provisions as rule-modules. Optionally apply provisions to scenarios with verbatim quotations.
Input Modes
Mode A: Text-only briefing
- Required: Statutory text (or delimited excerpt)
- Optional: Citation info, version type (enacted/codified/amendment), length constraint (short/standard/long)
Mode B: Scenario-driven briefing
- Required: Statutory text + scenario description
- Optional: Decision posture (advice/compliance/litigation), length constraint
If citation/version missing, label brief as "text-as-provided" without recency claims.
Output Structure
Every brief produces two layers. In Mode B, prepend the Scenario Module.
Scenario Module (Mode B only)
See references/scenario-template.md for detailed template.
Six components:
- Scenario synopsis – Legally salient facts only
- Issues framed as statutory questions – Frame disputes as statutory interpretation questions
- Relevant excerpts (verbatim) – Block-quoted text with pinpoint cites; include adjacent definitions/exceptions
- Application map (statute-to-facts) – For each issue: elements met, unclear, or disputed; identify missing facts
- Context map (where excerpts live) – Title/Chapter/Section path for each excerpt
- Not used but structurally important – Major Act components not triggered by scenario
MAPS (System-Level Map)
Five components:
- Citation and text status – Citation block or "citation not provided"; note if partial text
- Purpose – Quote express purpose/findings if present (with cite); otherwise label as inference
- Structure map (entire Act) – Hierarchical outline with functional labels ("definitions," "prohibition," "enforcement," etc.); for large statutes, provide major-divisions overview plus zoomed detail
- Scope and coverage – Covered actors, conduct, geography, time, jurisdictional hooks, explicit exclusions
- Definitions and interpretive rules – Defined terms index; interpretive provisions; cross-references
RULES (Operational Modules)
For each major operative provision (or scenario-relevant provisions), produce a rule-module.
See references/rule-module-template.md for detailed template.
Rule-Module required fields:
- Provision – Pinpoint cite
- Trigger conditions (elements) – What activates the provision
- Legal effect – Command / permission / prohibition / entitlement
- Exceptions / defenses / safe harbors – Carve-outs from the rule
- Procedure / decision-maker – Deadlines, notice, standards
- Consequences – Penalties, remedies, invalidity, loss of benefits
- Forum / enforcer – Agency, court, private plaintiff
- Interaction rules – Preemption/savings, severability, effective date, cross-references
Mandatory Constraints
Verbatim Discipline
- Never invent statutory language
- Mark all quotations explicitly with pinpoint cites
- If text is missing, say so and proceed with what is provided
Cross-Reference Discipline
- When statute defines a term used in operative provision, incorporate that definition
- Flag external cross-references: "cross-reference not included in provided materials"
Separation of Layers
- Keep "Quoted Text" separate from "Explanation/Translation"
- Use block quotes or clear markers
No Premature Narrowing
- Even in scenario mode, include MAPS structure map at major-division level
Selection Rules
Mode A (no scenario): Major operative provisions = primary prohibitions/requirements/entitlements + enforcement/remedies + key definitions + preemption/savings/severability/venue
Mode B (with scenario): Prioritize provisions governing scenario issues + conditioning definitions/enforcement/exceptions. Still include full structure map.
Length Control
| Constraint |
Structure Map |
Rule-Modules |
Definitions |
| Short |
Spine outline only |
Most relevant only |
Key scope terms only |
| Standard |
Major divisions complete |
Core operative provisions |
Terms affecting scope |
| Long |
Full detail |
All operative provisions |
Comprehensive index |
Uncertainty Handling
- Insufficient facts → Label "Fact needed: [specific missing fact]"
- Partial statute → Label "based on provided excerpt only"
- Never fill in absent provisions
Exact Headings (for parsing)
Scenario Module
Scenario synopsis
Issues framed as statutory questions
Relevant excerpts (verbatim)
Application map (statute-to-facts)
Context map (where excerpts live)
Not used but structurally important
MAPS
Citation and text status
Purpose
Structure map (entire Act)
Scope and coverage
Definitions and interpretive rules
RULES
Rule-Module: [Provision cite]
Boundaries
- Briefs statutes and legislative Acts only
- No policy commentary unless asked
- No grading or pedagogy commentary
- No generating new statutory text
- No case citations unless explicitly requested; may note "interpretive pressure points" as ambiguity flags
1---2name: statute-briefer3description: Brief statutes and legislative Acts using the MAPS + RULES framework. Use when briefing statutes, analyzing legislative text, mapping statutory structure, extracting rule-modules from provisions, applying statutes to scenarios, or any statutory analysis task. Triggers include "brief this statute," "analyze this Act," "map the statute," "apply [statute] to [scenario]," "what are the elements of [provision]," "statutory analysis," or references to codified sections (such as 42 U.S.C. sections or Texas Health & Safety Code). Supports two modes - (A) text-only briefing for structural analysis, and (B) scenario-driven briefing that applies statutory provisions to specific facts.4---5
6# Statute Briefer (MAPS + RULES)
7
8Produce structured statute/Act briefs that (a) map the architecture of the entire statute/Act and (b) express operative provisions as rule-modules. Optionally apply provisions to scenarios with verbatim quotations.
9
10## Input Modes
11
12**Mode A: Text-only briefing**
13- Required: Statutory text (or delimited excerpt)
14- Optional: Citation info, version type (enacted/codified/amendment), length constraint (short/standard/long)
15
16**Mode B: Scenario-driven briefing**
17- Required: Statutory text + scenario description
18- Optional: Decision posture (advice/compliance/litigation), length constraint
19
20If citation/version missing, label brief as "text-as-provided" without recency claims.
21
22## Output Structure
23
24Every brief produces two layers. In Mode B, prepend the Scenario Module.
25
26### Scenario Module (Mode B only)
27
28See [references/scenario-template.md](references/scenario-template.md) for detailed template.
29
30Six components:
311. **Scenario synopsis** – Legally salient facts only
322. **Issues framed as statutory questions** – Frame disputes as statutory interpretation questions
333. **Relevant excerpts (verbatim)** – Block-quoted text with pinpoint cites; include adjacent definitions/exceptions
344. **Application map (statute-to-facts)** – For each issue: elements met, unclear, or disputed; identify missing facts
355. **Context map (where excerpts live)** – Title/Chapter/Section path for each excerpt
366. **Not used but structurally important** – Major Act components not triggered by scenario
37
38### MAPS (System-Level Map)
39
40Five components:
411. **Citation and text status** – Citation block or "citation not provided"; note if partial text
422. **Purpose** – Quote express purpose/findings if present (with cite); otherwise label as inference
433. **Structure map (entire Act)** – Hierarchical outline with functional labels ("definitions," "prohibition," "enforcement," etc.); for large statutes, provide major-divisions overview plus zoomed detail
444. **Scope and coverage** – Covered actors, conduct, geography, time, jurisdictional hooks, explicit exclusions
455. **Definitions and interpretive rules** – Defined terms index; interpretive provisions; cross-references
46
47### RULES (Operational Modules)
48
49For each major operative provision (or scenario-relevant provisions), produce a rule-module.
50
51See [references/rule-module-template.md](references/rule-module-template.md) for detailed template.
52
53**Rule-Module required fields:**
541. **Provision** – Pinpoint cite
552. **Trigger conditions (elements)** – What activates the provision
563. **Legal effect** – Command / permission / prohibition / entitlement
574. **Exceptions / defenses / safe harbors** – Carve-outs from the rule
585. **Procedure / decision-maker** – Deadlines, notice, standards
596. **Consequences** – Penalties, remedies, invalidity, loss of benefits
607. **Forum / enforcer** – Agency, court, private plaintiff
618. **Interaction rules** – Preemption/savings, severability, effective date, cross-references
62
63## Mandatory Constraints
64
65### Verbatim Discipline
66- Never invent statutory language
67- Mark all quotations explicitly with pinpoint cites
68- If text is missing, say so and proceed with what is provided
69
70### Cross-Reference Discipline
71- When statute defines a term used in operative provision, incorporate that definition
72- Flag external cross-references: "cross-reference not included in provided materials"
73
74### Separation of Layers
75- Keep "Quoted Text" separate from "Explanation/Translation"
76- Use block quotes or clear markers
77
78### No Premature Narrowing
79- Even in scenario mode, include MAPS structure map at major-division level
80
81## Selection Rules
82
83**Mode A (no scenario):** Major operative provisions = primary prohibitions/requirements/entitlements + enforcement/remedies + key definitions + preemption/savings/severability/venue
84
85**Mode B (with scenario):** Prioritize provisions governing scenario issues + conditioning definitions/enforcement/exceptions. Still include full structure map.
86
87## Length Control
88
89| Constraint | Structure Map | Rule-Modules | Definitions |
90|------------|---------------|--------------|-------------|
91| Short | Spine outline only | Most relevant only | Key scope terms only |
92| Standard | Major divisions complete | Core operative provisions | Terms affecting scope |
93| Long | Full detail | All operative provisions | Comprehensive index |
94
95## Uncertainty Handling
96
97- Insufficient facts → Label "Fact needed: [specific missing fact]"
98- Partial statute → Label "based on provided excerpt only"
99- Never fill in absent provisions
100
101## Exact Headings (for parsing)
102
103```
104Scenario Module
105 Scenario synopsis
106 Issues framed as statutory questions
107 Relevant excerpts (verbatim)
108 Application map (statute-to-facts)
109 Context map (where excerpts live)
110 Not used but structurally important
111
112MAPS
113 Citation and text status
114 Purpose
115 Structure map (entire Act)
116 Scope and coverage
117 Definitions and interpretive rules
118
119RULES
120 Rule-Module: [Provision cite]
121```
122
123## Boundaries
124
125- Briefs statutes and legislative Acts only
126- No policy commentary unless asked
127- No grading or pedagogy commentary
128- No generating new statutory text
129- No case citations unless explicitly requested; may note "interpretive pressure points" as ambiguity flags
gabrielmoreira