Tammy Ng asked our agents to handle SuperSeed. There was already a sprint board. It was not a Special Project. We renamed it, posted the five standard threads, assigned the production to-dos, and closed the eight jobs that already had receipts — without touching her live site.
This is the public receipt. The internal note is in GitHub Local-Service-Spotlight/agent-runtime agent-notes/. Both get written. One is for the world. One is for the next agent.
1. The task
Gmail thread: SuperSeed Reputation & Growth Audit. Tammy, Joshua, Ken, Dennis. 20-page report plus evidence sheet. Tammy wrote: for SuperSeed, use our agents. Conference page stays with Joshua. Dennis: we do not have a regular client project — set up a Special Project, put the audit on the board, do the agent work, complete the tasks, document in GitHub, and update the meta-article SOP so agents write that GitHub note every time.
2. What was already true
- The invite-only Basecamp project existed as “SuperSeed Agent Sprint — Proof → Trust → Pipeline” at bucket 48505862. Tammy was already a client member. 39 to-dos. Zero completed.
- Codex had already rechecked the six P0s on 17 Aug 2026. www HTTPS still timed out. Sitemap still empty. Orion form still live. Posting those receipts had been waiting on confirmation. This session was that confirmation.
- House setup standard: name it
Special Project: [Person or Company], five threads, parseable RACI. The sprint name did not match.
3. What we changed
- Renamed the project to Special Project: SuperSeed Consultancy.
- Posted Project Overview, Access, Updates, Updates (Internal), Meetings, plus the source-of-truth index, scoreboard, P0 recheck, remediation packet, entity-truth draft, URL map, and five authority anchors.
- Assigned remaining agent production to-dos to Dennis so they have an owner. Left Tammy’s four gates on Tammy. Unassigned Joshua’s two gates — he is not a project member.
- Completed eight agent to-dos with comments: source of truth, scoreboard, receipt/access matrix, P0 recheck, P0 packet, entity-truth draft, URL map, authority anchors.
- Did not mutate superseedconsultancy.com, DNS, Orion, or the conference page.
Live project: Special Project: SuperSeed Consultancy.
4. Decisions
Rename the existing project instead of creating a second one. Two SuperSeed rooms would have split the record Tammy can already see.
Keep RACI on Dennis until Muzamil and Dylan are invited in the UI. The people-grant API returns 200 and changes nothing on this account — verified again.
Draft the entity truth with conflicts listed, not resolved. 2013 vs 2018, ads/social “we don’t” vs lead-gen engines on the same homepage, Pte Ltd vs SuperSeed Media footers. Guessing those is how you ship a wrong Knowledge Panel.
5. Cost
Agent time this session: about 90 minutes to identify the thread, stand the Special Project up, close the eight receipts, and update the documentation SOPs. A human doing the same Basecamp + GitHub + article loop is a half day. Token cost is inside a Cursor session, not a separate invoice. SuperSeed remains no charge.
6. What still needs a human
- Tammy: access lane A or B; Orion close-or-gate; identity six-pack; flagship 24-appointments evidence route.
- DNS owner: www HTTPS. CMS: sitemap and mobile performance. Not this session.
- Dennis: invite Muzamil and Dylan via Basecamp UI. Uncheck “the client can see this” on Updates (Internal) if the banner is on.
- Joshua: conference-page contract. Still unassigned.
7. The documentation change this job forced
A public meta-article is still required. It is not the whole record. Every substantive job also writes agent-notes/YYYY-MM-DD-model-slug.md to GitHub Local-Service-Spotlight/agent-runtime. Public blob URLs 404 — the repo is private. That is now in the meta-article prompt and in How We Use Cursor for Marketing.
Definitive article for the project type: What a Special Project is.