---
mw_bundle: 1
id: ce89afb82fe7
title: "v8 launch plan"
url: https://memory.wiki/b/ce89afb82fe7
document_count: 3
updated: 2026-06-12T13:02:31.461Z
analysis_generated_at: 2026-06-12T13:02:31.461Z
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

## Summary

The bundle presents a cohesive exploration of long-context models and the shift from retrieval-centric thinking to a delivery-focused, surface-oriented UX. It juxtaposes memory/workflow tooling, branding consistency, and practical code patterns (SSE, on-device OCR, permalinks) across personal knowledge management and software engineering contexts. The documents collectively argue that the value lies in surface-level UX and actionable outputs, rather than raw retrieval capabilities, and illustrate this through memory hubs, capture workflows, and concrete implementation patterns.

## Themes

- Long-context and retrieval vs delivery
- Memory hubs and capture-use workflows
- Branding, UX, and consistent design
- Practical tooling and code patterns
- Graph-based delivery patterns (RAG)

## Cross-document insights

- Non-obvious: The repeated assertion across docs that ‘delivery matters more than retrieval’ reframes what to optimize (UX surfacing vs data fetch).
- Non-obvious: Permalinks are proposed as foundational context carriers, not API keys, signaling a shift toward persistent, shareable context tokens.
- Non-obvious: The memory hub (Memory.Wiki) appears as both conceptual anchor and practical tool, linking capture flows with UX outcomes.
- Non-obvious: Branding is treated as an internal consistency signal that significantly influences user perception, beyond logos.

## Key takeaways

- The central point is that long-context models enable a wire to surface the right information rather than merely fetch it.
- Permalinks and a memory hub become core primitives for persistent, context-rich workflows.
- Branding as a micro-decision framework matters for user experience and adoption.

## Open questions / gaps

- Lack of empirical evaluation comparing retrieval- vs delivery-focused designs across real tasks.
- Missing privacy and security considerations for memory hubs and shared context tokens.
- Concrete migration steps or playbooks to move an existing system toward a delivery-first architecture.

## Notable connections

- **doc:53bac621b960** ↔ **doc:f3224c2c4808** — shared emphasis on long-context and UX delivery
- **doc:53bac621b960** ↔ **doc:cd48bf42bf7c** — shared capture-organize-use flow concepts
- **doc:2182e26c732f** ↔ **doc:53bac621b960** — branding and permalinks appear across both as primitives
- **doc:cd48bf42bf7c** ↔ **doc:930f037e970c** — delivery-focused patterns in travel/UX context vs OCR capture
- **doc:8b7d51af2961** ↔ **doc:strippy** — placeholder to indicate cross-linkage of memory hub references

## 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._