Memory.Wiki v8 Strategy and Vision

The collected documents outline Memory.Wiki's evolution toward becoming a cross-AI knowledge layer, positioning itself as the URL delivery system for AI context rather than another note-taking app. The v8 direction emphasizes sustainable craftsman SaaS growth while solving the core problem of users having to re-explain context across different AI tools.

Key claims

  • [EXTRACTED] Memory.Wiki is "the URL delivery layer for your AI knowledge" with three URL primitives: Documents (memory.wiki/<id>), Bundles (memory.wiki/b/<id>), and Hubs (memory.wiki/hub/<you>) [doc-1]
  • [EXTRACTED] The external thesis is "Stop re-explaining your context to every AI. Put your knowledge in one URL they can all read" [doc-2, doc-3]
  • [EXTRACTED] The founder goal is "지속 가능한 craftsman SaaS. 5년에 ARR $2-5M. NPS 70+. 1k-10k paid 사용자가 정말로 사랑하는 product" [doc-2]
  • [INFERRED] OpenAI/Anthropic cannot build a cross-AI memory layer because it would require feeding competitors, creating a structural wedge for Memory.Wiki [doc-1, doc-3]
  • [EXTRACTED] The strategic framework follows "CAPTURE → ORGANIZE → USE" with an indispensability loop, measured by Weekly Recapture Rate [doc-2]
  • [AMBIGUOUS] Embedded chat may not be essential for launch since it directly competes with ChatGPT/Claude, while the real strength is providing "perfect context URLs" [doc-3]
  • [EXTRACTED] Functional differentiation should focus on "AI-optimized context packaging" rather than raw document storage [doc-4]
  • [EXTRACTED] Intent-adaptive bundles could provide the same graph with different contexts (coding, fundraising, research) via URL parameters like memory.wiki/project-x?intent=coding [doc-4]

Cross-references

  • The "cross-AI" positioning appears in [doc-1] as a core primitive and in [doc-3] as a strategic wedge against big AI companies. Both emphasize this as Memory.Wiki's unique advantage.
  • Bundle functionality is described technically in [doc-1] as "curated groupings of docs" and strategically in [doc-3] as part of the launch magic moment where "AI가 bundle을 만든다."
  • The shift from feature complexity to focused simplicity appears in both [doc-2] (reducing from 8 features to 3) and [doc-3] (questioning even the embedded chat priority).

Open questions / gaps

  • How will the intent-adaptive bundles technically work beyond URL parameters?
  • What specific AI optimization techniques will differentiate Memory.Wiki from simple RAG wrappers?
  • How will temporal memory with graph edges (valid_from, valid_to, supersedes) be implemented?
  • What are the specific metrics and timeline for achieving the "Weekly Recapture Rate" goal?
  • How will the pricing model support the $2-5M ARR goal with 1k-10k users?

Provenance

  • [doc-1]: Comprehensive current state audit and homepage source defining Memory.Wiki's three URL primitives and capture surfaces
  • [doc-2]: Strategic v8 plan with founder goals, architectural framework, and success metrics
  • [doc-3]: Strategic analysis emphasizing cross-AI positioning strength and questioning embedded chat priority for launch
  • [doc-4]: Technical differentiation ideas focusing on AI-optimized context packaging and intent-adaptive bundles