Workflow

My agent watches city hall so I don't have to

My watchers cover a Florida city's public record: council and planning board agendas twice a day, county court dockets for a set of tracked lawsuits, federal co

by Thomas GaumeUpdated 13 Oct 2026Useful · 0

Share this workflow Post to X Post to Threads

Say this to Muse

I want you to run a stack of standing watchers over public records for me. Each watcher checks one source on its own schedule, remembers everything it has already seen, and stays silent until something actually changes. When something changes, I get one full report. Never two.

INPUTS: the sources to watch (a meeting agenda portal, a court docket search, a permit database, property sale records) [INPUT]; what counts as newsworthy in each source [INPUT]; how often each source gets checked [INPUT]; where the watchers keep their state files [INPUT].

1. State is a file, not a memory. Each watcher keeps a state file listing everything it has already seen: document IDs, case numbers, permit numbers, dates. Every run compares the live source against that file. If it isn't in the file, it's new. If it is, it doesn't exist.
2. Silence is the default. A run that finds nothing new writes a one-line status to its log ("checked, nothing new") and sends me nothing. That log line matters: it's how I

Copy it into Muse and run it.

The result

My watchers cover a Florida city's public record: council and planning board agendas twice a day, county court dockets for a set of tracked lawsuits, federal court once a month with a hard cap on paid database searches, building permits and development applications nightly, land sales weekly, and water district permits weekly. Most runs find nothing and say nothing, which is the point. When the city posts a surprise agenda addendum or a new lawsuit lands against it, I know within hours, with the document already archived, instead of finding out at the meeting.

What didn't work: an early watcher kept "succeeding" for days while the portal it checked had started blocking it, so it was reporting silence from behind a wall. Watchers now have to prove a real read each run, and blindness gets reported as a failure, not mistaken for a quiet day. The first versions also re-reported the same item every run until state files and the surface-once rule ended that. And one portal redesign broke a

Questions about this workflow

What does this workflow do?

My watchers cover a Florida city's public record: council and planning board agendas twice a day, county court dockets for a set of tracked lawsuits, federal co

What prompt does this workflow use?

I want you to run a stack of standing watchers over public records for me. Each watcher checks one source on its own schedule, remembers everything it has already seen, and stays silent until something actually changes. When something changes, I get one full report. Never two. INPUTS: the sources t...

How do I use this workflow?

Copy the prompt from this page into Muse and adjust the details to your situation. The result above is what the author got. Every workflow here is free to use; you just need access to Muse, and if you do not have an invite yet you can claim a community code on the homepage.

Report this workflow

Your turn

Be one of the first to post your Muse workflow here. Add your own and become the person people follow.

Publish a workflow More workflows

Discussion

No comments yet

Be the first to share how this worked for you.