Where Waygate Sits

"One brain. Many surfaces. Waygate is the one that touches your files."

A Family, Not a Suite

Waygate does not stand alone. It is one sibling in a family of native apps and engines that all orbit a single brain called Pippa, who lives in one codebase (cwkPippa). Each sibling owns one domain and borrows everything else. The lineage even carries a theme — fire — because the apps were named in a burn cycle: Cinder and Ember, then Bonfire, then Rekindle, then Firekeeper. Waygate is the file workbench: the sibling whose whole job is helping you see, select, and safely change the files on your machine.

The Rule That Keeps It Coherent

There is exactly one Pippa, and she is not in Waygate. Identity, conversation, memory, model routing — all of that lives in cwkPippa. Waygate has no own brain. When it wants to talk to Pippa, it mounts a Sidekick dock: a web view pointed at cwkPippa's embed surface, bound to a conversation that belongs to cwkPippa, not Waygate. That single rule is why a file manager can stay small and sharp — it isn't also trying to be an AI platform.

The Machine-Scoped Dock

The clever part is that the dock is scoped to the machine. Each Mac's Sidekick gets its own conversation, and the cwkPippa side reads that machine's file-workbench state, so the Pippa in the dock is always talking about the files in front of you — not some other Mac's. Waygate itself still runs no server and owns no brain; it just hosts a view and hands cwkPippa a read-only window into its own state.

A surface borrows the brain instead of rebuilding it. That is why Cinder can be a drawing sidecar, Rekindle a prose editor, and Waygate a file workbench — each small, each sharp — while exactly one Pippa, in one place, stays the mind they all share.

Why this quest exists. Every cwk sibling app earns a self-referential quest that teaches its own architecture as a concept — not a repo to clone. This is Waygate's. By the end you could build your own bounded file workbench, having watched this one explain itself.

Code

The fire-family, by domain·text

  Pippa      (cwkPippa)     the one brain: identity, memory, routing
    |
    +-- Cinder                drawing workspace (Photoshop sidecar)
    +-- Ember                 image-generation engine
    +-- Bonfire               music-learning engine
    +-- Rekindle              prose editor
    +-- Firekeeper            voice / dictation
    +-- Waygate               <-- YOU ARE HERE: the file workbench

  Each sibling owns ONE domain. None of them owns a second Pippa.

The Sidekick dock, conceptually·text

  Waygate window
  +--------------------------------------------------+
  | sidebar |  Pane A  |  Pane B  | [ Sidekick dock ] |
  |         |          |          |  a web view of    |
  |         |          |          |  cwkPippa's        |
  |         |          |          |  /embed/waygate    |
  +--------------------------------------------------+
                                        |
              host_kind = 'waygate', host id scoped per Mac
              cwkPippa reads THIS Mac's workspace read-only

  Waygate runs no server, owns no brain. It hosts a view.

Exercise

Pick two apps you use that both 'have AI features.' For each, ask: does it run its own model and memory, or is it a surface onto a brain that lives elsewhere? Then decide which architecture you'd choose if you were building a family of five apps that all needed the same assistant.

Hint

If each app ships its own model and its own memory, they will drift — different capabilities, different personalities, different bugs. The 'one brain, many surfaces' pattern trades a little per-app independence for a family that actually stays coherent. That trade is the whole reason Waygate has no brain of its own.

A Family, Not a Suite

The Rule That Keeps It Coherent

The Machine-Scoped Dock

Code

External links

Exercise

Progress

Comments 0