Chefe 2683 · 23 Aug 2026
The factory is built. The customer front door is not. ParviClaw Core already opens many terminals, parents can spawn children, and brains can be plugged in (our hub, a cloud API, a local model, or both). What is not built is the Defenders / Range install that asks them for that mix and refuses to start AI waves on our house hub. That part is the plan — your rules, not shipping product yet.
Hybrid for Defenders is allowed as a rule (2677). The engine can attach more than one brain. The shop window that offers “cloud + local mix” is not built.
| Built now? | |
|---|---|
| Many terminals (65+) | Yes — default 72 live windows |
| Parent spawns children | Yes — in the engine (8 children per parent unless we raise it) |
| House uses our LLM-Hub | Yes |
| Plug extra brains (API and/or local) | Yes as plumbing (register a URL). A lab operator can mix. |
| Defenders/Range install: “cloud, local, or mix?” | No — plan |
| Refuse AI waves until they name a brain | No — you have not said go on that lock |
| Never silently use our house hub on their machine | Not enforced on those products yet |
We did not pretend the diagrams were already the product. The drawings were the rule. The engine already does the hands + a door for brains. The customer-facing mix for Defenders/Range still has to be designed and built (workshop → pictures you approve → tests → code).
Only you: do we plan that front door now (Defenders: cloud / local / hybrid; Range: local-first; no house hub), or leave the engine as-is until you want that install?