---
mw_bundle: 1
id: ce89afb82fe7
title: "v8 launch plan"
url: https://memory.wiki/b/ce89afb82fe7
document_count: 3
updated: 2026-05-29T00:08:00.000Z
source: "Memory.Wiki"
---
# v8 launch plan

> v8 launch plan — a curated set of memories grouped by theme. Reviewer note: this is generated demo content.

**Intent:** decompose

## Documents

### 1. [Travel notes: Seoul → Tokyo](https://memory.wiki/cd48bf42bf7c)
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.

### 2. [On-device OCR is good enough for most capture flows](https://memory.wiki/930f037e970c)
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. [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.


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