What your editorial team would write — if they had three hours every Monday

The SF Rules Committee meets every Monday at 10am. The agenda lands Sunday; the supplementary packet runs two hundred pages. By Tuesday noon, three other outlets have already published on it. Yours hasn’t.

This closes that gap.

What it does

Watches the Rules Committee page all weekend and through Monday morning. The moment a packet, supplemental, or caption drops, it’s read.
Writes a listicle by early Monday afternoon — nine items, one pull-quote each, in the cadence your team has already picked. (Drop in two or three of your existing posts and it learns your house voice.)
Flags every line item over $5M. Flags anything touching audit, overspending, budget, or charter. Team adds its own keywords.
Every claim cites back to the page of the PDF — with a clipped screenshot of the passage ready to drop into a post.
Lands in your editor’s inbox by 3pm Monday, pre-reviewed.

The reveal

2pm, committee wraps. 3pm, your editor opens an email with a draft listicle, nine pull-quotes, and nine agenda screenshots. Edit, publish by 6. No one on your side opened a PDF.

What it doesn’t do

No opinions. No speculation. No “what this means for San Francisco.” It writes what happened with citations; your writers bring the argument.

Configuration

Committee pages: starts with the Rules Committee. Add Budget & Finance, the Board of Supervisors, or any sf.gov/department-* page.
Voice model: drop in 2-3 of your existing posts; briefs match their cadence.
Alert keywords: defaults to audit, overspending, budget, charter, and any dollar line item over $5M. Team adds or removes.
Delivery: who gets Monday’s listicle, and by when.

Triggers