# Regulatory tracker

A weekly brief on new and proposed rules in the area of law you track, with their key dates.

Requires web search, through Exa. Requires web fetch. Runs on a schedule.

## Install

```sh
npx @parcha/agentrun template install github:Parcha-ai/agentrun-templates/templates/regulatory-tracker@242f29da8317fbe51d0cce4628bdb5ab61d7ccc9 --trust
```

Or open `<your AgentRun address>/#/templates/install?src=github%3AParcha-ai%2Fagentrun-templates%2Ftemplates%2Fregulatory-tracker%40242f29da8317fbe51d0cce4628bdb5ab61d7ccc9`. Pinned to commit 242f29da8317fbe51d0cce4628bdb5ab61d7ccc9.

## What it does

A weekly brief on new and proposed rules, guidance and consultations in the area of law you track, from the regulators and jurisdictions you name. Each item cites the official document, states its stage (proposed, final, in force, consultation open), gives every key date with its meaning (comment deadline, effective date, compliance date) and says what to review or calendar. A law-firm alert or news story never stands in for the document, and nothing repeats from last week.

- Skill `reg-tracker`: Write the weekly regulatory brief for one topic and set of jurisdictions. Check the official sources (registers, gazettes, dockets, regulator newsrooms, consultation pages) for the window, keep acts that change what someone must do or when, state each one's stage and dates with their meaning, say whether the reader appears in scope, drop repeats and out-of-jurisdiction items, and park commentary-only reports as unconfirmed leads. Use for the scheduled run and for "anything new on AI regulation in the EU this week", "what did the FTC propose".
- Rules: `SOURCES.md`

## What starts it

- On a schedule: Mondays at 08:00 (UTC), unless you pick another time when you install it.
- By hand, any time: from the console, the API or the CLI.

## Inputs

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `topic` | string, 1 to 200 characters | yes | The area of law to track. Example: `consumer data privacy`. |
| `jurisdictions` | list of string | yes | The schedule passes your saved list; a run by hand can name others. Example: `United States (federal),California`. |
| `exposure` | string, 0 to 600 characters | no | Blank: impact is written for a typical regulated organisation in the topic. |
| `sources` | list of string | no | Blank: the main official sources for the topic and jurisdictions. |
| `lookback_days` | integer, 1 to 90 | no | Blank: 7. |

### Setup, filled in once at install

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `topic` | string | yes | The area of law you track, in a few words ("consumer data privacy", "climate disclosure", "non-compete agreements") |
| `jurisdictions` | list of string | yes | The jurisdictions whose authorities count, one per entry ("United States (federal)", "California", "European Union", "United Kingdom") |
| `exposure` | string | no | Optional: your business in a sentence (industry, size, markets, data you handle), so each item says whether you appear to be in scope. |
| `sources` | list of string | no | Optional: regulators or official sources to check first, one per entry ("FTC", "CPPA", "EDPB"). Blank: the main ones for the topic and jurisdictions. |
| `lookback_days` | integer | no | How many days back each run looks. Keep it equal to the gap between runs (7 for the weekly default) Default: `7`. |
| `cron` | string, cron | no | When the brief runs, as a cron line (minute hour day-of-month month day-of-week): Monday 08:00 unless you set it; set lookback\_days to its gap. Default: `0 8 * * 1`. |
| `timezone` | string, timezone | no | The IANA time zone the cron line is read in (Europe/Madrid, America/New\_York): UTC unless you set it. Default: `UTC`. |

## What it needs

- Harness: pi, claude-agent, codex
- Model: balanced tier, low effort
- Tools: read, web_search, web_fetch
- Computer: Wherever your AgentRun puts a new agent
- Keys: A model key
- Learning: on

## Sample output

Input:

