Platform/How it fits together

Agents, twins and controls, as one governed loop.

Elidyne builds the loops that run your physical systems. Each is specialised agents, physics twins and controls, working as one governed loop: it measures what is real, tests every change on a twin first, and acts only inside the limits your engineers set. Every decision is traced; every cycle compounds.

One Scientific LoopCycling
Measure → Trace. Limits is where your engineers set the gate that stands before Act.

Copilots answer.

One question, one response. The system never hears about it.

Agents finish tasks.

A plan, a job done well. Inside a loop, that job becomes one step of many.

Loops own the outcome.

Agents, twins and controls stay with the system: measure, test, act within limits, trace.

The problem

Physical systems are not short of tools. They are short of loops.

Instruments stream into one system, simulations live in another and the reasoning that connects them sits in documents or in people’s heads. Every change is a handoff, and every handoff loses context.

A Scientific Loop keeps all of it in one governed cycle. Specialised agents read, plan and check; a calibrated physics twin predicts; controls act on the real system. Elidyne builds and operates the loop, and your engineers approve: nothing reaches Act without passing the limits they set.

What a loop is made of

Three parts, one loop.

Agents are the parts; the loop is what Elidyne ships. Elidyne is also the control pane around it, where every loop is watched, tested, approved and traced.

  1. 01

    Specialised agents

    Scoped agents for research, analysis, design, simulation and verification. They read the evidence, draft the plan and check each result against physics and the limits.

    Agents →
  2. 02

    Physics twins

    Calibrated twins, solvers and surrogates that forecast where the system is heading, with uncertainty, and test every change before anything real moves.

    Workbench · Compute →
  3. 03

    Controls

    Gates, standing grants and bounded writes to the real system, each with a fallback and a named approver, and a trace behind every one.

    Operations · Governance →
The loop

Six steps, every cycle.

Measure → Twin → Test → Limits → Act → Trace. The same six steps run whether the system is a reactor, a spacecraft, a fab or a lab. Only the physics changes.

  1. 01

    Measure

    Reads instruments, historians, telemetry, lab systems and literature through governed connectors, and checks each reading against the twin.

    Operations →
  2. 02

    Twin

    Keeps a calibrated physics twin of the system, forecasts where it is heading with uncertainty, and reports how far it has drifted from the plant.

    Workbench →
  3. 03

    Test

    Specialised agents propose a change and try it on the twin first, on the compute the policy allows.

    Agents →
  4. 04

    Limits

    Checks the proposal against the bounds, the approver and the autonomy level your engineers set. Anything outside them waits for a person.

    Governance →
  5. 05

    Act

    Applies the approved change to the real system through a gate or a standing grant, with a fallback if anything goes quiet.

    Operations →
  6. 06

    Trace

    Records every input, decision and approver, and saves the approved cycle as a reusable recipe and a cited report.

    Reports →
Three pillars

What makes it a Scientific Loop.

01

Physics-grounded

Physics twins and solvers do the predicting, not language models alone. Every prediction is checked against physics and against what the instruments actually measured.

02

Governed

An approval gate stands before every Act on a real system. Autonomy runs from L1 Assisted to L4 Self-improving, and your engineers set the level system by system.

03

Compounding

Every approved cycle becomes a reusable recipe, so the next loop starts from what the last one proved.

Autonomy

Set per system, changed per shift.

Elidyne builds and operates the loop; your engineers approve. Every system has an approval gate before Act, and you choose how much passes on policy and how much waits for a person.

L1

Assisted

Elidyne observes and proposes. People take every action.

L2

Supervised

Elidyne prepares each action; a named approver releases it.

L3

Governed

Actions inside the agreed bounds pass on policy; the rest wait.

L4

Self-improving

Elidyne also refines its recipes, still inside policy.

Deployment

One platform, four boundaries.

Cloud, private VPC, customer on-prem and air-gapped or classified. The loop and the control pane around it are identical in each; only the boundary changes.

ModeControlConnection
CloudElidyne-managedConnected
Private VPCElidyne + customerControlled
Customer on-premCustomerRestricted
Air-gapped / classifiedCustomerOffline
Deployment boundaries
Outcomes

What changes when the loop closes.

01

Shorter cycles

Measurement, modelling, test and decision stop waiting on each other.

02

Fewer surprises

Every change is tried on the twin before it touches the real system.

03

Defensible decisions

Each action carries its evidence, uncertainty and approver.

04

Capability that compounds

Approved cycles become recipes the whole organisation can reuse.

Start a mission

Bring us the system that matters.

Tell us about the system, the instruments and simulations around it, and where it has to run. We will map a first loop with you, from Measure to Trace, inside the limits your engineers set.