Skip to main content

Scientific pipeline with AI interpretation

Keep deterministic science and AI-assisted interpretation independently reproducible.

Scientific pipeline with AI interpretation

Activity responsibilities

ActivityResponsibility
prepare-experimentExecute the prepare experiment stage and publish its declared outputs for downstream activities.
run-simulationExecute the run simulation stage and publish its declared outputs for downstream activities.
extract-measurementsExecute the extract measurements stage and publish its declared outputs for downstream activities.
statistical-analysisExecute the statistical analysis stage and publish its declared outputs for downstream activities.
ai-interpretationExecute the AI interpretation stage and publish its declared outputs for downstream activities.
validate-conclusionsExecute the validate conclusions stage and publish its declared outputs for downstream activities.
publish-reportExecute the publish report stage and publish its declared outputs for downstream activities.

Inputs

  • Experiment definition
  • Domain software
  • Interpretation model

Outputs

  • Simulation data
  • Analyses
  • Validated report

Provenance to preserve

  • Parameters and software
  • Raw data
  • Prompt and validation

Runnable example

This is the complete checked-in bundle for this pattern. Download the environment, scope, topology, workflow, input, container recipe, runner, and validation contract from this page before executing it.

Verified local execution

These captures and the output manifest were produced by the fixture's local Docker run and validator. They are published with the same bundle as the runnable files.

Scientific pipeline with AI interpretation workflow execution evidence
Workflow evidence
Scientific pipeline with AI interpretation execution evidence
Execution evidence
Scientific pipeline with AI interpretation output evidence
Output evidence
Open verified output manifest ↓

Execution considerations

Separate scientific computation from interpretation so reviewers can reproduce the results without the AI model.

AkôFlow boundary: the engine schedules, deploys, executes, transfers data, and records evidence. The ML or agent framework remains an implementation choice inside each activity.