UnifiedFlowInfrastructure for Evidence

Platform / Provenance & continuity

A result you canreturn to.

Trace a result through its source data, processing parameters, and review history. Give your team the records to investigate an output, compare revisions, or continue another researcher’s work.

Discuss your workflowExplore the supporting record
One result, connected to the work behind itAn analysis output is linked to source data, method settings, researcher decisions, and version history, showing the records a team can use to investigate a result or compare revisions.Data & setupRecording + acquisitionMethods & settingsRetained configurationResearcher reviewDecision + reasonAnalysis outputThe connected recordSourceMethodReviewVersion historyEarlier → current

Inside the supporting record

Follow one result
back through the work.

Trace an output through its data lineage: the source files, method version, execution history, and scientific review behind it.

01 / The result

Start with something worth returning to.

Start with an analysis output, then trace the inputs, processing steps, and review decisions that produced it. Those links give your team a way to investigate or explain the result.

An output with a supporting record

Inspect this record
Output
Activity summary · Recording A
Artifact
Scientific output linked to a processing run
View
Activity output connected to its source and processing history
The output is the starting point.Activity outputRecording AActivitySource-linked artifact
A scientific artifact connects the file to the work that produced it.

02 / The execution

See how the work reached this point.

Follow the output to its processing run. Stage and attempt records help an operator understand progress, interruptions and the execution that produced the output.

The history stays with the work

Inspect this record
Run
Recording A · processing run
Attempt 1
Interrupted during extraction
Attempt 2
Completed after the environment issue was resolved
The output connects to its execution history.Activity outputproduced byProcessing runPrepareExtractOutputs01 · Interrupted02 · Completed
An interrupted attempt and a completed attempt remain distinct records.

03 / The actual settings

Return to what this run used.

A reusable preset can change. The resolved settings and retained configuration explain this execution, even when the team prepares a different configuration for later work.

A specific configuration for a specific run

Inspect this record
Method
Cellular activity · version 3
This run
Configuration A · retained with the run
Later work
Preset adjusted to configuration B
Later changes do not explain an earlier run.Activity outputused these settingsActual run settingsCellular activity · v3A · Retained for this runB · Preset for later workRun configurationA · Retained for this run
Read the configuration retained by this run; a current preset alone is not its history.

04 / The source

Reconnect the output to the experiment.

Follow the declared inputs to the recording, its storage reference, and acquisition metadata. Check the instrument setup and collection settings when assessing how the data was produced.

Trace derived outputs back to the original recording and acquisition settings.

Inspect this record
Input
Recording A · native file reference
Collection
Imaging rig A · acquisition profile revision 2
Storage
Institution-controlled research storage
Source files retain their acquisition record.Activity outputderived fromSource & acquisitionRecording A · native inputImaging rig AAcquisition profile · rev 2Institution-controlled storage
The input reference identifies the material; the acquisition record describes how it was collected.

05 / The review

Carry the reasoning into the next handover.

Return to the outputs and snapshot the scientific team examined. Keep acceptance decisions, exclusions, and their rationale available so the next researcher can understand what was reviewed.

A starting point for the next person

Inspect this record
Review bundle
Selected outputs, source references, and run settings
Snapshot
State assembled for the review
Decision
Scientific review outcome and notes
The result and its review belong together.Activity outputreviewed inReview & handoverReview bundleSnapshotDecision + notesThe basis for review stays attached.
Scientific acceptance is a lab decision for a defined use, separate from completed processing.
Keep the work usable over time.

From a connected record to continuing use

Keep the work
usable over time.

Agree what is retained, who looks after it and what another researcher would need to run the work again.

Preserve the record

Keep run parameters, input and output references, execution attempts, and review decisions. Establish how platform records are retained and supported within the deployment.

Look after the files

The institution manages retention and backup of source materials and scientific outputs. References help locate the files; recovery depends on the storage and backup arrangements.

Prepare to run again

Retain the needed inputs, method versions, and software dependencies. Check the environment and evaluate changes with the lab before relying on a new execution.

Plan the operating environment How we evaluate workflow changes

A conversation, grounded in your work

What would your next researcher need?

Let’s identify the records, files and operating knowledge your lab needs to carry forward.

Discuss your workflow