--- title: "Memory.wiki Strategic Pivot and Product Evolution" url: https://memory.wiki/4N8X52tq updated: 2026-05-21T02:50:03.911Z hub: https://memory.wiki/hub/raymindai concept_count: 11 source: "auto-synthesis" --- # Memory.wiki Strategic Pivot and Product Evolution > The documents chronicle memory.wiki's strategic evolution from a basic markdown sharing tool to an AI-native knowledge graph platform, with multiple rounds of scope refinement to achieve a focused launch strategy. ## Key claims - [EXTRACTED] The core value proposition is "A memory.wiki URL is an API for any AI" - users can paste URLs into ChatGPT, Claude, Gemini, or Cursor [doc-1, doc-2] - [EXTRACTED] The project underwent a major rebranding from "mdfy.app" to "memory.wiki" between v6 and v7, with the domain secured and finalized [doc-1, doc-7] - [EXTRACTED] The system operates on a 3-tier architecture: "수집/소화/활용" (Capture/Digestion/Utilization) where users author content, AI organizes it into graphs, and any AI can consume it via URLs [doc-1, doc-3] - [EXTRACTED] The launch scope was dramatically reduced from "8개 → 3개" features (8 to 3 features) to make the 16-week deadline achievable [doc-7] - [INFERRED] The project positioning shifted from being another note-taking app to serving as "LLM 서비스의 기본 지원 메모리 레이어" (fundamental memory layer for LLM services), targeting the knowledge delivery problem rather than AI memory [doc-5, doc-8] - [AMBIGUOUS] The business model and pricing structure underwent multiple revisions, settling on a 3-tier approach (Free/Pro/Team), though specific pricing details remain undefined [doc-7] ## Cross-references - The "URL as API" concept appears consistently across all versions, remaining the core architectural principle despite other strategic pivots [doc-1, doc-2, doc-5] - The founder's motivation (doc-5) directly connects to the product specification's "delivery problem" framing, reinforcing the strategic thesis [doc-3, doc-5] - The scope reduction in v7-revised reflects lessons learned from the ambitious v7 plan, showing iterative refinement of the launch strategy [doc-1, doc-7] ## Open questions / gaps - Technical architecture details for how URLs actually function as APIs across different AI platforms - Specific pricing tiers and monetization mechanics for the Free/Pro/Team model - Implementation timeline for post-launch features like Bundle Spec RFC and public hub sharing - Competitive differentiation strategy against established players like Notion and emerging AI memory solutions ## Provenance - [doc-1]: Original v7 business plan establishing the core vision and 3-tier architecture - [doc-2]: Duplicate content reinforcing the central value proposition - [doc-3]: Product specification defining technical requirements and brand positioning - [doc-4]: Meta-commentary on the business plan evolution and architectural principles - [doc-5]: Founder's manifesto articulating the knowledge delivery problem and solution rationale - [doc-6]: Product specification synthesis focusing on the dual-door vision - [doc-7]: Revised v7 plan with dramatically reduced scope for achievable launch - [doc-8]: Simplified explanation of the core concept and competitive positioning --- ## Summary Memory.wiki is evolving from a markdown sharing tool into an AI-native knowledge graph platform where users can share content via URLs that function as APIs for any AI system (ChatGPT, Claude, Gemini, etc.), operating through a three-stage architecture of capture, digestion, and utilization. The project underwent a major scope reduction from 8 to 3 features to meet its 16-week launch deadline while maintaining its core positioning as a fundamental memory layer for LLM services. ## Themes - AI-native knowledge infrastructure - strategic scope reduction - URL as universal API - 3-tier architecture model - rebranding and repositioning ## Key takeaways - memory.wiki's core value proposition is that any memory.wiki URL functions as an API consumable by ChatGPT, Claude, Gemini, or Cursor. - The platform operates on a 3-tier architecture of Capture/Digestion/Utilization where users author content, AI organizes it into graphs, and any AI can consume it via URLs. - The project rebranded from mdfy.app to memory.wiki between v6 and v7 with domain finalized. - Launch scope was reduced from 8 features to 3 features to meet the 16-week deadline. - memory.wiki positions itself as a fundamental memory layer for LLM services addressing the knowledge delivery problem rather than AI memory. ## Insights - The project's core value proposition remained constant across multiple strategic pivots, suggesting the URL-as-API concept is the fundamental architectural anchor rather than a feature. - Scope reduction from 8 to 3 features was a deliberate trade-off to meet launch deadlines, indicating prioritization of market entry speed over feature completeness. - The positioning shifted from competing as a note-taking tool to serving as foundational memory infrastructure for LLM services, suggesting a recognition that the addressable market is defined by AI consumption patterns rather than user crea ## Open questions / gaps - How do URLs technically function as APIs across different AI platforms with varying API specifications and authentication requirements? - What are the specific pricing details and mechanics for the Free/Pro/Team tier model? - What is the post-launch roadmap for features like Bundle Spec RFC and public hub sharing? ## Concepts in this document - **memory.wiki** _(entity)_ The primary product platform being developed and documented. - **URL as API** _(concept)_ Core architectural principle where every Memory.Wiki URL serves as a fetchable API endpoint for AI consumption - **Knowledge Graph** _(tag)_ Graph-based representation of entities and relationships tied to memory.wiki concepts. - **Knowledge Delivery Problem** _(concept)_ The fundamental issue that knowledge gets trapped in closed containers instead of being deliverable across AI tools - **mdfy.app** _(entity)_ Legacy product being migrated to memory.wiki brand with 1+ year redirect maintenance planned. - **Scope reduction** _(concept)_ Strategic decision to cut features from 8 to 3 for launch, enabling the 16-week deadline and iterative post-launch evolution. - **LLM memory layer** _(concept)_ Repositioned value proposition: memory.wiki as fundamental infrastructure for LLM services rather than a standalone note-taking tool. - **Capture/Digestion/Utilization** _(concept)_ Three-tier architecture describing the user authoring flow, AI-driven graph organization, and consumption by external AI systems. - **AI platform integration** _(concept)_ Ability to paste memory.wiki URLs into ChatGPT, Claude, Gemini, and Cursor, enabling multi-platform AI consumption. - **3-tier pricing model** _(concept)_ Planned business model with Free, Pro, and Team tiers to monetize the platform, though specific pricing undefined. - **Markdown sharing tool** _(concept)_ The original product positioning before strategic evolution toward AI-native knowledge graph. ## Concept relations (within this doc's concepts) - **memory.wiki** positioned as **LLM memory layer** - **Knowledge Delivery Problem** solved by **LLM memory layer** - **memory.wiki** addresses **Knowledge Delivery Problem** - **memory.wiki** builds and surfaces **Knowledge Graph** - **memory.wiki** rebrand from legacy **mdfy.app** - **memory.wiki** implements **URL as API** - **Scope reduction** refines launch of **memory.wiki** - **URL as API** enables **AI platform integration** - **memory.wiki** monetized via **3-tier pricing model** - **mdfy.app** rebranded to **memory.wiki** - **Knowledge Delivery Problem** solved by **URL as API** - **mdfy.app** migrates to **memory.wiki** _Hub canonical:_ https://memory.wiki/hub/raymindai _Concept digest:_ https://memory.wiki/raw/hub/raymindai?digest=1&compact=1