Decision

Deploy the Hermes-rebuilt Casper comment system immediately. Test with Ben first, then transition all clients to Blake starting Monday. Build per-client agent instances to fix memory and voice-consistency issues. Set up an internal-only Notion board for in-progress content.

Context

The original Casper multi-agent system hit $350 in a single day and was shelved, reverting to Casper plus Eddie only. Hermes ran a full QA sweep and rebuilt from scratch using the OpenClaw scaffolding. Comments now run on Fable for voice fidelity at an estimated cost under $100/client/month even at 100 comments/week. Blake flagged four foundational quality problems: rule forgetting, single shared channel confusion, thread noise, and lack of format variety.

Options Considered

  • Continue with Casper plus Eddie only (status quo): Low cost but low quality; does not solve Blake’s complaints.
  • Hermes rebuild on Fable: Better voice fidelity, lower cost than original architecture, addresses core quality issues.

Consequences

  • Hermes comment rebuild ships today (July 30); Ben is the first test client.
  • Client transition to Blake begins Monday August 3.
  • Per-client agent instances to be built and tested next.
  • Internal-only Notion board to be created; clients no longer see raw drafts.
  • Roadmap of five advanced automations queued for subsequent sprints.
  • Ryna compiling 500-1,000 LinkedIn creator URLs for viral format library scrape.

Source

Casper Product Direction Sync