---
mw_bundle: 1
id: 400b3906b96a
title: "Personal-knowledge-management notes"
url: https://memory.wiki/b/400b3906b96a
document_count: 4
updated: 2026-06-05T05:20:45.436Z
analysis_generated_at: 2026-06-05T05:20:45.436Z
source: "Memory.Wiki"
---
# Personal-knowledge-management notes

> Personal-knowledge-management notes — a curated set of memories grouped by theme. Reviewer note: this is generated demo content.

**Intent:** decompose

## Summary

This collection decomposes the intersection of modern AI capabilities, personal knowledge management, and solo-founder operations. It argues that long-context models render traditional retrieval obsolete, shifting the challenge to UX-focused delivery. The documents collectively advocate for vendor-agnostic infrastructure via permalinks and output-centric productivity systems.

## Themes

- Long-Context UX
- Vendor Portability
- Solo-Founder Forcing Functions
- Output-Centric Design

## Cross-document insights

- The 'retrieval problem' in AI is actually a 'delivery problem' that can be solved by better UI/UX rather than better search algorithms.
- Permalinks are not just for sharing; they are the fundamental unit of cross-AI portability that prevents vendor lock-in.
- The friction in knowledge management is often misallocated to capture; the real value is in the 'indispensability loop' of surfacing information.
- Solo-founder productivity is not a time-management issue but a structural design issue requiring external forcing functions.

## Key takeaways

- Long-context AI shifts the engineering focus from retrieval infrastructure to UX-driven delivery.
- Portability is a structural moat; use permalinks as the primary primitive for user context.
- Design systems for output, not input; the value of a tool is in what it surfaces, not what it stores.

## Open questions / gaps

- Lack of specific implementation details for the 'indispensability loop' beyond the diagram.
- Missing data on how to handle privacy/security when using public URLs as a portability layer.

## Notable connections

- **doc:2b94a74983a4** ↔ **doc:dc400be3d9c2** — Both documents define the shift from retrieval to delivery in AI.
- **doc:3e47bc1f1576** ↔ **doc:dc400be3d9c2** — Both identify permalinks as the essential primitive for portability.
- **doc:38374b9d8f59** ↔ **doc:53bac621b960** — Both emphasize the importance of output-heavy over capture-heavy systems.

## Concepts (this bundle)

- **Long-Context UX**
- **Permalink Infrastructure**
- **Forcing Functions**
- **Output-Heavy Systems**

## Concept relations

- **Long-Context UX** ↔ **Output-Heavy Systems** — enables better

## Documents

### 1. [The Pragmatic Programmer revisit](https://memory.wiki/38374b9d8f59)
Most personal-knowledge tools optimise for input. The friction is on the way in: capture this thought, file it, tag it, link it. But the value lives on the way OUT — when the system surfaces the right note at the right moment without you asking. Capture-heavy products are easier to build; output-hea…

### 2. [Reading log: October-November](https://memory.wiki/53bac621b960)
The interesting thing about long-context models isn't that they can read more — it's that they finally make the *retrieval* problem optional. When a model can hold the whole repo in context, the question shifts from "what should I fetch?" to "what should I show?". That's a UX question, not an infrastructure one.

### 3. [Notes from Show Your Work](https://memory.wiki/7c265e654e4f)
Branding is not the logo. It's the consistency of every micro-decision: button radius, copy voice, error tone, empty-state warmth. The logo just labels the bag. The branding is what's inside it.

### 4. [The 30-second cache rule](https://memory.wiki/dc400be3d9c2)
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.


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