diff --git a/docs/src/content/docs/blog/2026-08-19-agent-of-the-day.md b/docs/src/content/docs/blog/2026-08-19-agent-of-the-day.md
new file mode 100644
index 00000000000..4e67a4107ca
--- /dev/null
+++ b/docs/src/content/docs/blog/2026-08-19-agent-of-the-day.md
@@ -0,0 +1,36 @@
+---
+title: "Agent of the Day – August 19, 2026"
+description: "Meet the Daily Community Attribution Updater, the workflow keeping gh-aw's README and wiki honest about who actually built the project."
+authors:
+  - copilot
+date: 2026-08-19
+metadata:
+  seoDescription: "The Daily Community Attribution Updater tracks 300+ real contributors to gh-aw with a five-tier attribution strategy — no guesswork."
+  linkedPostText: "The agent that gives credit where it's due, every single day"
+---
+
+## Agent of the Day – August 19, 2026: The Ledger Keeper
+
+Open source projects live and die by whether contributors feel seen. It's easy to merge a PR and move on; it's much harder to keep an accurate, living record of *everyone* who helped — especially when "helping" doesn't always mean a merged pull request. Sometimes it's an issue reporter whose bug got fixed by someone else entirely. Sometimes it's a discussion that quietly shaped a feature. Today's spotlight exists to make sure none of that gets lost.
+
+## Agent of the Day: The Ledger Keeper
+
+We're calling this workflow's persona **The Ledger Keeper** — an apt name for the **Daily Community Attribution Updater**, which runs once a day against `gh-aw` with one job: maintain a live, accurate community contributions section in the project's `README.md`, plus an all-time **Community Contributors** wiki page, by working through every community-labeled issue using a five-tier attribution strategy.
+
+That strategy is deliberately conservative, and it's worth spelling out because it's the whole reason the results are trustworthy:
+
+1. **Tier 0 (Direct):** Issues closed as `COMPLETED` by the reporting author — the strongest possible signal that a community member's report led to a real fix.
+2. **Tier 1 (GitHub Native):** Issues closed automatically via GitHub's built-in "Closes #N" linking in a merged PR.
+3. **Tier 2 (Keywords):** Standard closing keywords found in PR bodies that GitHub didn't auto-link.
+4. **Tier 3 (Cross-reference):** Follow-up or split issues resolved indirectly, found via targeted lookups.
+5. **Tier 4 (Candidates):** Anything closed during the review period that doesn't cleanly fit the first four tiers gets **flagged for a human maintainer** instead of being silently attributed or silently dropped.
+
+That last tier is the tell that this isn't a rubber-stamp bot. In [today's run](https://github.com/github/gh-aw/actions/runs/32092724656), the Ledger Keeper processed the full contributor set — now standing at **301 total community contributors** and **1,003 resolved issues** — and still found two edge cases it wasn't confident enough to attribute automatically: [#47156](https://github.com/github/gh-aw/issues/47156) and [#41994](https://github.com/github/gh-aw/issues/41994), both closed as `NOT_PLANNED` rather than merged fixes. Rather than guess, it surfaced them for a maintainer to make the final call.
+
+The same run added four brand-new names to the contributor rolls — Dongbumlee, kubaflo, Calidus, DeagleGross, and Etienne-M among the latest additions — updated `README.md` with the refreshed counts and links, refreshed the Community Contributors wiki page with a compact top-10 view, and opened its changes as a pull request (`community-attribution-2026-08-19`) for review. Across its last three tracked runs, it completed with **zero errors**, moved from a fast 1.5-minute no-op check to full 13-minute update passes when new activity appeared, and consistently classified as either `baseline` or `normal` — no `risky` or failed runs in the window.
+
+What makes this workflow worth highlighting isn't flashy output — it's the discipline. A five-tier waterfall that only claims what it can prove, a standing habit of flagging ambiguity instead of hiding it, and a running total that's grown past 300 real people whose names now live permanently in the project's own history. For a project built largely *by* its community, having an agent whose entire purpose is making sure that community gets named correctly is exactly the kind of quiet, unglamorous work that deserves the spotlight.
+
+---
+
+Curious how a workflow like this is built? Browse the [gh-aw repository](https://github.com/github/gh-aw) to see the Daily Community Attribution Updater and the rest of the agentic workflows running there every day.