---
mw_bundle: 1
id: ggAzbcHr
title: "memory.wiki: Knowledge Graph as AI-Native Infrastructure"
url: https://memory.wiki/b/ggAzbcHr
document_count: 8
updated: 2026-05-21T02:50:47.440Z
analysis_generated_at: 2026-05-21T02:50:47.440Z
source: "Memory.Wiki"
---
# memory.wiki: Knowledge Graph as AI-Native Infrastructure

> The vision, architecture, and business rationale behind memory.wiki — a personal knowledge wiki that serves as a URL-based memory layer for any AI.

## Summary

These documents chronicle the comprehensive development of memory.wiki, a personal knowledge wiki that functions as a deployable memory layer for AI systems. The collection traces the evolution from the initial mdfy concept through multiple business plan iterations to a finalized product specification, consistently centered on the principle that knowledge should be URL-accessible to any AI platform.

## Themes

- URL-native knowledge delivery
- Cross-AI platform strategy
- User authoring vs AI extraction
- Knowledge graph automation

## Cross-document insights

- The reframing from 'AI memory problem' to 'knowledge delivery problem' represents a fundamental strategic insight that differentiates memory.wiki from competitors like Mem0 and Letta
- The structural impossibility for big tech companies (OpenAI, Anthropic) to build cross-AI solutions creates a sustainable competitive moat for independent developers
- The tension between comprehensive vision and shipping constraints led to multiple scope revisions, revealing the challenge of balancing ambition with execution timelines
- The evolution from mdfy to memory.wiki shows how branding and positioning can crystallize around a core technical insight (URL as API) to create clearer market positioning

## Key takeaways

- Memory.wiki's core innovation is treating URLs as APIs that any AI can fetch, solving knowledge delivery rather than memory storage
- The three-tier architecture of capture/digestion/utilization with user authoring and AI organization creates a sustainable differentiation from extraction-based competitors
- Strategic focus on cross-AI compatibility leverages a structural advantage that big tech companies cannot replicate due to competitive constraints

## Open questions / gaps

- Competitive analysis depth - limited discussion of how existing tools like Obsidian or Roam Research compare beyond basic positioning
- Technical implementation details - while the vision is clear, specific technical challenges like AI model costs, scaling, and infrastructure are underexplored
- User research validation - the documents are founder-driven without evidence of customer interviews or usage data to validate core assumptions

## Notable connections

- **doc:fz45GXXj** ↔ **doc:UwZWUmdo** — The manifesto's 'delivery vs memory' thesis directly informs the product specification's dual-door architecture and URL-as-API principle
- **doc:xv6A2DKS** ↔ **doc:nvF3Li2x** — The revised plan systematically reduces v7's scope from 8 features to 3 while preserving the core strategic thesis and architecture
- **doc:8QB0olhs** ↔ **doc:Tk71NDw0** — The accessible explanation in the recap directly maps to the formal three-tier architecture specified in the technical document
- **doc:pBEnMXSs** ↔ **doc:xv6A2DKS** — The evolution overview serves as meta-commentary on the finalized business plan, highlighting the strategic transformation process

## Concepts (this bundle)

- **URL as API**
- **Three-Tier Architecture**
- **Knowledge Graph**
- **Cross-AI Compatibility**
- **Delivery vs Memory Problem**
- **User Authoring**
- **LLM Self-Maintenance**

## Concept relations

- **Cross-AI Compatibility** ↔ **URL as API** — enables through
- **Knowledge Graph** ↔ **LLM Self-Maintenance** — built by

1. [memory.wiki 사업계획 v7 (FINAL)](https://memory.wiki/qHc1FWxq) — Complete business plan v7 detailing the 3-tier architecture (capture/digestion/utilization) and knowledge graph vision

2. [memory.wiki 사업계획 v7 (FINAL)](https://memory.wiki/xv6A2DKS) — Duplicate business plan v7 with full strategic thesis on knowledge graphs as AI APIs

3. [memory.wiki — Product Specification](https://memory.wiki/Tk71NDw0) — Product specification defining link graphs, semantic search, and LLM self-organization as core graph features

4. [Memory.wiki Business Plan and Architecture](https://memory.wiki/pBEnMXSs) — Architecture synthesis explaining how the knowledge graph serves as a URL-native API for AI systems

5. [내가 memory.wiki를 만드는 이유](https://memory.wiki/fz45GXXj) — Founder's manifesto on the delivery problem that knowledge graphs solve — AI memory through structured URLs

6. [memory.wiki — Product Specification Synthesis](https://memory.wiki/UwZWUmdo) — Product spec synthesis covering dual-door vision: personal wiki + deployable memory graph for AI

7. [memory.wiki 사업계획 v7-revised](https://memory.wiki/nvF3Li2x) — Revised v7 plan focusing on graph-first features with reduced scope for launch viability

8. [Mdfy v6 recap](https://memory.wiki/8QB0olhs) — Simple explanation of how markdown URLs create a knowledge graph accessible to any AI


_Digest view — follow any link above to fetch that doc's full markdown. Add `?full=1` to this URL for the concatenated payload._