Assisted
Elidyne observes and proposes. A person takes every action.
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.
Authority, provenance and access are evaluated as each action happens. Governance stops being an audit exercise and becomes part of the run itself.
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.
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.
| Action | Elidyne | Requirement |
|---|---|---|
| Read engineering data | Allowed | Entitlement scope |
| Propose a plan | Allowed | Evidence attached |
| Commit compute | Gated | Owner approval |
| Change a live setpoint | Gated | Standing grant + bounds |
Identity, entitlements and engineering data come from your existing estate, so control is expressed once and applied everywhere instead of being rebuilt per tool.
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.
Elidyne observes and proposes. A person takes every action.
Elidyne prepares the action. A named approver releases it at the gate.
Actions inside the agreed bounds pass on policy. Anything outside waits.
Elidyne also refines its own recipes, still inside policy and on the record.
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.
Provenance is a side effect of doing the work, so nobody spends the last fortnight of a programme rebuilding the paper trail.
Gates sit at consequential decisions, so autonomy speeds up the routine without quietly absorbing the judgement calls.
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.
Six products, one control pane. Governance mainly carries Limits, Act and Trace; the rest of the loop is already connected when you need it.
Places the gates in every plan and records each sign-off and request for changes.
Open Workbench →02 · Work in ElidyneHolds the standing grants behind every write to a live system.
Open Operations →03 · Work in ElidyneMakes release a gate and keeps limitations on the page.
Open Reports →04 · Under the hoodSets what Elidyne may read, propose and do, and logs every refusal.
Open Agents →05 · Under the hoodEnforces classification and residency before any job is placed.
Open Compute →Limits, approvals and trace for every loop
You are hereMeasure → Twin → Test → Limits → Act → Trace. Every product serves the same six steps, in every loop.
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.