README: continuity-layer positioning, hero anti-drift block, FAQ

[gregherbe76]

Pre-launch README reframe based on user / Lovable feedback.

Changes

Positioning — replaces "memory protocol for vibe coding agents" with the clearer category claim:

A continuity layer for AI-built projects. Persistent memory for Claude Code, Cursor, Lovable, Replit Agent — across sessions, across agents, across months.

The word "continuity" is less saturated than "memory" (MCP memory, LangChain memory, agent memory, RAG memory) and creates a sharper category.

Business pain line added under the tagline:

Without continuity, the human becomes the project's memory system. vibe-memory takes that load off.

Names the actual cost (the human acting as the project's cache / diff engine / architectural reminder) that today's "AI memory" projects describe only abstractly.

Hero anti-drift block moved above the fold. The "stop the agent before it contradicts a past decision" moment is the protocol's most concrete value. Code-fenced block placeholder for now; replace with a GIF/video at launch.

FAQ section added (before License), answering the questions the launch will get:

• Why not an MCP memory server? — MCP = retrieval, vibe-memory = continuity. Complementary, not competitors. Avoids becoming "anti-MCP".
• Why not just a CLAUDE.md / .cursorrules? — Those store rules; vibe-memory stores events.
• Is this just ADRs? — vibe-memory is ADRs operationalized for AI — machine-readable, written by the agent during the session, re-read by the agent at every future session.
• Will the agent actually follow the protocol?
• How does it scale?
• What about token cost?

Why a separate PR

PR #1 was merged and tagged v0.3.0. This README reframe is purely positioning / launch-prep material — no code, no protocol change. Merging here lets you decide between:

• Land it on main as a doc-only patch (no tag bump needed)
• Roll it into a v0.3.1 with whatever else accumulates pre-launch

No new protocol section, no new file, no behavior change. Just framing.

---

Generated by Claude Code

[github-actions]

🧠 vibe-memory changes in this PR

1 new decision(s):

• convention [positioning] — README reframed around 'continuity layer for AI-built projects'; added business-pain line, hero anti-drift block, and FAQ (MCP=retrieval vs vibe-memory=continuity, CLAUDE.md=rules vs memory/=events, ADR comparison)
  • why: prepare repo for v0.3.0 launch: replace abstract 'persistent memory' positioning with concrete 'continuity' framing and the anti-drift moment as the hero
  • by: claude-code

Posted by the vibe-memory PR-comment workflow. Edit decisions/drift entries before merging if needed.