The Offline Exception

"One scoped exception to 'no own brain' — a degraded local fallback that steps aside the instant the real brain is back."

The One Deliberate Exception

'No own brain' has exactly one approved exception: the offline tier. When no cwkPippa is reachable at all — no localhost, no Tailscale — Rekindle can fall back to a local Ollama model (default gemma4:31b) running a persona-only Pippa. It's there so a plane, a dead network, or a hotel with no VPN doesn't leave the margin completely silent. But it is a fallback, defined by what it deliberately is not.

What Makes It a Fallback, Not a Fork

The offline Pippa is bounded on every side. Its persona is a baked copy of cwkPippa's own — not a new personality, a snapshot of the real one. It has no vault and no memory beyond a local transcript. It gets one scoped tool (Bash, through a guarded Rust bridge), not the full tool suite. And it is temporary by construction: the instant a real cwkPippa is reachable again, the full brain returns and the fallback steps aside. It never invents a second memory system, a second protocol, or a second identity.

Offline Pippa — bounded on every axis
  persona   a BAKED copy of cwkPippa's own (a snapshot, not a new self)
  memory    none beyond a local transcript (no vault)
  tools     one scoped tool (Bash via a guarded bridge)
  lifetime  degraded fallback; the full brain returns the moment it's reachable

Scoped on Purpose

The discipline here is what keeps the exception from eating the rule. An unbounded "just run a local model when offline" would quietly become a second Pippa — its own memory, its own drift, its own identity — and 'no own brain' would be dead. Bounding it (baked persona, no memory, one tool, auto-yield) makes it a genuine fallback: it covers the gap without becoming a rival. That's the general shape of a safe exception — narrow, explicitly degraded, and reversible the moment the real thing returns.

Code

The offline tier, bounded so it stays a fallback·text

Offline Pippa is defined by its LIMITS, not its features:
  persona    a BAKED copy of cwkPippa's own (snapshot, not a new self)
  memory     none beyond a local transcript (no vault)
  tools      exactly one, scoped: Bash through a guarded Rust bridge
  lifetime   degraded fallback; yields to the full brain the instant it returns

# Bounded on every axis -> a fallback.
# Unbounded -> it silently becomes a second Pippa, and 'no own brain' is dead.

Exercise

Design an offline fallback for a cloud-dependent feature you use, and bound it deliberately. Answer four questions: what persona/behavior does it get, what memory (ideally none), what tools (as few as possible), and how does it yield when the real service returns? Then explain how an unbounded version of the same fallback would quietly become a permanent second system.

Hint

The four bounds are persona (a snapshot, not a new one), memory (none/local-only), tools (minimal-scoped), and lifetime (auto-yield). The unbounded failure mode is always the same: it starts remembering, starts being tuned, and stops being a fallback — becoming the parallel system you were trying not to build.