The Draft Is a Function of the Crumbs

"Two drafts over the same crumbs, read differently, are a supported outcome — not a conflict to resolve."

A Draft Is Derived, Never Primary

You already know crumbs are evidence and drafts are projections. Here's the consequence that makes the whole model calm: a draft is a function of its crumb set. Give assembly the same crumbs and you can produce a draft again; the crumbs are the input, the draft is the output, and the crumbs are never mutated in the process. A draft is derived, never primary — which is the opposite of the classic 'living document', where the document itself is the truth and every edit is a one-way change you can't take back.

Because the draft is derived, three freedoms fall out for free. It's regenerable: lose it, dislike it, or change the assembly and you can rebuild it from the crumbs. It's disposable: throw a draft away and you've lost a rendering, not a memory. And it's pluralizable: nothing stops you from keeping two drafts over the same crumbs, each reading the day through a different lens.

Derive the expensive thing from the durable thing. Keep the raw evidence as the asset you protect, and treat every polished output as a cheap, replaceable rendering of it. When the beautiful artifact is a projection rather than the source, you can experiment with it freely — because the thing you'd be afraid to lose was never the artifact.

Why This Makes Assembly Low-Stakes

Here's the payoff. If a draft were primary — if assembling consumed the day into finished prose — then every assembly would be a high-stakes, one-shot event you'd hesitate to trigger. Instead, because the draft is just a projection, proposing one costs nothing permanent. Pippa can offer a draft, you can reject it, and you've lost nothing; you can ask for another reading and compare; you can accept one today and generate a completely different one at year's end. The freedom to experiment comes directly from the draft being derived. That's why the next lesson can treat assembly as a relaxed consultation rather than a committing operation — the architecture already removed the risk.

The Crumbs Are the Asset

So what do you actually protect? The crumbs. They are the append-only evidence, the thing a lifetime accrues, the input every future draft will read. The drafts come and go — beautiful, interpretive, disposable. A journal that confused the two would guard its polished pages and let its raw fragments rot. Vesta does the reverse: it guards the fragments and lets the pages be as fluid as you like.

Code

draft = assemble(crumbs) — crumbs are the input, never touched·python

def assemble(crumbs, history) -> Draft:
    # reads crumbs (and relevant history), returns prose + provenance
    # DOES NOT mutate any crumb
    return Draft(
        text=propose_prose(crumbs, history),
        source_crumb_ids=[c.id for c in crumbs],  # exact provenance
    )

day = load_crumbs(journal, "2026-03-14")

reflective = assemble(day, history)      # one reading
factual    = assemble(day, history)      # regenerate anytime
year_end   = assemble(day, broader_ctx)  # a third, different lens

# all three exist happily; `day` is byte-for-byte unchanged after each call

Exercise

Pick something in your workflow that you treat as precious and final — a formatted report, a summary doc, a slide deck. Ask: is it primary (the source of truth, edited destructively) or could it be derived from more durable raw inputs? Sketch what the raw 'crumbs' underneath it would be, and notice how much braver you'd be with the output if you could always regenerate it.

Hint

The tell is fear of editing: if you're scared to change the artifact because you can't get the old version back, it's primary. If there's a raw source you could re-derive it from, the artifact could be a cheap projection — and you'd stop treating a rendering like an irreplaceable original.

The Draft Is a Function of the Crumbs

A Draft Is Derived, Never Primary

Why This Makes Assembly Low-Stakes

The Crumbs Are the Asset

Code

External links

Exercise

Progress

Comments 0