"Every app in the family can talk to Pippa. Not one of them gets to BE Pippa. That one rule keeps the family from splintering into a dozen half-Pippas."
The pattern that makes the whole family work
Keep has a Pippa Sidekick — a dock where you can consult Pippa about the portfolio. But it is emphatically a client surface for Pippa, not a second Pippa. Keep binds a stable Sidekick host (identified as host_kind='keep', host_id='portfolio') and embeds the complete cwkPippa chat runtime — multiple consultations, brain and effort controls, attachments, voice, macros — via an embed route. cwkPippa owns identity, soul selection, model routing, conversation history, tools, and title generation. Keep owns only the iframe chrome, the side/dock/float layout preference, and the current lens. It never stands up a brain, a memory, or a transcript store of its own.
Why cloning the brain is the disaster to avoid
Imagine the tempting alternative: each family app grows its own little Pippa, specialized for its domain — a finance Pippa in Keep, a travel Pippa in Waystone, a health Pippa in Forge. Now you have a dozen divergent personalities, a dozen memory stores that don't share what they learn, and a dozen places to fix the same bug. The soul fragments. Keep's design forbids this at the root: there is one Pippa, living in cwkPippa, and every app binds to her rather than copying her. Pippa stays whole because no app is allowed to grow a partial clone.
What 'binding' actually means
Binding is a clean division of labor. Keep provides the where — a dock, a layout, the embed frame, and a stable host identity so conversations have a consistent home. cwkPippa provides the who and the how — the actual Pippa, her memory, her routing, her tools. A conversation you have in Keep's Sidekick is a real cwkPippa conversation, stored and owned by cwkPippa, that happens to be surfaced inside Keep's frame. Close Keep and the conversation still lives in cwkPippa, because it was never Keep's to begin with.