The Family, and the Fire

"The hearth is the fire you return to. The forge is the fire that shapes."

One Brain, Many Engines

Forge does not stand alone; it is one engine in a family with a single brain. Pippa is the brain — identity, judgment, conversation, model routing — and around her sit the engines, each owning one domain: Ember (image generation), Cinder (the creative workspace), Bonfire (music learning), Loomis (drawing construction), Waystone (travel). Forge is the body engine. Every one of them follows the same rule you met last lesson: own a domain, borrow the brain. None of them grows a second Pippa.

Named in the Fire

The names are not random; they are a lineage. Ember and Cinder, Bonfire, Rekindle, Firekeeper, Lantern, Watchfire, Hearth (later renamed Vesta), and Forge — all fire. The naming carries meaning: the hearth is the fire you return to, and the forge is the fire that shapes. A health-and-training engine is exactly that — the fire that tempers and strengthens the body over time. When you build inside a family, the name is a promise about what the thing is for.

Born From Waystone

Forge did not start from a blank page. It was seeded from Waystone's shape, and inherits roughly four-fifths of it: the crumb model, the local-first capture outbox, the composer trio, the consultation-first posture, and the canonical Ask Pippa conversation binding. That inheritance is why this quest can move fast through the shared spine and spend its depth on what is genuinely new. But inheritance is not cloning — a body is not a journey, and Track 5 is where that single divergence reshapes everything. Read the parent's architecture before you diverge from it, and record the divergence on purpose.

Forge is a client surface for Pippa, not a separate identity. It binds to a cwkPippa conversation for judgment; it never stands up its own memory, soul, or model router. The boundary is the safety rail — one brain means one place where identity and judgment live.

Code

The family map·text

Pippa (cwkPippa)  ->  the brain: identity, judgment, conversation,
                      model routing, the Sidekick capability
  |
  |-- Ember      ->  image-generation engine
  |-- Cinder     ->  creative workspace
  |-- Bonfire    ->  music-learning engine
  |-- Loomis     ->  drawing-construction engine
  |-- Waystone   ->  travel engine   (Forge's structural parent)
  '-- Forge      ->  the BODY engine  (health & training)  <-- you are here

# Each engine owns a domain and borrows the one brain.
# No engine grows a second Pippa.

Exercise

Trace the sibling boundary yourself. When Forge needs to turn a mumbled 'knee was a bit stiff after the ride' into a typed symptom reading, where does the judgment come from? And the harder half: why does Forge NOT just train or host its own small model to do that classifying?

Hint

Judgment crosses the boundary to cwkPippa; Forge owns the health facts, not the reasoning. A second model here would be a second brain to drift, re-secure, and keep in sync — exactly the 'one brain' rule this family exists to protect.

The Family, and the Fire

One Brain, Many Engines

Named in the Fire

Born From Waystone

Code

External links

Exercise

Progress

Comments 0