Crate scientific_workflow 

Rust primitives for reproducible scientific workflows.

scientific-workflow provides the data and execution foundations needed to describe scientific systems, record their evolution, and organize scoped computational work. The crate is intentionally divided by responsibility: state representation, state time series, dispatch, persistence, and language bridges remain separate modules rather than accumulating behind one monolithic interface.

Current module

The first implemented module is system_state. It provides:

• JSON-defined, immutable field layouts;
• heterogeneous concrete Rust payloads behind a typed API;
• clone-free payload insertion, mutation, and extraction;
• explicit deep cloning of complete states;
• deterministic time-point metadata.

Type erasure and boxing remain internal to that module. Downstream crates work with their original concrete payload types.

Basic use

use scientific_workflow::system_state::{StateSpec, TimePoint};

let spec = StateSpec::load("state.json")?;
let mut state = spec.empty(TimePoint::new(0));

state.set("population", vec![10_u64, 20, 30])?;
state
    .get_mut::<Vec<u64>>("population")?
    .push(40);
let population = state.take::<Vec<u64>>("population")?;

assert_eq!(population, vec![10, 20, 30, 40]);

Future SSTS and dispatcher modules will build on the same ownership and module-boundary principles without changing the public state-value contract.

Modules

system_state

Template-defined, heterogeneous scientific system states.