Bob — Your Local Brain

Bob is the local brain that ships with every ModelReins Companion. He stores your routing patterns, memories, and learned behaviors in a database on your machine.

What Bob does

• Remembers your preferences — which models you use for what, your quality thresholds, your routing patterns
• Stores the Imprint — the starter template every new Bob gets. Default routing rules and quality gate settings.
• Accumulates Lore — everything Bob learns after the Imprint. Your Lore is unique to you.
• Feeds the Matriarch — the Matriarch reads Bob’s knowledge to make routing decisions

What Bob isn’t

• Bob’s database isn’t replicated to a ModelReins-side store. The SaaS routes job dispatch and coordination — it doesn’t sync Bob’s brain back up to us.
• Bob isn’t an account on our servers. There’s no ModelReins-side mirror of Bob’s memories with your name on it.
• Bob isn’t held hostage. If you stop using the SaaS, Bob and his database stay on your machine and continue to work locally.

This is the substrate posture: we don’t collect Bob’s memory because Bob’s memory lives on your hardware. The SaaS is the dispatch relay; Bob is the brain. Different layers.

One Bob per Range

Every fleet (Range) has exactly one Bob. If you install the Companion on multiple machines, they all share the same Bob. The second install detects the existing Bob and syncs from it instead of starting fresh.

You can rename Bob

Bob is the default name. You can rename your brain to whatever you want.

The Imprint and Lore

Imprint is the seed template. Identical for all new users. Think of it as the base genome — everyone starts the same.

Lore is everything Bob learns after the Imprint. Your routing preferences, review patterns, cost thresholds. Lore is what makes your Bob different from everyone else’s.

Data is tagged at creation: pattern (Imprint, shareable) or instance (Lore, private to the keyholder).