Components Legal
regulatory-update
Progression Ledger Structure
Change log against a baseline — numbered list of statutes/cases/rules with citation, summary, and effective date.
Variant
Use when a quarter's regulatory motion needs a single-slide digest. Each row carries the change name, the citation (inline code), the summary, and the effective-date marker (inline code).
When to use
- Period-bounded digest. When a quarter or half of regulatory motion needs to land as a single scannable ledger. The audience sees what moved, when it took effect, and where to read it — without flipping through a multi-page memo.
- Citation is the proof. Each row anchors on its inline-code citation chip. Without the citation the row reads as opinion; with it, the row earns its place in a compliance brief.
- Effective-date pill closes the row. The trailing
Effective Mon YYYYchip tells the audience whether the change is live, imminent, or final. The pill is the row's call-to-action signal.
When not to use
- Single rule's lineage. If the slide walks one rule from statute through case, use
authority-chain. regulatory-update is a period digest. - Past six rows. More than six items compresses the row gap and the citation chips run out of room. Split by jurisdiction.
- Missing summary or citation. Each row needs all three sub-items — citation, summary, effective date. Otherwise the row reads as rumour.
Slots
| Slot | Selector | Required | Description |
|---|---|---|---|
heading | h2 | yes | Slide heading framing the period or theme of the changes. |
scope | p:first-of-type > code | no | Optional inline-code scope label (e.g. 'Federal · State · International'). |
items | ol > li | yes | Ordered list of changes. Each item leads with a plain text name; nested ul carries citation (code), summary, and effective date (code). |
Anatomy
┌─────────────────────────────────────────┐
│ header │
│ Regulatory update heading. │
│ │
│ 01 Name §cite gloss [eff] │
│ 02 Name §cite gloss [eff] │
│ 03 Name §cite gloss [eff] │
│ │
│ footer 1/19 │
└─────────────────────────────────────────┘Variants
timeline — Timeline — chronological spine instead of ranked ledger
Renders the rows as a chronological spine — effective-date chips align on the right and the chrome reads as a calendar rather than a ranking. Use when chronology is the read, not weight.
<!-- _class: regulatory-update timeline -->
## Privacy and AI motion — Q1 2026 by effective date.
`Federal · State · International`
1. EU AI Act
- `Title III`
- Conformity-assessment pre-market obligation took effect.
- `Effective Feb 2026`
2. Colorado AI Act
- `SB 24-205`
- Developer and deployer duties for consequential-decision systems.
- `Effective Feb 2026`
3. FTC v. Avast
- `§5 unfairness`
- $16.5M consent order; clarifies the deception standard for privacy branding.
- `Final Mar 2026`
4. Texas DPSA
- `§541.151`
- DSAR opt-out portal mandatory; small-business safe-harbor narrowed.
- `Effective Mar 2026` priority — Priority — ranked by exposure rather than chronology
Stamps a priority rail on the left of each row and ranks by exposure rather than effective date. Use for board updates where the audience needs 'what to do' before 'when it landed'.
<!-- _class: regulatory-update priority -->
## Q1 motion ranked by exposure.
`Top three · by ARR at risk`
1. EU AI Act
- `Title III`
- High-risk system inventory due before April.
- `Effective Feb 2026`
2. Colorado AI Act
- `SB 24-205`
- Deployer disclosures required; copy in flight.
- `Effective Feb 2026`
3. Texas DPSA
- `§541.151`
- DSAR opt-out portal mandatory.
- `Effective Mar 2026` cards — Cards — one panel per item
Breaks the running list into discrete cards, one per development. Use when each item is independent and the audience may photograph a single card.
<!-- _class: regulatory-update cards -->
## Privacy and AI motion — Q1 2026.
`Federal · State · International`
1. EU AI Act
- `Title III`
- Conformity-assessment pre-market obligation took effect.
- `Effective Feb 2026`
2. Colorado AI Act
- `SB 24-205`
- Developer and deployer duties for consequential-decision systems.
- `Effective Feb 2026`
3. FTC v. Avast
- `§5 unfairness`
- $16.5M consent order; clarifies the deception standard for privacy branding.
- `Final Mar 2026`
4. Texas DPSA
- `§541.151`
- DSAR opt-out portal mandatory; small-business safe-harbor narrowed.
- `Effective Mar 2026` diff-bands — Diff-bands — grouped by change kind
Groups items under colour-coded h3 bands by the kind of change — Added, Amended, Repealed, Enforced. Use when the type of action matters as much as the instrument.
<!-- _class: regulatory-update diff-bands -->
## What changed this quarter, by kind.
### Added
1. Colorado AI Act
- `SB 24-205`
- New developer and deployer duties for consequential-decision systems.
### Amended
2. CCPA regulations
- `§7027`
- Opt-out preference signal handling clarified and tightened.
### Repealed
3. Small-business carve-out
- `§541.107`
- The blanket exemption was narrowed and partially repealed.
### Enforced
4. FTC v. Avast
- `§5 unfairness`
- $16.5M consent order finalised against deceptive privacy branding.