The Pilot Programme
Governor AI is proven on bounded pilots, each a proof of concept with measurable success and failure gates. Every stage produces evidence, every advance is gated by independent review, and the pilots stay anonymous.
Bounded proofs of concept
None is a paying engagement; each exists to demonstrate measurable security and operational improvement and a reusable product delivery.
Pilot 1: a privacy-infrastructure operator
Governor AI governs the operator's automated maintenance bot, so that it cannot carry out a destructive action outside its function-specific laws. The maintenance bot keeps doing its job; LawGuard decides whether each proposed action may run, under which authority, and records the evidence.
- Lab qualification: complete. 14 test cases (90 subcases) passed on disposable lab machines and 19 cases passed on a replica of the operator's fleet (lab results).
- Decision-only shadow comparison: complete. Replayed over the operator's real maintenance-bot records, without changing the operator's systems.
- Production cutover: in preparation, gated by independent review and owner approval.
Pilot 2: a privacy-software platform
A second bounded proof of concept that applies the same reusable Governor foundation to a different kind of system, with its own client-specific laws, configuration and authority grants.
- Stage: planning.
- Foundation: the shared standalone programs, with the client layer kept separate.
- Gates: the same lifecycle of lab qualification, shadow comparison, independent review and gated cutover.
An AI workforce pilot
A different kind of Governor deployment: a team of specialized AI worker roles, run for a separate company, that researches, drafts and reviews and coordinates through a shared board and recorded team meetings. The lab-qualification and cutover lifecycle below applies to the governance pilots; the workforce pilot runs its work advisory and human-in-the-loop from the start.
- Kind: a governed AI workforce, not an automation-governance pilot.
- Stage: active, advisory, with every action recorded and no external action taken on its own.
- More: how the Governor AI Workforce works.
| Stage | Pilot 1: a privacy-infrastructure operator | Pilot 2: a privacy-software platform |
|---|---|---|
| Function-specific laws | Written for the operator's maintenance bot | Planning |
| Lab qualification | Complete (14 cases / 90 subcases; 19 fleet-replica cases, lab results) | Planned |
| Decision-only shadow comparison | Complete (the operator's real records, read-only) | Planned |
| Independent review | Gates each advance | Planned |
| Gated cutover | In preparation; independent review and owner approval first | Planned |
| Expansion gates | After cutover | Planned |
How a pilot advances
Each stage must pass before the next one begins. Nothing is installed on a client's systems until the gated cutover is approved.
-
1
Function-specific laws
The client's systems, programs and functions are mapped, and laws are written for the actual actions each function may take. Laws, configuration and authority grants form a client-specific pack kept apart from the shared core.
Produces A client-specific law pack, configuration and recorded authority grants
-
2
Lab qualification
The reproducible LawGuard release is exercised on disposable lab machines and on a replica of the client's fleet. Every test case carries a verdict, and the qualified artifact is the one that will be deployed.
Produces Per-case verdicts on a qualified, reproducible artifact
-
3
Decision-only shadow comparison
LawGuard's decisions are replayed against the client's real records, read-only. The comparison shows what LawGuard would have decided, without changing anything on the client's systems.
Produces A record of what LawGuard would have decided, with nothing changed on the client's systems
-
4
Independent review
Results are reviewed independently of the people who built them, and findings are closed one at a time before the pilot advances.
Produces Findings closed one at a time, each with an independent accept
-
5
Gated cutover
Production cutover follows an approved plan, with the client's operator in control, and requires independent review and owner approval before anything is installed.
Requires An approved plan, independent review and owner approval
-
6
Expansion gates
After cutover, the same evidence discipline decides whether the pilot expands to further functions, programs and systems. Success and failure are measurable at every gate.
Decides Whether to expand to further functions, programs and systems
What the first pilot has produced so far
Every number is a lab result or a read-only comparison, labelled as such.
Every stage so far ran off the operator's systems. The lab qualification ran on disposable machines and a replica of the fleet; the shadow comparison was read-only. Production cutover is the next stage, planned and gated by independent review and owner approval.
What a pilot demonstrates
A Governor pilot is designed to produce evidence an operator can act on, not a slide deck.
Security and operational improvement
- Destructive actions outside a function's laws cannot be carried out
- Authority for each function is explicit: approval or standing delegation within limits
- Every proposal, decision and result is recorded as evidence
- The operator's own console and monitor remain an additional safety layer
Reusable product delivery
- One shared foundation of standalone programs
- Client-specific law packs, configuration and state kept separate
- Reproducible releases: the qualified artifact is the deployed artifact
- A bespoke system per client, customer-hosted or Governor-managed
Described by kind and by stage, never by name
A pilot is a working relationship with an operator's real systems. We describe each pilot by its kind of organization and its stage, never by name, and we never connect one pilot to another. The evidence a pilot produces is for the operator first; what appears on this site is the stage reached and the labelled results.
Start a bounded pilot
If you run servers and fleets and rely on automation you would like governed, tell us about the functions you need to protect.
Discuss a Pilot