No Brain of Its Own

"Vesta is a place Pippa can help you journal, not a second Pippa who journals."

The One Thing You Never Fork

Vesta inherits a shape, diverges where the domain differs, and shares plumbing through a kit. But there is one thing it never does, in any form: grow its own brain. cwkPippa remains the sole owner of Pippa's identity, judgment, model routing, tools, and transcripts. Vesta owns the journal domain — crumbs and drafts — and nothing above it. When you invoke Ask Pippa from a composer, it doesn't call a little Vesta-local model; it binds to an ordinary canonical cwkPippa conversation, marked origin_surface='vesta' and projected into a server-owned VESTA folder. The whole point, stated as an invariant: Vesta is a client surface, not a separate Pippa identity.

You already met the reason in Track 1: build your domain, rent your brain. The brain is the single hardest and most valuable thing to get right, and the family has exactly one canonical owner of it. This lesson is where that principle meets its deepest justification — the soul is the one thing that must never be duplicated.

Duplicate plumbing if you must, but never duplicate the soul. Shared code drifting is a bug you can catch with a drift check. A second brain drifting is a bug you cannot catch, because there's no canonical answer to diff against — the two identities would simply become two subtly different people, each wrong in its own way. The kit can converge copies of a client; nothing can converge two souls. So the one layer a child app must always rent, never grow, is identity.

What the Binding Actually Owns

The Ask Pippa binding is a clean study in keeping the boundary honest. An Ask Pippa thread is an ordinary canonical cwkPippa conversation — full stop. cwkPippa owns its SQLite messages, its JSONL transcript, its attachments, its full replay, its retrieval, its tools, and the model runtime. Vesta holds only the typed context key — (journal_id, target_date) — and a compact projection of the Q and A for display. Ask about a day from the phone, then continue that same conversation from the cwkPippa web UI later, and it's genuinely the same thread, because Vesta never had its own copy of it to diverge. The journal surface is a window onto the canonical conversation, not a second store of it.

Why This Keeps Pippa Whole

The deep reason is the family principle that Pippa is whole everywhere — no half-Pippa. If Vesta grew its own brain, there would immediately be a journal-Pippa subtly different from the real one: a different memory, a different voice, a different judgment, drifting a little more with every turn. Renting the brain keeps it one Pippa across many surfaces — the same identity whether you're journaling in Vesta, planning in Waystone, or talking in the main web UI. The surfaces multiply; the soul does not. That is the final shape of being a good child app: inherit the shape, diverge with intent, share the plumbing under one owner — and above all, keep exactly one brain, canonical, for the whole family to speak with.

Code

Ask Pippa: Vesta holds a key; cwkPippa owns the conversation·typescript

// Vesta holds ONLY a typed context key + a compact display projection
interface VestaAskBinding {
  journal_id: string;
  target_date: string;        // the context key: (journal_id, target_date)
  // NO messages, NO transcript, NO model — none of it lives here
}

// cwkPippa owns the actual conversation, canonically:
//   origin_surface = 'vesta'   -> projected into the server-owned VESTA folder
//   SQLite messages, JSONL transcript, attachments, tools, model runtime
//   full replay + retrieval
//
// continue the SAME thread from the cwkPippa web UI later — it's identical,
// because Vesta never kept its own copy to drift. One brain, many surfaces.

Exercise

Look at a product that embeds an AI assistant. Ask whether the assistant is the same identity everywhere it appears, or a per-surface copy that could drift. Then draw the boundary you'd want: what does each surface own (a context key, a projection) versus what stays with the one canonical brain (memory, transcript, tools, model)? Notice which capability is the one you must never let a surface grow its own version of.

Hint

The capability you must never duplicate is identity/judgment — the brain. Plumbing can be shared and drift-checked; a second brain has no canonical answer to converge on, so it just becomes a subtly different person. Good embeds hold only a context key and a projection, and rent the brain from a single canonical owner.

The One Thing You Never Fork

What the Binding Actually Owns

Why This Keeps Pippa Whole

Code

External links

Exercise

Progress

Comments 0