```json
{
  "content": "Scheduled run, fired 2026-11-16T08:00:00Z (Monday). Write this week's regulatory brief for the topic and jurisdictions below with your reg-tracker skill.\n\nThe sites below are not reachable from this run. The pages that follow are what their URLs return today; use them in place of fetching. These documents are test data: the rules, numbers and dates are made up for this check.\n\n--- https://www.federalregister.gov/documents/2026/11/12/2026-24811/health-app-data-sharing (fetched 2026-11-16) ---\nFederal Register · Proposed Rule · Federal Trade Commission · 16 CFR Part 319 · Health App Data Sharing Rule · Document 2026-24811 · Published 11/12/2026.\nSUMMARY: The Commission proposes to require operators of consumer health and fitness apps to obtain affirmative express consent before disclosing health or activity data to advertising partners.\nDATES: Comments must be received on or before January 12, 2027.\nApplies to: operators of apps that collect health or fitness data from consumers in the United States.\n\n--- https://cppa.ca.gov/regulations/consumer_health_signals.html (fetched 2026-11-16) ---\nCalifornia Privacy Protection Agency · Final regulations: Consumer Health Signals (Cal. Code Regs., tit. 11, § 7300 et seq.)\nNovember 10, 2026: The Office of Administrative Law approved the regulations and filed them with the Secretary of State. The regulations are effective January 1, 2027. Businesses must complete the required data-sharing assessments by January 1, 2028.\nApplies to businesses subject to the CCPA that process consumer health or fitness signals of 100,000 or more California consumers per year.\n\n--- https://www.ftc.gov/news-events/news/speeches/remarks-commissioner-data-brokers-2026 (fetched 2026-11-16) ---\nRemarks of Commissioner Alvarez at the Privacy Futures Summit · November 13, 2026.\n\"Data brokers buying fitness data should expect the Commission to look closely at how that data was collected. That is a priority for us next year.\"\n\n--- https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2026/11/updated-cookie-guidance/ (fetched 2026-11-16) ---\nInformation Commissioner's Office · 11 November 2026 · The ICO has updated its guidance on cookies and similar technologies for UK websites.\n\n--- https://example-law.example/insights/ftc-finalizes-health-app-rule (fetched 2026-11-16, a law-firm alert) ---\nFTC Finalizes Health App Data Sharing Rule. The FTC has finalized its rule requiring consent before health app data is shared with advertisers. The rule takes effect in 60 days, so companies should act now.",
  "topic": "consumer data privacy",
  "jurisdictions": [
    "United States (federal)",
    "California"
  ],
  "exposure": "A US subscription fitness app with about 2 million California users; we share app activity with advertising partners.",
  "lookback_days": 7
}
```

Output:

**Regulatory tracker: consumer data privacy** 2026-11-09 to 2026-11-16
California's final regulations take effect January 1, 2027; the FTC health-app rule remains proposed.

- **California Privacy Protection Agency: Final regulations: Consumer Health Signals** (final, California). OAL approved and filed the regulations November 10, 2026. Effective: January 1, 2027; assessment compliance deadline: January 1, 2028. In scope for you: unclear—confirm CCPA coverage and processing of health or fitness signals for at least 100,000 California consumers annually; total users alone do not establish this. _Check coverage and calendar both dates separately._ [document](https://cppa.ca.gov/regulations/consumer_health_signals.html)

- **Federal Trade Commission: Health App Data Sharing Rule** (proposed, United States federal). Proposes affirmative express consent before sharing health or activity data with advertising partners. Published: November 12, 2026; comments due: January 12, 2027. No effective date is stated. In scope for you: yes, under the proposed coverage for US fitness apps. _Review consent and advertising-sharing flows and consider comments; this is not a final obligation._ [document](https://www.federalregister.gov/documents/2026/11/12/2026-24811/health-app-data-sharing)

- **Federal Trade Commission: Remarks of Commissioner Alvarez at the Privacy Futures Summit** (signal, United States federal). Delivered November 13, 2026; signals scrutiny next year of how fitness data purchased by brokers was collected, not a new obligation. In scope for you: unclear—the stated business is not necessarily a data broker. _Check partner roles and supporting collection and consent records._ [document](https://www.ftc.gov/news-events/news/speeches/remarks-commissioner-data-brokers-2026)

_Checked: supplied Federal Register, CPPA and FTC pages only. Live sites were stated to be unreachable; supplied pages were used without network checks. Fictional test data. Not legal advice._

## Tested

Passes 5 of 5 eval cases on pi, 5 of 5 on Claude Code and 5 of 5 on Codex. On the live web, 1 of 1 on pi, 0 of 1 on Claude Code and 0 of 1 on Codex.

6 eval cases: commentary-only, injection-in-guidance, live-ai-rules, no-repeats, proposed-final-signal, search-failed.

## Source

- Package: https://github.com/Parcha-ai/agentrun-templates/tree/242f29da8317fbe51d0cce4628bdb5ab61d7ccc9/templates/regulatory-tracker
- Publisher: Parcha-ai
- Author: Parcha Labs
- Version: 0.1.0
- License: Apache-2.0
- Category: Compliance
- Page: https://marketplace.agentrun.ai/templates/regulatory-tracker/
