Skip to content

Case-Study Writeups Brief

Status: Active commitment (formerly proposed as ADR-069) Date: 2026-05-23 Owner: CoachJ (writeup), Claude / Hermes (with-vs-without runs)

What it is

A case-study writeup is a published artifact that takes a real Hermes interaction with a Sync-augmented agent and contrasts it against the same agent without Sync. Same person, same question, same conversation context — one with the Sync profile loaded, one without. The delta in recommendation, framing, and grounding is the artifact.

First subject: Ryan Sarver. Named on 2026-05-08 as the canonical first writeup.

Why it's the most-discussed-never-shipped marketing artifact

Three reasons it matters:

  1. Eval harness produces quantitative signal but lacks qualitative legibility. "Condition C produces 73% more aligned recommendations than Condition A" is real but not legible to a prospect. A side-by-side case study makes the same signal visible at a glance.

  2. Market positioning depends on concrete demonstration. Every personal-AI competitor (Lindy, Manus, Granola, custom GPTs) shows feature demos. None can show "agent that knows you specifically." That's the thesis Sync uniquely substantiates — and demonstrating it requires showing the with-Sync vs. without-Sync delta on a real person, not in synthetic examples.

  3. Case studies compound. One case study is a demo. Five case studies across different domains (governance, hiring, financial trade-offs, interpersonal conflict) becomes a pattern prospects can map themselves onto.

Why it hasn't shipped before: every prior attempt got displaced by feature work. The blocker has been the per-case-study time investment (4-6 hours setup + execution + writeup + publication), not capability.

Format

Each case study follows the same structure:

  1. Subject and context (1-2 paragraphs)
  2. Who the subject is (role, relevant background)
  3. The specific decision-style question being explored

  4. Why this question is a genuine trade-off (no objectively correct answer)

  5. The setup (1 paragraph)

  6. Same agent (Claude / Hermes)
  7. Same conversation context (any prior turns)

  8. Two runs: with Sync profile loaded vs. without

  9. The without-Sync response (verbatim, in a quote block)

  10. Full agent output

  11. No editing for length or clarity

  12. The with-Sync response (verbatim, in a quote block)

  13. Full agent output

  14. No editing for length or clarity

  15. The delta — what Sync changed (2-3 paragraphs)

  16. What specific signals the with-Sync response anchored to
  17. What the without-Sync response defaulted to
  18. Why the with-Sync version is more useful for this person specifically — not a generic "better answer"

  19. Honest assessment: where the without-Sync version was still defensible

  20. What this generalizes to (1 paragraph)

  21. The pattern this case study demonstrates
  22. When you'd expect to see similar behavior in your own use

Cadence and triggers

Trigger-driven, not calendar-driven. Each significant Hermes integration milestone is a candidate for a case study. Milestones include:

  • A new MCP tool surface that opens a new question class
  • A profile signal becoming visible to users for the first time (ADR-065 territory)
  • An ADR shipping that changes how the agent represents the user

Target cadence: one per month is ambitious. One per quarter is sustainable. Pick deliberately — overcommitting and missing is worse than committing and consistently hitting.

Distribution

External surfaces (in priority order): 1. Beacon blog / Pulse marketing site — canonical home 2. Twitter/X thread — primary distribution channel 3. LinkedIn — secondary, for B2B reach 4. Anthropic Showcase / Cookbook submissions when format aligns

Internal surfaces: - Each case study doubles as a qualitative data point in the evaluation pipeline alongside the quantitative eval harness - Sales conversations get to point at "this is what we mean by personalized agent"

Adjacent ideas (parked, ship case studies first)

  • Daily Hermes-driven sync routine ("the daily drop") — audit item 46. Adjacent marketing surface. Ship case studies first; the daily-drop can build on whatever distribution channel case studies establish.
  • Per-team demo/training arc — audit item 44. Team-level case study format. Same principle: wait until single-user case studies are proven.

First case study scoping

Before the first writeup ships, three things need to be true:

  1. A real Sarver question with a non-obvious answer is identified
  2. Both runs (with-Sync and without-Sync) are completed and outputs preserved verbatim
  3. A 4-6 hour writing slot is blocked

If any of those slips, document why and move the slot rather than abandoning the artifact.

Why this was originally proposed as an ADR

ADR-069 was the original home for this commitment, but ADRs are for technical/architectural decisions (dependencies, patterns, API design, deferred features). A content/marketing strategy commitment is a different category of work. Superseded by this brief on 2026-05-23.