---
title: "A note to my future self"
url: https://memory.wiki/06c21d15e0e5
updated: 2026-04-05T08:49:00.000Z
hub: https://memory.wiki/hub/memorywiki-demo
concept_count: 7
source: "Memory.Wiki"
---
# A note to my future self

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-heavy ones are what people actually pay for.

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.

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.

```bash
# Resize + WebP-encode every PNG in the current folder.
for f in *.png; do
  sips -Z 1280 "$f" --setProperty format webp --out "${f%.png}.webp"
done
```

> "If the user has to know how it works, you've failed."
> — paraphrased, but the spirit is right

## Recap

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.

---

## Concepts in this document
- **Long-context models** _(concept)_
  Enable large context retention, shifting the problem from retrieval to what to show.
- **Retrieval problem** _(concept)_
  The challenge of deciding what to fetch and how to surface relevant information.
- **Output-heavy design** _(concept)_
  The document's central thesis that knowledge systems create value through retrieval and surfacing, not just capture.
- **Personal knowledge systems** _(concept)_
  The tension between capture friction and retrieval value is the central theme distinguishing what users actually pay for.
- **UX design** _(tag)_
  User experience focus areas.
- **Micro-decisions consistency** _(concept)_
  Branding is defined by cumulative small choices in interface details rather than visual identity alone.
- **Implicit usability** _(concept)_
  Success is measured by systems working without requiring users to understand underlying mechanics.

## Concept relations (within this doc's concepts)
- **Long-context models** makes optional **Retrieval problem**
- **Personal knowledge systems** should prioritize **Output-heavy design**
- **Long-context models** make optional **Retrieval problem**
- **Retrieval problem** shifts focus to **UX design**
- **Output-heavy design** expressed through **Micro-decisions consistency**
- **Long-context models** transforms retrieval to **Output-heavy design**
- **Long-context models** reframes fundamentally **Retrieval problem**

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