Platform/Under the hood/Governance

Every loop, inside a visible boundary.

Governance is what makes Elidyne the control pane where every loop is watched, tested, approved and traced. It decides what each loop may read, propose and do, system by system: gates hold consequential steps for a named person, standing grants bound every action on a live system, and provenance traces every number back to its source.

Provenance of one valueTrace complete
Walk any number back. Inputs, model, solver settings and approver are captured while the work runs.
What Governance covers

Control that runs with the work, not after it.

Authority, provenance and access are evaluated as each action happens. Governance stops being an audit exercise and becomes part of the run itself.

§ 01Approval gatesConsequential steps wait for a named person. Accept, request changes or refuse, all on the record.
§ 02Standing grantsBounds, rate limits, watchdogs and a fallback for every point Elidyne may change on a live system.
§ 03Autonomy levelsL1 to L4, set per system and changed per shift, campaign or change window.
§ 04ProvenanceInputs, model versions, settings and approvers captured for every computed value.
§ 05Identity and accessSSO, directory groups and entitlements respected from end to end.
§ 06ConnectorsStorage, PLM, lab, test and plant systems connected as governed, read-first sources.

Every number can be walked back to its source.

Provenance is captured as work happens: which input, which model version, which solver settings, which earlier result. A value in a report can be expanded until you reach the raw data behind it.

Provenance · margin = +9.1 K
Derived from
Run 24 · thermal steady state
Model
Assembly v7 · mesh 4.2 M
Solver
CFD suite · settings locked
Inputs
Duty cycle D-3 · material MS-11
Accepted by
Thermal lead · 12 Mar

Authority is explicit, and it is enforced.

Policy states what Elidyne may observe, what it may propose and what it may do. Consequential actions stop at a gate and wait for a named person. There is no implicit escalation.

Authority model
ActionElidyneRequirement
Read engineering dataAllowedEntitlement scope
Propose a planAllowedEvidence attached
Commit computeGatedOwner approval
Change a live setpointGatedStanding grant + bounds

Connected to the systems the work already lives in.

Identity, entitlements and engineering data come from your existing estate, so control is expressed once and applied everywhere instead of being rebuilt per tool.

Governed connections
Autonomy levels

You set how far each loop may act.

Elidyne builds and operates the loop; your engineers approve. Autonomy is a setting per system, not a property of the model: raise it when the evidence supports it, lower it for a shift, a campaign or a change window.

L1

Assisted

Elidyne observes and proposes. A person takes every action.

L2

Supervised

Elidyne prepares the action. A named approver releases it at the gate.

L3

Governed

Actions inside the agreed bounds pass on policy. Anything outside waits.

L4

Self-improving

Elidyne also refines its own recipes, still inside policy and on the record.

Grants, in the product

Every control point has a grant.

On the Operations desk, each point Elidyne may change shows its grant: the level, the bounds, the fallback, who approved it and until when. Pausing writes stops every grant at once.

app.elidyne.ai / buoy-a3 / operations / grantsOpen full screen ↗
Loading the workspace…
  • Bounds and rate limits enforced before a command leaves the gateway
  • A fallback the asset’s own controller applies if the link goes quiet
  • Grants that expire, and must be renewed by a named approver
  • One switch for the operations desk to pause every write
Why it comes first

The precondition, not the polish.

01

Evidence is captured, not reconstructed

Provenance is a side effect of doing the work, so nobody spends the last fortnight of a programme rebuilding the paper trail.

02

People stay accountable where it counts

Gates sit at consequential decisions, so autonomy speeds up the routine without quietly absorbing the judgement calls.

03

One policy, applied everywhere

The same authority model governs connected, private and air-gapped deployments, including what may leave the boundary.

Trust is not a feeling about a model. It is a property you can demonstrate, action by action.
We build for the moment a reviewer, an auditor or a regulator asks the hardest possible question, and the answer is already attached.
How it connects

Governance and the other five.

Six products, one control pane. Governance mainly carries Limits, Act and Trace; the rest of the loop is already connected when you need it.

  1. 01Measure
  2. 02Twin
  3. 03Test
  4. 04Limits
  5. 05Act
  6. 06Trace

Measure → Twin → Test → Limits → Act → Trace. Every product serves the same six steps, in every loop.

Start a mission

Bring us the system that matters.

Bring the question your reviewers always ask. We will show what the answer looks like when gates, grants and provenance are captured while the work runs.