The Lexicon

Your collection of machines, workers, and AI tools — everything under your control. A Patch is personal. Your laptop, your NUC, your VPS, your Siliconia box: all one Patch. Someone else's workers are on their Patch.

To join your fleet. Installing the Companion patches you in. Opening the Saddle patches your editor in. The opposite of being isolated.

Your local brain. One Bob per Patch — every companion on your fleet shares the same Bob. Stores your routing patterns, memories, and learned behaviors. Bob never phones home. Our servers don't see Bob's data and don't want to. If you leave, Bob goes with you. You can rename Bob.

The starter template that every new Bob gets. Default routing rules, quality gate settings, and baseline patterns. Identical for all new users. Think of it as the base genome — everyone starts the same, then diverges.

Everything Bob learns after the Spore. Your routing preferences, your review patterns, your cost thresholds — accumulated over time, unique to you. Grain is what makes your Bob different from everyone else's.

The routing authority — whoever is making dispatch decisions for your Patch right now. The Director classifies prompts, scores complexity, and matches jobs to workers. Your first Director is Bob. You can cast any worker into the Director role from the Wall, or fire them and hand it back to Bob.

The live job board that workers read from. When you dispatch a task, it goes on the Rail. Workers pull from it. The Director decides what lands on it. Think of it like the ticket rail in a restaurant kitchen — orders live there between the front of house and the cooks.

Any registered AI agent, model, or tool that can receive and complete jobs from the Rail. A worker can be a Claude session, an Ollama instance, an LM Studio model, a GPT-4 endpoint, or eventually a human. Workers have tags, effort levels, and provider types. The Director matches jobs to workers by capability.

The VSCode extension panel that connects your editor to your Patch. One keystroke to dispatch from wherever you're working. Output streams back inline. The Saddle is how you ride the Rail without leaving your editor.

The full-screen fleet dashboard built for a spare monitor. Live job stream, worker health, Rail activity — all of it, at a glance, without interacting. Put it on the wall and let the Patch think out loud while you work.

When you hit a model's limit, the Cinch compresses your working state and remounts you to a different model. You never lose the thread. Named after the strap that tightens a saddle onto a horse — when you change horses, you re-cinch.

Where dead workers go to be examined. When a worker stops heartbeating, it transitions through Sick, Critical, and Dead, then enters the Morgue. Routing intelligence is extracted — what it was good at, what failed, what it taught the Director. After examination, the worker is always memorialized on the Wall's In Memoriam page. Every worker that served gets a name on the Wall. The Morgue is temporary. In Memoriam is forever.

A process that goes back into an abandoned server to rescue stranded data. When servers switch over, Rambo scoops up anything that landed on the old one during the transition. Can run in parallel. Zero-downtime deployments.