Roz — Your Local Brain
Roz is the local brain that ships with every ModelReins Companion. She stores your routing patterns, memories, and learned behaviors in a database on your machine.
What Roz does
Section titled “What Roz does”- Remembers your preferences — which models you use for what, your quality thresholds, your routing patterns
- Stores the Imprint — the starter template every new Roz gets. Default routing rules and quality gate settings.
- Accumulates Lore — everything Roz learns after the Imprint. Your Lore is unique to you.
- Feeds the Matriarch — the Matriarch reads Roz’s knowledge to make routing decisions
What Roz isn’t
Section titled “What Roz isn’t”- Roz’s database isn’t replicated to a ModelReins-side store. The SaaS routes job dispatch and coordination — it doesn’t sync Roz’s brain back up to us.
- Roz isn’t an account on our servers. There’s no ModelReins-side mirror of Roz’s memories with your name on it.
- Roz isn’t held hostage. If you stop using the SaaS, Roz and her database stay on your machine and continue to work locally.
This is the substrate posture: we don’t collect Roz’s memory because Roz’s memory lives on your hardware. The SaaS is the dispatch relay; Roz is the brain. Different layers.
One Roz per Range
Section titled “One Roz per Range”Every fleet (Range) has exactly one Roz. If you install the Companion on multiple machines, they all share the same Roz. The second install detects the existing Roz and syncs from it instead of starting fresh.
You can rename Roz
Section titled “You can rename Roz”Roz is the default name. You can rename your brain to whatever you want.
If your brain was installed before June 2026 it’s probably still named Bob — brains keep their names; Roz is the default for new installs.
The Imprint and Lore
Section titled “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 Roz learns after the Imprint. Your routing preferences, review patterns, cost thresholds. Lore is what makes your Roz different from everyone else’s.
Data is tagged at creation: pattern (Imprint, shareable) or instance (Lore, private to the keyholder).
Why Roz?
Section titled “Why Roz?”The name carries a dual lineage. It’s a warm, everyday name — and it’s ROZZUM unit 7134 (“Roz”) from Peter Brown’s The Wild Robot: a machine that arrives with factory programming, learns the lore of her territory, becomes its matriarch, and refuses to be repossessed by the company that built her. (With a nod to Monsters, Inc.’s Roz — the deadpan dispatch-desk clerk secretly running the whole operation, the routing brain.) The canon maps onto product truths: the factory Imprint is the Imprint, learning her territory is Lore, becoming the range’s matriarch is the Matriarch, and refusing repossession is Export Roz / Import Roz — she stays on your hardware if you leave the SaaS. Nothing held hostage; your hardware.