---
title: "Meeting with the legal team — context dump"
url: https://memory.wiki/6045a1f67e69
updated: 2026-03-18T01:46:00.000Z
hub: https://memory.wiki/hub/memorywiki-demo
concept_count: 9
source: "Memory.Wiki"
---
# Meeting with the legal team — context dump

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.

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.

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.

### Today's reading list

1. *Designing Data-Intensive Applications* — chapter 5 (replication)
2. The Hacker News thread on "What I learned writing a JIT"
3. A Stripe engineering blog post about idempotency keys
4. Karpathy's tweet thread about LLM evals

```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)
    }
}
```

| Surface | Latency goal | Notes |
|---|---|---|
| Capture | <1s tap → toast | local-first, server is best-effort |
| Open | <500ms URL → LCP | edge cache for public URLs |
| Search | <250ms keystroke → results | semantic + lexical merged |

The model's loss on the held-out set converged to $\mathcal{L} = 2.41$ after roughly $1.2 \times 10^4$ steps — well above the chance baseline of $\log_2 50{,}000 \approx 15.6$ bits per token but still leaving room for the next architecture pass.

```mermaid
sequenceDiagram
  participant U as User
  participant M as Memory.Wiki
  participant A as AI
  U->>M: Save thought / URL / photo
  M-->>U: Permalink
  U->>A: "Use [URL] as my context"
  A-->>U: Answer grounded in the hub
```

## Next steps

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.

---

## Concepts in this document
- **Markdown** _(concept)_
  A format that succeeded due to low switching costs despite not being the best in any single category.
- **Memory.Wiki** _(entity)_
  Hub/memory repository used as context source.
- **Output-heavy design** _(concept)_
  The document's central thesis that knowledge systems create value through retrieval and surfacing, not just capture.
- **Switching cost** _(concept)_
  The barrier preventing users from adopting alternatives, identified as Markdown's primary competitive advantage.
- **Latency optimization** _(concept)_
  Performance targets (capture <1s, open <500ms, search <250ms) that define user experience constraints.
- **Personal knowledge management** _(concept)_
  Collecting and surfacing knowledge for individuals.
- **SwiftUI state management** _(concept)_
  Technical implementation detail showing how to persist view state across tab switches using ZStack and @StateObject.
- **1-person startup** _(entity)_
  Context for understanding how lack of external forcing functions impacts shipping discipline and scheduling.
- **Semantic + lexical search** _(concept)_
  Hybrid retrieval approach required to surface relevant information within the 250ms search latency goal.

## Concept relations (within this doc's concepts)
- **Memory.Wiki** implements system for **Personal knowledge management**
- **Latency optimization** enables fast surfacing **Output-heavy design**
- **Semantic + lexical search** meets constraint within **Latency optimization**
- **1-person startup** motivates need for **Personal knowledge management**
- **Markdown** demonstrates power of **Switching cost**
- **Personal knowledge management** requires focus on **Output-heavy design**
- **Markdown** wins through low **Switching cost**
- **Markdown** dominates through **Switching cost**
- **Markdown** leverages **Switching cost**
- **Memory.Wiki** implements pattern of **Output-heavy design**

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