Context survives the handoff
Analysis knows what the site study established; the design knows which hazards it was checked against. Nothing is re-derived from a filename.
Elidyne is the control pane where every loop is watched, tested, approved and traced. Workbench is where engineers plan and test the work: Elidyne’s specialised agents draft a plan across study stages and try each change on the twin, you approve it and reserve the compute, and every run, version and review decision lands in one thread you can follow back to its source.
The planner for a deep-water tsunami buoy anchor: study stages chained from site basis to design basis, with gates and compute estimates on every step.
Site, hazards, capacity, installation. Each study feeds the next, and a change upstream marks what downstream has gone stale.
A named engineer accepts each basis before the next stage runs. Requests for changes are recorded, not lost in email.
Every step carries a compute estimate, so the plan is costed before anything is reserved or spent.
A revised plan is a new version with a visible diff. Try a larger caisson on a branch and keep the original for comparison.
Five steps, the same every time. Each one leaves a record the next one can build on.
Core logs, catalogues, hindcasts, drawings, certificates. Elidyne reads them and lists the inputs they do not give you, instead of quietly assuming them.
The plan names the studies, the methods and their assumptions, the gates and the compute each step needs. Change a step and Elidyne shows the diff before anything moves.
Approving a plan version reserves its compute. Runs are placed by policy and report their spend against the estimate as they go.
Each gate belongs to a named engineer. Assumptions accepted at a gate are carried forward as assumptions, so nobody mistakes them for results later.
Approved plans become reusable recipes, accepted results become the design basis, and the whole trace is ready for Reports to draft from.
Messages, plan versions, runs, drawings and review decisions sit on a single timeline. When a reviewer asks for changes, the request, the revised plan and the re-run stay linked, and the inspector shows the inputs and settings behind any result.
Analysis knows what the site study established; the design knows which hazards it was checked against. Nothing is re-derived from a filename.
Screening and simple checks run first, so high-fidelity compute is spent where it changes the decision.
Reports draw on the same record the runs already carry, so a defensible document is not a separate project.
A result without its provenance is a number. With its provenance, it is engineering.
Six products, one control pane. Workbench mainly carries Twin, Test and Limits; the rest of the loop is already connected when you need it.
Plan, test and approve the work a loop does
You are hereAn approved design becomes the twin that Operations watches in service.
Open Operations →03 · Work in ElidyneReports drafts the design basis straight from the investigation record.
Open Reports →04 · Under the hoodElidyne reads the brief, drafts each plan version and explains every diff.
Open Agents →05 · Under the hoodEach step is priced in compute units and placed by policy before you approve.
Open Compute →06 · Under the hoodGates, sign-offs and provenance are recorded while the investigation runs.
Open Governance →Measure → Twin → Test → Limits → Act → Trace. Every product serves the same six steps, in every loop.
Bring us the investigation that takes six weeks. We will show you what it looks like planned, tested on the twin, priced and gated in Workbench.