regulatorA control plane for agents

An orchestrator on Pi that applies Stafford Beer's Viable System Model as a control architecture. Prompts advise. Types describe. Gates enforce.

Get started

The control plane

GitHub

Gates, not personas

Forty-two active regulators. Each one is a registry record that names the failure it absorbs, where it is enforced, its tests and its stated limitations. A gate without a limitation does not pass the check.

A small loop that owns execution

The loop runs contract, dispatch, verify, route and close, with leases, budgets and worktree isolation around it. The recovery policy is declared as data and read by the loop. Nothing reads its own progress off the repository.

Evidence a host runs

The host verifies tests, checks, the inherited suite, the export signature, the protected identity and the glossary at a revision. The model's account of its own work is one more layer on top of that evidence and never the only one.

Obligations with an owner

Every finding, question, proposal and escalation is owed to S3, S5 or a named person. It holds the units it names until someone dispositions it, and it is delivered to an outbox with reminders while it waits.

Identity you cannot prompt away

Invariants, the glossary and the boundaries are files under S5 authority. A unit may propose a change to them, and only a person, checked against the interaction policy, may accept one.

Measured, not asserted

The eval harness runs declared arms, ablation per regulator, repetitions and confidence intervals. On that evidence a regulator earns its place in the registry or is retired.