| name | brief-a-regulation |
| description | Turn a new law, enforcement action, or piece of guidance into a structured briefing covering scope, obligations, penalties, dates, and practical implications, pitched at the intended audience. Use when something has been published and someone needs to understand what it means for them. |
Brief a Regulation
Turn a published instrument — a new law, an enforcement action, updated guidance — into a briefing
someone can act on. The work is scope and applicability, not summary.
1. Identify the instrument and the audience
Confirm exactly which instrument is in scope, in which jurisdiction, and at what stage: binding law
in force, adopted but not yet applicable, a proposal, or non-binding guidance. Those are different
things and readers act on them differently.
Establish who the briefing is for, because it changes the register more than the content:
- Expert: full legal detail, article-level references, assumes familiarity.
- Client-facing: plain language, actionable takeaways, technical terms defined.
- Board-level: one page, headline risk, financial exposure, no citations in the body.
2. Work from the instrument itself
Read the actual text, not commentary about it. Use commentary afterward to check your reading and to
find what practitioners think matters. Strawberry can work through official registers, regulator
sites, and subscriptions the user already has, and follow citations into the underlying provisions.
Keep confidential matter details out of search queries.
3. Cover what a reader needs to act
Depending on audience and instrument:
- what changed, with specific article or section references;
- who is affected, and the thresholds or exemptions that decide it;
- obligations, separated by the type of actor they fall on;
- enforcement and penalties;
- key dates — in force, applicable from, transition periods, deadlines;
- practical implications, and what is still pending or expected.
Distinguish binding obligation from guidance and from proposal throughout. Readers routinely act on
proposals as though they were law, and a briefing that blurs the two causes that.
4. Verify before returning it
Confirm every provision reference against the instrument itself. Article and section references are
structural and reliable; page references are not. Confirm dates against the official text rather
than reporting about it, and confirm the instrument has not been amended since the version you read.
Flag anything unverified rather than leaving it unmarked.
5. Deliver and continue
Lead with what the reader must do and by when. Keep the detail beneath it.
Use strawberry/legal/compare-across-jurisdictions when the same obligation needs comparing across
several regimes, and strawberry/legal/research-a-legal-question when the real need is an answer to
a question rather than a briefing on an instrument.
When the user tracks an area continuously, a Routine can watch agreed official sources and report
only material developments — new binding instruments, enforcement actions, imminent deadlines. Agree
the sources, what counts as material, the cadence, and the review point before setting one up.
