Agent stack build plans · № 2 · Hermes community manager

What you get

One agent that answers in three places, keeps a file on every regular, and hands you a reward queue instead of a vibe.

The end state of this build is a single hermes gateway daemon logged into your Discord server, your Slack workspace, and your WhatsApp group. Same brain everywhere: it answers support questions with data it fetched itself, appends what it learned about each member to a notes file, and every Friday proposes — never dispenses — the week’s rewards. Below is the community pulse it DMs you each morning, mocked up as a dashboard so you can see the whole loop at once.

community pulsetue 21 jul · 07:30 · cron: daily-pulse

discord · #help

@petra — “v2 migration breaks my webhooks?” unanswered 9h

@sam_k — install fails on Termux answered, cited v0.19.0 notes

slack · #partners

Dana L — asked for the API deprecation date answered from changelog skill

thread on rate limits went 14 replies — summary filed

whatsapp · core group

Ravi — shipped the docs PR he promised noted

quiet otherwise — 6 messages

member notes updated overnight — community-notes skill

petra.md3rd webhook question this month; runs self-hosted; patient but blocked

sam_k.md2nd helpful answer to others this week; Termux edge cases

ravi.mddocs PR merged; asked about a maintainer role in June

pending rewards — needs your approval

@sam_k5 answered threads this week → Discord role: Helper (discord_admin)

Ravidocs PR merged → shoutout in #announcements + WhatsApp group

memory: MEMORY.md 1,840/2,200 chars · 3 member files touched · next pulse 07:30

Static mock, real seams: every label maps to a mechanism this plan sets up — the pulse is a cron job, the notes are a skill the agent wrote for itself, the reward buttons are your approval step. The buttons here just toggle; the real ones are you replying “approve” in a DM.

A day in the life

07:30 — the daily-pulse cron job runs: Hermes searches its own past sessions (session_search, SQLite full-text — every conversation it has is queryable) and DMs you the pulse above.
10:12, Slack — a partner asks when the v1 API dies. The agent runs the changelog skill it wrote for itself (a scripts/ fetch against your repo’s releases), answers with the actual version and date, and appends a line to dana-l.md.
15:40, Discord — petra’s webhook question again. The notes file says it’s her third; the agent answers and flags the docs gap to you, because three identical questions is a docs bug.
Friday 17:00 — the weekly-shoutouts cron proposes at most three rewards with receipts. You reply “approve”; the agent assigns the Discord role via the discord_admin toolset and posts the shoutout. No approval, no action.

What it deliberately doesn’t do

No auto-moderation. It never deletes, mutes, or bans. Rewards are additive and human-approved; punishment stays human, full stop.
No per-member memory magic. Hermes’s built-in memory is two small markdown files about you and your setup — not a dossier per member. The member files above exist because this plan has the agent build and maintain a notes skill. Architecture shows the seam honestly.
No engagement theatre. It doesn’t post “great question!” filler or streak-count anyone. The pulse surfaces unanswered threads and quiet contributors; what to do about them is your job.