🔧 Reference

Hermes — Social Command Center

1 source Updated Sun Apr 19 2026 19:00:00 GMT-0500 (Central Daylight Time) Internal
toolhermesreferencetool-inventory

Summary

Hermes — Social Command Center — regenerated from canonical/guides/tools/hermes.md. Do not hand-edit this page — update the canonical file and re-project. Status: wip. Primary domain: hermes.stoicagent.com. Pipeline role: organic distribution + paid amplification — downstream of Spark + Lyra.

Content

Purpose

Agent-facing social distribution. Receives Spark output (with Lyra short link baked in) and distributes to per-agent Facebook/Instagram pages with personalized captions. Infographic builder included. Organic-first — paid boost via Facebook MCP Ads is the next layer (planned).

Current state

  • Status: Organic flow complete and live. Paid-ads layer (Wings) shipped through Phase 3 on 2026-04-20.
  • Replaces: Sked Social (~$50/month) for organic; absorbs the paid-amplification layer too (eliminates need for manual Meta Ads Manager work on listing posts)
  • Biggest organic gap: 5 agents (Andrew Meirink, Chad Wilkins, Colin Welsh, Jayden Renner, Joey Purdy) have invites pending in Meta Business Suite — Fred opted to leave them behind rather than chase
  • Pipeline position: Receives Spark output → distributes organically → auto-attaches paid boost (2.5h delay) → reports via ads-status

Wings (paid ads) — active build

  • Resume handoff: working/chats/2026-04-20-hermes-wings-phases-1-2-3.md
  • Approved plan: ~/.claude/plans/plan-mode-architecture-question-serene-patterson.md
  • Phases shipped: 1 (standalone boost mode), 2 (Claude-suggested strategy + historical seeding + safety hardening), 3 (Listing Promo auto-attach + policy rejection surfacing + webhook stub)
  • Phase 4 queued: bulk boost from queue view, "boost like last time" copy, conditional creative refresh (~6h)
  • Phase 5 queued: seller reporting PDF (Beacon-embeddable marketing receipts, ~8-10h)
  • Central ad account: act_1532163463522661 (ARTEMIS / MVP Data). Per-agent override via adAccountId field on agent records (null = central). Curtis and Darin have their own accessible accounts ready to assign.
  • Safety caps: $100/day, $1000/campaign, $3000/month — server-enforced

Where it lives

  • Code: Tools/Hermes/
  • Deployed: hermes.stoicagent.com (Netlify: artemis-social-poster.netlify.app)
  • Brand & voice: pulls from Write Like Fred v4 for caption style

Integrations

  • Spark — receives newly built showcase pages
  • Lyra — uses Lyra short URLs in every distribution
  • Meta Business Suite — per-agent Facebook/Instagram page access
  • Cloudinary — cloud dbxz8xmbr, preset artemis_social (unsigned) for media upload
  • Write Like Fred — caption generation applies voice rules
  • Future: Facebook MCP Ads (paid layer, next in queue)

Related

  • Inventory row: canonical/business-state/tool-stack-inventory.md → "Hermes"
  • Brand voice: canonical/brand/write-like-fred-v4.md
  • Cloudinary: settings in deploy env + parent CLAUDE.md

Typical development touchpoints

  • Per-agent caption personalization (variables: agent name, phone, photo, voice tone)
  • Meta API authentication per agent page
  • Infographic templating
  • Content queue + scheduling
  • Failure handling (agent disconnected, rate limit, media upload fail)

Active WIP location

working/drafts/tools/hermes/ (create as needed — this is the tool most likely to need an active WIP folder given its build stage)

Open questions / gaps

  • Agent onboarding completion rate — which agents have NOT accepted Meta Business Suite invites?
  • Infographic builder completeness — which templates are production-ready?
  • Content approval flow — does Fred approve per-post, per-agent, or auto-publish?
  • Failure alerting — if a post fails, where does the notification go?