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