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-2]
• [EXTRACTED] The external thesis is "Stop re-explaining your context to every AI. Put your knowledge in one URL they can all read" [doc-1]
• [EXTRACTED] The founder goal is "지속 가능한 craftsman SaaS. 5년에 ARR $2-5M. NPS 70+. 1k-10k paid 사용자가 정말로 사랑하는 product" [doc-1]
• [INFERRED] OpenAI/Anthropic cannot build a cross-AI memory layer because it would require feeding competitors, creating a structural wedge for Memory.Wiki [doc-6]
• [EXTRACTED] The strategic framework follows "CAPTURE → ORGANIZE → USE" with an indispensability loop, measured by Weekly Recapture Rate [doc-1]
• [EXTRACTED] The core product promise is "You author. AI uses. The wiki maintains itself" with automatic concept indexing, backlinks, and LLM maintenance [doc-4]
• [AMBIGUOUS] Current gap from mdfy to true memory.wiki is "링크 그래프, 의미 기반 검색, LLM 자가 정리" but timeline and implementation details vary across documents [doc-4]
• [EXTRACTED] Multiple distribution channels planned including MCP server, Chrome extension, Mac/iOS apps, VSCode extension for comprehensive capture [doc-5, doc-6]

Cross-references

• URL Architecture: Both doc-1 and doc-2 describe the three-tier URL system but doc-1 shows incomplete text while doc-2 provides full specification with markdown delivery via Accept: text/markdown.
• Cross-AI Positioning: Doc-4 emphasizes it's "not another notes app" while doc-6 positions it as "infrastructure category" rather than notes, memory, or agent memory store.
• Launch Strategy: Doc-5 details App Store submission process while doc-6 mentions "6월말 9-surface 동시 public 런치" suggesting coordinated multi-platform launch.

Open questions / gaps

• Specific implementation timeline for the missing pieces (graph links, semantic search, LLM auto-organization)
• Pricing strategy beyond the free tier mentioned in App Store listing
• Technical architecture for cross-AI compatibility and the promised "100% benchmark 검증"
• How the "indispensability metric" of reduced re-explanation will be measured across different AI platforms

Provenance

• [doc-1]: Strategic framework and URL architecture foundation for v8 direction
• [doc-2]: Launch checklist with current capabilities and capture surfaces
• [doc-3]: Referenced vision document (content appears cut off)
• [doc-4]: Detailed product specification defining core promises and differentiation
• [doc-5]: App Store submission guide showing distribution strategy
• [doc-6]: Founder pitch preparation positioning Memory.Wiki as infrastructure rather than notes app