---
title: "JSON schema for a doc with attachments"
url: https://memory.wiki/e7a714048331
updated: 2026-03-23T07:23:00.000Z
hub: https://memory.wiki/hub/memorywiki-demo
concept_count: 12
source: "memory.wiki"
---
# JSON schema for a doc with attachments

A good error message answers three questions: what happened, why it happened, and what to try next. Most ship the first, hint at the second, and forget the third. The fix is usually a single sentence longer.

Reading other people's code is a higher-leverage activity than writing your own. You learn three things at once: what works, what doesn't, and why someone smart picked the trade-off you'd never have considered. The ratio of read-to-write hours quietly separates the engineers who plateau from the ones who keep compounding.

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.

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

## 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
- **Long-context models** _(concept)_
  Core idea enabling retrieval-optional UX by keeping broader context in view.
- **Cross-AI portability** _(concept)_
  Portability across AI vendors enabled by public URLs that survive pivots.
- **Memory.Wiki** _(entity)_
  Central knowledge hub system referenced across documents as the platform for saving thoughts, URLs, photos and grounding AI responses.
- **Claude** _(entity)_
  AI provider evaluated for long context and instruction-following strength, with weakness in tiny prompt latency.
- **GPT-4o** _(entity)_
  AI provider evaluated for multimodal and fast performance, with weakness in long-session drift.
- **Markdown** _(entity)_
  Format mentioned as a practical, sufficient baseline.
- **Cursor** _(entity)_
  Code-aware editor with specialized ranking, locked to editor environment.
- **Branding consistency** _(concept)_
  Branding is the sum of micro-decisions and is central to product perception.
- **Branding** _(tag)_
  Branding as a set of micro-decisions rather than a logo.
- **Forcing function** _(concept)_
  A forcing function is essential for momentum in a 1-person startup.
- **Delivery model matters** _(concept)_
  Core thesis that how you deliver content matters more than how you retrieve it.
- **Error message design** _(concept)_
  Example of product quality where most implementations skip the third critical element: actionable next steps.

## Concept relations (within this doc's concepts)
- **GPT-4o** trades off in **Long-context models**
- **Cross-AI portability** enabled by **Memory.Wiki**
- **Memory.Wiki** enables **Cross-AI portability**
- **Claude** exemplifies strength in **Long-context models**
- **Memory.Wiki** implements context grounding with **Long-context models**
- **GPT-4o** compared against **Claude**
- **Claude** compared with **GPT-4o**
- **GPT-4o** alternative for multimodal **Long-context models**
- **Cross-AI portability** transcends constraints of **Long-context models**
- **Markdown** exemplifies principle of **Cross-AI portability**
- **Long-context models** utilizes as context **Memory.Wiki**
- **Claude** is an example of **Long-context models**
- **GPT-4o** is an example of **Long-context models**
- **Cursor** integrates with **Long-context models**

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