---
title: "The structural moat: cross-AI portability"
url: https://memory.wiki/rBRZ_nni
updated: 2026-05-14T17:52:48.410Z
hub: https://memory.wiki/hub/demo
bundle_count: 1
concept_count: 12
source: "memory.wiki"
---
# The structural moat: cross-AI portability

## One line summary

> A single AI vendor can build deeper integration against its own model than mdfy ever could. None of them can deliver a URL that works across their competitors. The portability is the product.

## Why this matters

Notion, Mem.ai, Roam, Obsidian — each is a destination. The user is asked to live inside the tool. mdfy is the opposite shape: the user lives wherever they already work (ChatGPT, Cursor, Claude Code) and mdfy is the thing that travels with them.

## What gets ported

- The doc body (clean markdown)
- The graph analysis (themes, insights, concept relations) attached to bundles
- The concept index attached to hubs
- Privacy gating (Public / Restricted / Private) — the URL behaves the same way the rendered viewer does

## Why the AI vendors can't replicate

OpenAI building "ChatGPT memory that Claude can read" is a competitive negative for them. Anthropic the same. The asymmetry is structural — mdfy benefits from being *not aligned* with any single vendor.

## Failure modes

- If one vendor builds a dominant memory layer that all AIs respect → mdfy still survives as the UX layer (curate, capture, share) but loses the "they can't" part
- If `llms.txt` adoption stalls → the URL contract weakens. Mitigate by treating `llms.txt` as one of multiple paths; raw markdown + clean URLs are the durable spec.

Bottom line: the moat depends on the URL contract, not on any one feature.


---

## 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.
- **bundle URL** _(entity)_
  The delivery mechanism for markdown digests that now carries embedded graph analysis instead of doc list only
- **mdfy Platform** _(entity)_
  Knowledge management platform designed for AI-first workflows with URL-based sharing.
- **Cursor IDE** _(entity)_
  Code editor that can fetch and utilize mdfy bundle URLs for project context.
- **ChatGPT** _(entity)_
  Example of an AI provider whose memory feature is intentionally confined to its own product.
- **AI Integration** _(tag)_
  Artificial intelligence features and infrastructure including vector search and multi-provider setup.
- **llms.txt** _(concept)_
  Plain-text discoverability standard for AI agents at site root, analogous to robots.txt and sitemap.xml.
- **Vendor neutrality** _(concept)_
  Design commitment to support Claude, OpenAI, Gemini, and open-source models equally without single-vendor dependencies.
- **viral loop** _(concept)_
  Growth mechanism dependent on URLs being self-contained and more valuable to receivers than senders could provide
- **AI Memory** _(tag)_
  Broad category encompassing how AI systems maintain and access knowledge across sessions.

## Concept relations (within this doc's concepts)
- **Cursor IDE** fetches **bundle URL**
- **Structural moat** requires **Vendor neutrality**
- **mdfy** integrates with **Claude**
- **mdfy** solves problem for **ChatGPT**

## Bundles containing this document
- [Engineering decisions + cross-AI strategy](https://memory.wiki/b/8IkpnVgX)
  > A working bundle: the ADR for shipping graph_data in URLs, the cross-AI moat argument, and a hands-on integration note for Cursor. Three docs that explain *what we're building and why* in 10 minutes o

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