The harness
Agents design. Code runs. People decide.
What sits under every product. Built in telecom network operations, applied to oil operations.
Prepared
Context joined before the alarm
Explained
Every call with its evidence
Rehearsed
Each response run in a twin first
Governed
Read-only. A person decides.
Parts
ContextJoined before the alarm
More
Asset register, the line model, the batch plan, planned work, the drills, the approved responses, the weather and the roads. One alarm is joined to them by deterministic reads. Nothing is invented at alarm time.
EvidenceEvery call carries its proof
More
A verdict is a hypothesis with a probability, conditional on a model, with the readings that support and contradict it. UNEXPLAINED when unsure. An alarm is annotated, never cleared.
TwinsDeterministic. Same seed, same answer.
More
Engines that run in the browser or on the edge box, answerable over MCP. They rehearse a leak, a pump trip, a station outage or a shutdown and report spill, throughput and pressure for each option. Reduced-order; labelled unverified until a field comparison exists.
PlaybooksResponses as contracts
More
A response is written once, plain for a person and exact for a machine: intent, the context it needs, the tools it may call, the approval before any change, the failure policy. Checked, rehearsed, scored, then compiled. Fired by an event. Each step leaves a receipt.
HandoffRequests with a clock and evidence
More
When a person or a crew must act, the harness raises a request: done-when lines, the evidence, a party, a clock, accepted by someone who took no part.
HostInside the platform you already run
More
On the IT side, a work-management suite: your tenancy, your region. For the control-room overlay, an on-premises bench. Nothing leaves. No public model is contacted at run time.
LearningLearned between builds, never live
More
An outcome becomes a drill, a precondition and a rule at the next build, verified and signed. At run time no model is in the loop.
Two clocks
Design time
- Agents ask typed questions, three perspectives and an adversary
- Verified by running the product
- Accepted by a person; shipped byte-identical
Run time
- No model in the loop
- Deterministic reads, twins, playbooks
- Proposals a person confirms; every step leaves a receipt
Rules
Read-only
Reads exports, journals, registers. Never writes to OT.
Exported
Starts on files you already export. No console link until a pilot grants a replica.
Explained
Cause and evidence on every call. Says UNEXPLAINED when unsure.
Rehearsed
Responses run in a twin before they are proposed.
Approved
A fixed rulebook checks. A named person approves.
Receipted
Every step leaves a signed receipt.
Sovereign
Your tenancy, your region, your devices. Nothing phones home.
Honest
Every figure labelled: measured, inferred, assumed, simulated.