Provenance & Evidence
Trace engineering values back to their source.
Platform / 04
Trust & engineering control
Give autonomy a clear operating boundary.
Make every action, result and decision reviewable: policy governs what can happen, people retain authority where it matters, and evidence stays connected to its source.
ObserveAllowed
ProposeAllowed with evidence
ExecuteApproval required
ExportPolicy controlled
Capabilities
Control that runs with the work, not after it.
Authority, provenance and access are evaluated as each action happens. Governance stops being a retrospective audit exercise and becomes a property of the run itself.
•
Human Approval
Explicit approval before consequential execution.
Policy & Authority
Control what AI can observe, propose and execute.
Secure Enterprise Access
Identity, organisations, SSO, entitlements and controls.
Connectors & Engineering Data
Connect storage, PLM, lab and engineering systems.
01Provenance
Every number can be walked back to its source.
Provenance is captured as work happens: which input, which model version, which solver settings, which prior 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
- Approved by
- Thermal lead · 12 Mar
- ✓Inputs, model versions and settings recorded per computed value
- ✓Derived quantities linked to the runs and datasets they came from
- ✓Evidence chains exportable for review, audit or regulatory submission
02Authority
Authority is explicit, and it is enforced.
Policy states what the system may observe, what it may propose and what it may execute. Consequential actions stop at a gate and wait for a named person—there is no implicit escalation.
AUTHORITY MODEL
ACTIONAGENTREQUIREMENT
Read engineering dataAllowedEntitlement scope
Propose a planAllowedEvidence attached
Commit computeGatedOwner approval
Export resultsGatedPolicy + classification
- ✓Observe, propose and execute governed as separate permissions
- ✓Approval gates bound to roles, not to whoever is nearest the keyboard
- ✓Refused and pending actions recorded alongside completed ones
03Connection
Connected to the systems the work already lives in.
Identity, entitlements and engineering data come from your existing estate—SSO, PLM, storage, lab and test systems—so control is expressed once and applied consistently rather than re-implemented per tool.
GOVERNED CONNECTIONS
Policy engineSSO / identityPLMObject storageTest & labRequirementsEvidence store
- ✓SSO, directory groups and organisation-level entitlements respected end to end
- ✓PLM, storage, lab and test systems connected as governed sources
- ✓Access decisions logged with the identity and policy that produced them
Why this is the precondition
Why this is the precondition, not the polish.
Evidence is captured, not reconstructed
Provenance is a side effect of running the work, so nobody spends the last two weeks of a programme rebuilding the paper trail.
Humans stay accountable where it counts
Approval gates sit at consequential decisions, so autonomy speeds up the routine without quietly absorbing the judgement calls.
One policy, applied everywhere
The same authority model governs connected, private and air-gapped deployments—including what may leave the boundary.
Where control is the requirement
Where control is the whole requirement.
Licensing and regulatory submissions
Produce evidence chains that stand up to a regulator asking where a number came from.
Requirements traceability
Bind requirements to the analysis, evidence and decisions that satisfy them.
Export-controlled programmes
Enforce classification and residency rules on every action, including exports and model transfers.
Supplier and partner collaboration
Share results without sharing the underlying IP, under entitlements you set.
Recorded, not asserted
Governance as a property of the run.
Actions attributed
Every observation, proposal and execution carries an identity, a policy and a timestamp.
Authority levels
Observe, propose and execute governed independently, per role and per environment.
Silent escalations
Consequential actions wait at a gate. Nothing widens its own authority.
Illustrative platform targets. Actual outcomes vary by workflow, model and deployment environment.
ELIDYNE / 04
“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.
Meet Elidyne ↗ Perspectives
Request the briefing pack ↗Further reading on trust & engineering control.
TRUST
WORKING PAPER · 9 MINObserve, propose, execute: an authority model for engineering agents
Request it ↗04
/ 04
GUIDE · 11 MIN/ 04
Evidence chains that survive a regulatory submission
Request it ↗FIELD NOTE · 7 MIN
Connecting PLM and lab systems without duplicating policy
Request it ↗ Start a mission
Bring the question your reviewers always ask.
We will show what the answer looks like when provenance, authority and approval are captured while the work runs.