Platform/Work in Elidyne/Reports

Reports that cite their sources.

Every loop keeps a trace of what it measured, tested, approved and did. Reports turns that trace into design-basis, event and shift reports: every value links back to the run and the input that produced it, and anything still open is listed as a limitation that cannot be quietly removed.

app.elidyne.ai / buoy-a3 / reports / design-basisOpen full screen ↗
Loading the workspace…

The report composer drafting a design-basis report for the buoy anchor, with an event addendum after an earthquake. Every figure is cited to the run behind it.

  1. 01

    Choose the scope

    The whole investigation, or chosen runs and gates. The outline follows your organisation’s template.

  2. 02

    Every value cited

    Numbers in the text link to the run, the plan version and the input behind them.

  3. 03

    Open items stay visible

    An assumption or unresolved finding is carried into the report as a limitation, not dropped.

  4. 04

    Released through a gate

    A draft stays a draft until a named engineer releases it. Addenda keep the version history.

How it works

Drafted from the record, not a blank page.

The evidence already exists in the investigation. Reports assembles it, cites it and keeps it honest.

Step 01

Start from the record.

Pick the investigation, the runs and the gates to cover. Reports pins the records it draws on, so the draft cannot drift from them.

Scope · Investigation 1
Runs
1–6 · 38 records pinned
Gates
G1–G4 accepted
Template
Design-basis report
Open items
1 assumption · listed
Status
Draft · not released
Step 02

Every number carries its source.

Elidyne drafts the prose and checks that each claim has a source before it is shown. Assumptions are labelled as assumptions wherever they appear.

Cited values
  • Factor of safety2.75 after Mw 9 · Run 5
  • Penetration7.95 m · deployment log
  • Turbidity velocity2.5 m/s · assumption
  • ReleaseAwaiting sign-off
Step 03

Keep reports current as the system lives on.

When something happens in service, an event addendum is drafted from the operations log and the twin re-run, on top of the released design basis.

Report history
v1 · ReleasedDesign basisRuns 1–6
EventEarthquake recordedTwin re-run
v2 · DraftEvent addendumAwaiting release
What it drafts

Five reports engineers actually write.

Each one follows your organisation’s template, and each one is drafted from the same record.

01

Design basis

The accepted inputs, methods and results a design rests on, gate by gate.

02

Verification and qualification

Evidence against each requirement, with the tests and runs that satisfy it.

03

Event report

What happened in service, what the twin showed and what was done about it.

04

Shift report

Signals, incidents and control changes over one shift, drafted from the log.

05

Review pack

What a review board needs: results, open questions and the decisions asked of it.

Why reviewers prefer it

Honest about what is not yet known.

01

No copy and paste

Figures and tables are generated from stored results, so they match the runs exactly.

02

Limitations cannot vanish

Removing an open item needs a recorded decision, so the report says what is not yet known.

03

Reviewers get answers attached

Any value can be expanded back to its run, its inputs and the person who accepted it.

If a number cannot be walked back to its source, it does not belong in the report.
Reports is built for the reviewer, the auditor and the regulator who ask where a value came from.
Start a mission

Bring us the system that matters.

Send us the report your reviewers always send back. We will show what it looks like drafted from the record.