---
title: "Show HN plan (working draft)"
url: https://memory.wiki/r_HaRypO
updated: 2026-05-14T18:15:49.480Z
hub: https://memory.wiki/hub/demo
bundle_count: 1
concept_count: 12
source: "memory.wiki"
---
# Show HN plan (working draft)

> Living plan that I refine before launch day.

## Title

**Show HN: mdfy – Your AI memory, deployable to any AI**

Alternates I'm holding: "Markdown URLs as a memory layer for Claude, ChatGPT, Cursor" / "I built the personal wiki Karpathy described, then deployed it as a URL." Current preference is the first — leads with our line and the cross-AI differentiator.

## Body — target ~400 words, no marketing language

Opens with: "I've been building mdfy for ~8 weeks. Today I'm shipping v6, which turns it from a markdown publisher into a memory layer."

Then: the thesis (LLMs read markdown, URLs cross every boundary, so your memory should be a markdown URL).

Then: what it does today, bulleted.
- Capture from any AI (Chrome ext, MCP, paste).
- Capture from anywhere else (GitHub, Notion, Obsidian, files).
- Bundle by topic with AI-synthesised analysis.
- Hub auto-clustering into a concept index.
- llms.txt + bundle digests + recall API.
- Cross-AI wiring via AGENTS.md / CLAUDE.md / .cursor/rules.

Then: what's interesting (in *my* voice).
- Cross-AI is structural moat.
- Authored memory ≠ extracted memory.
- Graph-RAG-as-URL (not Graph-RAG-as-service).
- The Karpathy wiki shape, deployed as URL.

Then: stack. Then: try it (free, no signup).

Then: "Happy to dig into anything technical, the cross-AI thesis, why I left X to do this, or where I think this goes if it works."

## Anticipated questions, pre-drafted answers

1. **Isn't this just Notion + AI?** — Notion's AI works in Notion. mdfy works wherever the URL goes.
2. **What about Mem0 / Letta / extracted memory?** — Different question. Mem0 asks what the AI should remember; mdfy asks what *you* want to remember.
3. **How is this different from GitHub Pages + markdown?** — Capture surfaces, hub layer, cross-AI deployability.
4. **Won't AI companies just build this?** — They structurally can't. Their incentive is the wall.
5. **Pricing?** — Free during beta. Pro $X/mo after launch (price TBD).
6. **Why are you doing this?** — Trillions of tokens of high-quality AI-assisted thinking are being created daily and lost to chat histories nobody returns to. I want to catch the part you actually meant to keep.

## Timing

Tuesday or Wednesday, 7 AM PT. I'll be online and responding for 6 hours minimum.

## What I'm explicitly not doing

- Recruiting upvotes from Slack.
- Posting in any other forum within 24 hours of the HN post.
- Buzzword pile-up.
- Reddit-style "let me know what you think!" tail.


---

## Concepts in this document
- **mdfy** _(entity)_
  A tool that stores project context and decision history, integrated into Cursor via custom rules.
- **Structural moat** _(concept)_
  The defensible advantage created by mdfy's vendor-neutral positioning, which competitors cannot replicate due to inherent conflicts of interest.
- **Claude** _(entity)_
  Anthropic's AI model cited as an example of vendor lock-in through projects and memory features.
- **Hacker News** _(entity)_
  Primary GTM channel chosen for high ICP overlap with developers and format alignment with technical credibility.
- **Cursor** _(entity)_
  Code editor that consumes mdfy bundles as context for chat and composer sessions.
- **ChatGPT** _(entity)_
  Example of an AI provider whose memory feature is intentionally confined to its own product.
- **Cross-AI memory** _(concept)_
  The core thesis: a memory layer that persists across multiple AI providers simultaneously, structurally unavailable to single-vendor AI companies.
- **Anthropic** _(entity)_
  Incumbent AI vendor mentioned as competitive threat with integrated memory and user lock-in.
- **Show HN Launch** _(concept)_
  Central launch strategy focused on Hacker News as primary channel.
- **Launch Strategy** _(tag)_
  The overarching theme covering all aspects of the product launch preparation and execution.
- **mdfy product** _(entity)_
  The core product being developed with build-in-public approach and AI integration as substrate.
- **Competitive Positioning** _(tag)_
  How the product differentiates from alternatives and establishes unique market position.

## Concept relations (within this doc's concepts)
- **Launch Strategy** encompasses approach **Show HN Launch**
- **Competitive Positioning** includes strategy **Structural moat**
- **Structural moat** enables differentiation **Competitive Positioning**
- **Hacker News** primary channel **Launch Strategy**
- **Cross-AI memory** creates advantage **Structural moat**
- **Claude** developed by **Anthropic**
- **mdfy** integrates with **Claude**
- **mdfy** solves problem for **ChatGPT**
- **mdfy** integrates with **Cursor**
- **Structural moat** enables **Cross-AI memory**
- **Cursor** positioned to deliver **Cross-AI memory**
- **mdfy** integrated into **Cursor**

## Bundles containing this document
- [Launch strategy: Show HN week](https://memory.wiki/b/DlrrKcQ2)
  > Pre-launch plan + GTM channels + what not to do. The strategy bundle a reviewer can read end-to-end.

_Hub canonical:_ https://memory.wiki/hub/demo
_Concept digest:_ https://memory.wiki/raw/hub/demo?digest=1&compact=1