C.W.K.
Stream
Lesson 02 of 04 · published

Crumbs Are Raw Material, the Draft Is the Derivative

~11 min · crumbs, drafts, provenance, source-vs-derivative

Level 0Cold Hearth
0 XP0/34 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete
"Crumbs are the raw material. The draft is the derivative."

Two Kinds of Thing, Never Confused

Everything in Vesta reduces to two nouns, and the entire architecture depends on never mixing them up. A crumb is a piece of raw evidence — a fragment you captured, immutable and append-only, that means exactly what it meant the moment you dropped it. A draft is a derivative — prose Pippa assembled by reading a set of crumbs, and it carries the exact IDs of the crumbs it read. The crumb is the negative; the draft is the print. You can make many prints from one negative, and you never scratch the negative to make a print.

If you have ever worked with an event log and a materialized view, this is the same shape. Events are the source of truth: they happened, they are never edited, you only append. The view is derived: you can rebuild it, replace it, or keep several different views over the same events. Vesta is that pattern pointed at a diary — crumbs are the events, drafts are the views.

Evidence is immutable; projections are disposable. A crumb can never be rewritten by an assembly — only appended to through an explicit revision. A draft can be regenerated, discarded, or joined by a second draft that reads the same crumbs differently. Confusing the two is how journals quietly lose the truth of what was actually written down.

Provenance Is Not a Summary

When Pippa assembles a draft, it doesn't just produce prose — it records source_crumb_ids, the precise list of crumbs that fed the draft. That's provenance, and it is exact, never a paraphrase. Months later you can open a paragraph and walk back to the three fragments it grew from. The draft is allowed to be beautiful and interpretive; the crumbs underneath it stay literal and addressable forever.

The Same Crumbs, Read Twice

Because assembly never consumes anything, a crumb that fed Monday's reflective draft is still fully available to feed a year-end review, or a completely different draft that reads the same day through another lens. Two drafts over the same crumbs, telling different stories, are not a conflict to resolve — they're a supported outcome. The raw material is inexhaustible; only the derivatives are opinions.

Code

A crumb (evidence) and a draft (derivative) that cites it·json
// crumb — append-only, means what it meant when captured
{
  "id": "01J8Z...crumb",
  "text": "the light in the kitchen at 6pm was the whole day",
  "target_date": "2026-03-14",
  "kind": "text"
}

// draft — a projection that names its exact sources
{
  "id": "01J9A...draft",
  "title": "A Quiet Saturday",
  "target_date": "2026-03-14",
  "source_crumb_ids": ["01J8Z...crumb", "01J8Z...b", "01J8Z...c"],
  "status": "accepted"
}
// regenerate the draft as often as you like — the crumbs never change

External links

Exercise

Take one real memory from this week and split it into the two nouns. First write the crumb: the smallest raw fragment, exactly as you'd have captured it in the moment. Then write a one-paragraph draft that could have been assembled from that crumb plus two others. Notice that the draft interprets, while the crumb only records.
Hint
If your 'crumb' already reads like finished prose, it's actually a draft — push it back down to the raw fragment. The crumb should feel almost too small to be worth keeping. That smallness is the point.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.