Result
self-reportedIn a 17-agent marketing practice, a publishing agent’s log said a whole week of posts had gone out, and none were live. Separately, one decision only the owner could make sat for six weeks with five runs blocked behind it. He added five simple checks so both get caught fast.
Aaron Douglas is a fractional marketing leader who runs his practice with about 17 AI agents. A duplicate-run guard trusted its own log, so it skipped a week of posts that never published. His rule now: check the output, not the log, because “an API 200 is a claim, not a fact.” His check layer is a run ledger, a daily watchdog, one agent whose only job is reporting, one writer per file and a decisions log with a “revisit if” tripwire.
Who did it
Try it now
- Have every scheduled run write one start line and exactly one end line to a shared ledger, even on days with nothing to do.
- Have a watchdog read the ledger daily, message you, and escalate any flag older than 7 days.
- For anything that publishes or sends, check the live result (the post on the page, the email in the sent folder), not the agent’s own log.
- Let only one agent edit a given file at a time.
- Keep a decisions log with a “revisit if” line, and make the call on any flag that keeps coming back.
You are my agent watchdog. Every morning, read [ledger file]. For each scheduled run from the last 24 hours: confirm there’s exactly one start and one end line. For every run that published or sent something, open the live result ([site / social profile / sent folder]) and confirm it’s really there. Don’t trust the run’s own log. Message me a short list: missing runs, runs with no end line, published items that aren’t live, and any flag that’s been open more than 7 days.
Make it run every week
A play works once. Turn it into a routine in three small steps:
- Run it once and check the result yourself.
- Give your AI a schedule. Tell it when to run this play (every week, or every month) and to message you with what it found before you act.
- Keep a log. One line per run: what was checked, anything flagged, what you did.
What to watch out for
Self-reported in his own article. It’s a lesson play: the money here is the week of posts you don’t lose. The checker can be wrong too, so decide in advance who checks it. Build it with Page: a status page your team can open to see what actually went live.
Did it work?
PageMotor keeps this site free.