prospects\2026-08-03.md — mark SENT in the log after
2
📣 Approve & post today's content
draft in your Gmail · file: content-queue\2026-08-03.md
3
📌 GBP appeal pending (submitted 2026-08-02)
standing reminder — check it off in chief-of-staff-agent.md when done
4
📌 Gemini API key rotation
standing reminder — check it off in chief-of-staff-agent.md when done
Bottom line
$2,970
potential pipeline — 6 active prospects × $495 if each closes as a Quick Win (drafted 6 · sent 0 · follow-up 0)
0Sent, awaiting reply
1Posts produced
0Opt-outs
The team — 8 agents, draft-first, $0/mo
EmailON DUTY2h · 8–6
ContentFRESH7:01a
ProspectsFRESHwkdy 7:33a
HealthON DUTY6:37a
ChiefFRESHMon 8:37a
MarketFIRST RUN SOONWed 7:07a
NewsFIRST RUN SOONThu 8:19a
ManagerON DUTY7:01p
Manager proposals — approve via directives.md
Google-review responder agent — build the moment the GBP appeal is approved. Benefit: every review answered within a day, local SEO signal.
Invoice-chaser agent wired to the paypal-invoicer app — needs a design chat with Steve first. Benefit: unpaid invoices never slip.
Add `reply` + `ring` columns to contacted-log.csv and score sourcing channels by reply rate instead of rubric points. Benefit: the prospect agent is at 94% on its own rubric and has zero outcome data — it is currently optimizing against its own judgment, not against what earns replies.
Recent manager changes
2026-08-03 — dashboard: added News chip + pending-newsletter action; weekly agents (chief/market/news) now use a 7-day freshness window instead of 3, which was flagging them stale by design mid-week. Team count now derived, not hardcoded. (by Claude, with Steve)
2026-08-03 (evening run) — prospect-agent.md, LINK RULE: added LINK CHECK — re-read every draft before saving and confirm no `tech-d-enterprises.com`/`www.` URL survives. Why: all three run-2 drafts (Lotus, Vantage Point, Rhode River) link to `https://www.tech-d-enterprises.com/appointments/`, violating the brain's own LINK RULE. Existing drafts NOT edited — they are Steve's to send; he must fix the link by hand or have the agent regenerate them. (manager, autonomous tweak 2/2)
2026-08-03 (evening run) — site-health-agent.md, Reporting: agent now writes a one-line heartbeat to `health\YYYY-MM-DD.md` on EVERY run, pass or fail (folder created). Why: the Monday brief could not distinguish "site healthy" from "agent never ran" — silence is most expensive on the one agent guarding the booking and contact pages. Loud-only-on-failure behavior unchanged. (manager, autonomous tweak 1/2)
2026-08-03 (evening run) — dashboard/build-dashboard.js: added a Refresh button + live "data as of … / Xm ago" age counter to the header. Clicking it reloads with a `?t=<timestamp>` cache-buster so Cloudflare can't serve back the build you're already looking at (verified: the live page was serving a stale cached copy before this). Baked into the generator, so it survives every rebuild. (by Steve's request, not an autonomous tweak)
rebuild: node build-dashboard.js · task the team: directives.md · retrain an agent: edit its brain .md