"Waystone talks to Pippa. It never becomes a Pippa. That single refusal is the family's oldest rule."
The Deepest Reuse Is the Brain
Of everything Waystone reuses, the brain is the one that matters most, because it is the one most tempting to fork. It would be so easy for a travel app to grow its own little conversation store, its own model calls, its own memory of what you asked. Waystone refuses all of it. It never grows a parallel soul, conversation store, or model router. When you use Ask Pippa inside Waystone, you are not talking to a travel-flavored copy of Pippa — you are talking to the Pippa, through a canonical cwkPippa conversation.
How Ask Pippa Actually Binds
Each Ask Pippa thread is scoped to a (journey, local date) and binds to one ordinary canonical cwkPippa conversation, marked with a travel origin and projected into cwkPippa's own WAYSTONE system folder. The ownership split is precise: cwkPippa owns the messages, the transcript log, the attachments, the full replay, the retrieval, the model routing, and every tool the vessel supports. Waystone owns only the schedule key and a compact question-and-answer projection. Switching to a different day resolves a different canonical conversation, so history is retained per day without Waystone ever building a transcript of its own.
Migration, Not a Parallel Store
An earlier version of Ask Pippa did keep a small local log. When the canonical binding landed, that log was not kept as a second home for conversations — it became a one-time migration source, read once to import old questions and answers into canonical conversations, and never written to again. This is the tell of a real 'no own brain' commitment: not just declining to build a brain, but actively retiring the half-brain you already had. A parallel store that lingers 'just in case' is a fork waiting to drift; retiring it to migration-only is how you keep the binding honest.