---
type: "synthesis"
primary_sources: ["s11", "s18", "s21", "s22", "s24", "s40"]
tags: ["mcp", "lock-in", "open-protocols", "skills", "memory"]
id: "arc-walled-garden-vs-open"
sources: ["cross-day"]
---
# The Walled-Garden Argument

Six videos build a coherent strategic claim: **AI vendors will use feature design (memory, skills, custom GPTs, native integrations) to create lock-in — and the user's only defense is to insist on open formats and standards**.

## The Lock-In Pattern

### S11 — Storage Lock-in (Don't Let Knowledge Live in SaaS)

[[concept-file-over-app]]: the philosophical anchor. Store knowledge in markdown / SQL you control, not inside Notion / Obsidian's proprietary format. [[action-own-your-context-layer]] is the operational rule.

### S18 — Memory Lock-in (The 5th Capital Surrender)

[[claim-ai-memory-lock-in]]: ChatGPT and Claude memory features are deliberate platform-stickiness mechanisms via [[concept-honing-effect]]. [[claim-shadow-ai-usage]]: 60-90%+ of workers use personal AI for work, voting with their feet against IT-imposed lock-in. [[concept-tool-switching-penalty]] is the daily tax. The escape: [[concept-mcp]] (bidirectional read/write open protocol) + BYOC architecture.

### S21 — The Anti-SaaS Build (Skip Lovable)

[[contrarian-anti-saas]]: build the visual layer yourself with free LLM code-gen + [[entity-vercel-d21]] free tier, instead of paying [[entity-lovable-d21]] for an AI app builder.

### S22 — The Open Stack (Notion is Dead)

[[contrarian-notion-is-dead]]: Notion / Evernote are wrong-paradigm for the [[concept-agent-web]]. Migrate to [[entity-postgresql]] + [[entity-pgvector]] + [[concept-model-context-protocol|MCP]] — described as "the USB-C of the AI age." [[contrarian-corporate-memory-is-hostile]] reframes vendor memory features as switching costs disguised as conveniences.

### S24 — Shadow Agents (The Org Version)

[[concept-shadow-agents]]: the AI equivalent of Shadow IT — unsanctioned team-built RAG pipelines and agent stacks. Symptom of vendor fragmentation. Fix: [[action-build-mcp-infrastructure|unified context infrastructure]] on open protocols.

### S40 — The Inadvertent Anti-Lock-In Feature

[[contrarian-ecosystem-lock-in]]: the funniest moment in the series. [[concept-claude-skills]] are stored as Markdown files. Anthropic chose Markdown for adoption ergonomics inside Claude — and inadvertently produced a *universal super-prompt generator* exportable to ChatGPT and Gemini. [[claim-skills-are-platform-agnostic]] · [[quote-nobody-is-talking-about-this]]. [[concept-skill-file-format]] (S12, .skill files) is the same pattern at the design-system layer.

## The Strategic Synthesis

The series argues a coherent posture for any AI buyer or builder:

1. **Storage** — own your data in open formats ([[concept-file-over-app]]).
2. **Protocol** — connect via MCP, not vendor APIs.
3. **Memory** — host the context layer yourself (BYOC).
4. **Skills** — package instructions in Markdown, not vendor-proprietary formats.
5. **Posture** — treat "vendor convenience" features as *latent switching costs*.

This is the through-line that connects six otherwise distinct chapters. The defensive stance is consistent across days even when the surface topic changes (note-taking, design systems, agent skills, memory).

## The Open Question

[[question-corporate-response-mcp]]: how will major labs respond when MCP threatens their lock-in? S18 raises [[question-enterprise-mcp-adoption]]: will enterprise IT block external MCP servers as data-exfiltration risks? S40 raises [[question-anthropic-response-to-export]]: will Anthropic eventually restrict Skill exports? All three ask the same question: *will open protocols survive contact with vendor incentives*?

## Counter-Perspective

The enrichment overlays repeatedly note: native memory features genuinely help casual users; hybrid native+external is viable; full BYOC is overkill outside of power users and serious agentic workflows. The lock-in critique is sharpest for builders, less binding for casual ChatGPT users.

## Connection to Other Arcs

- The [[arc-byoc-memory-architecture|BYOC arc]] is the *positive prescription* — what the open stack actually looks like.
- The [[arc-where-defensibility-migrated|moat arc]] connects: the build layer is collapsing, but [[concept-vertical-context]] (proprietary data + permissioning) is durable when you own it.