Platform/Under the hood/Agents

Specialised agents that show their working.

Elidyne is the set of specialised agents inside every Elidyne loop. They read the brief and the evidence, draft plans and proposals, check results against physics and the limits you set, and write up what happened. Each agent has a scoped role inside a governed loop, and nothing runs that you have not approved.

From brief to planPlan under review
The brief in, a plan out. The objective and its limits travel with every step; gates sit only where a decision is consequential.
What Elidyne does

Four jobs, one loop.

Elidyne’s agents read, plan, check and draft against the same context, so a change at the top of an investigation is felt everywhere below it. They are the parts; the governed loop is what decides.

  1. 01

    Reads

    Files, data and earlier investigations, and lists the inputs they do not give you.

  2. 02

    Plans

    Study stages, methods, gates and cost, as a plan you can edit and approve.

  3. 03

    Checks

    Results against physics, acceptance criteria and the bounds of every grant.

  4. 04

    Drafts

    Proposals, diffs, alerts and reports, with a source behind every claim.

Move 01

State the objective once. Constraints travel with it.

The brief captures the target, the operating limits, the models and data it applies to, and the standards it has to meet. Everything downstream stays bound to it instead of being re-explained in each tool.

Brief · draft
Objective
Raise thermal margin ≥ 8 K
Hard limit
Mass increase ≤ 2%
Standards
Internal DR-4 · design rules v7
Context
3 CAD variants · 12 earlier runs
Owner
Thermal systems
  • Objectives, hard limits and acceptance criteria held as structured context
  • Drawings, meshes, test data and earlier investigations attached at source
  • Change a constraint and every dependent step is flagged for replanning
Move 02

A plan you can argue with before compute is spent.

Planning produces a readable artefact: stages, methods, assumptions, expected evidence and the gates where a person has to say yes. Engineers review the reasoning while it is still cheap to change.

Plan · 16 steps · 3 gates
BriefThermal marginObjective accepted
Plan16-step study3 approval gates
Run24 candidatesPlaced by policy
  • Methods stated with their assumptions and known limitations
  • Cost and duration estimated per stage before anything is submitted
  • Gates placed where the decision is consequential, not everywhere
Move 03

Specialised agents, composed for the problem.

Elidyne selects the agents, solvers and checks a stage actually needs, then holds them to the same context and the same authority. No agent runs outside the plan it belongs to.

Composition for one study
  • Research, analysis, design, simulation and verification as scoped agents
  • Tools and solvers bound at run time from what the project may use
  • Every action attributed, logged and traced to the step that asked for it
Where you meet Elidyne

Elidyne works in the thread.

In a Workbench thread, Elidyne reads what was attached, lists what it would otherwise have to assume and drafts each new plan version with its diff. When an input changes, it flags the results that have gone stale and proposes the re-run.

app.elidyne.ai / buoy-a3 / workbench / threadOpen full screen ↗
Loading the workspace…
  • Missing inputs listed up front, never silently assumed
  • Every plan version shown as a diff before it is approved
  • Stale results traced to the input that changed
  • Nothing runs until a person approves it
Why it earns trust

Agents you can check.

01

Plans are artefacts, not black boxes

The plan is reviewable, editable and versioned. Disagree with the method and you change the plan, not the prompt.

02

Context and authority travel together

Each step receives the objective, the constraints, the data and an explicit limit on what it may do without approval.

03

Replanning stays cheap

A changed requirement re-plans the affected branch instead of restarting the investigation.

An agent that cannot show its plan is not an engineering tool. It is a guess with better grammar.
Elidyne treats the plan as its main output. Execution follows agreement, and the loop, not the agent, decides what may happen next.
How it connects

Agents and the other five.

Six products, one control pane. Agents mainly carries Test 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 us an objective that keeps stalling. We will show the plan Elidyne drafts, and where it stops to ask.