---
title: "The 30-second cache rule"
url: https://memory.wiki/dc400be3d9c2
updated: 2026-04-27T07:56:00.000Z
hub: https://memory.wiki/hub/memorywiki-demo
bundle_count: 1
concept_count: 5
source: "Memory.Wiki"
---
# The 30-second cache rule

Cross-AI portability is the structural moat OpenAI and Anthropic can't build for themselves. The user's context, exported as a public URL, becomes infrastructure that survives any single vendor's pivot. That's why the right primitive isn't an API key — it's a permalink.

The hardest part of a 1-person startup isn't the work — it's the lack of a forcing function. Without a meeting on Tuesday, nothing has to ship on Monday. The schedule has to come from somewhere, and "because I said so" isn't enough.

Markdown won because it was always good enough. Not the best at any one thing — never the fastest editor, never the prettiest output, never the most semantically rich. But always close enough that the switching cost killed every alternative.

### Capture-flow check-list

- [x] Pulled from Safari via Share Sheet
- [x] OCR'd a whiteboard photo
- [x] Dictated three voice memos walking to coffee
- [ ] Imported the long PDF I was avoiding
- [ ] Cleaned the inbox folder

```swift
// SwiftUI: keep all five tab views mounted across tab switches so
// each view's @StateObject model persists.
ZStack {
    ForEach(AppTab.allCases, id: \.self) { tab in
        view(for: tab)
            .opacity(router.selectedTab == tab ? 1 : 0)
            .allowsHitTesting(router.selectedTab == tab)
    }
}
```

| Provider | Strength | Weakness |
|---|---|---|
| Claude | Long context, instruction following | Slow for tiny prompts |
| GPT-4o | Multimodal, fast | Drifts on long sessions |
| Cursor | Code-aware ranking | Locked to editor |

The thesis here[^1] is that delivery model matters more than retrieval quality.

[^1]: First articulated in the W6 internal note "Graph RAG is delivery, not retrieval."

## Recap

The hardest part of a 1-person startup isn't the work — it's the lack of a forcing function. Without a meeting on Tuesday, nothing has to ship on Monday. The schedule has to come from somewhere, and "because I said so" isn't enough.

---

## Concepts in this document
- **Output-Heavy Systems** _(concept)_
  Knowledge tools that prioritize surfacing information over capturing it.
- **Linear** _(entity)_
  Design philosophy benchmark for default-easy, hard-possible workflows.
- **Long-Context UX** _(concept)_
  The shift from retrieval-based systems to presentation-based systems.
- **Permalink Infrastructure** _(concept)_
  Using public URLs as a vendor-agnostic portability layer.
- **Forcing Functions** _(concept)_
  External constraints required to maintain productivity in solo ventures.

## Concept relations (within this doc's concepts)
- **Long-Context UX** enables better **Output-Heavy Systems**

## Bundles containing this document
- [Personal-knowledge-management notes](https://memory.wiki/b/400b3906b96a)
  > Personal-knowledge-management notes — a curated set of memories grouped by theme. Reviewer note: this is generated demo content.

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