— Platform · Research to release →

From experiment to released batch — one continuous chain.

In most organisations each arrow between systems is a place someone re-types data. In Holonyx each arrow is a graph edge created at the moment the transition happens.

  1. 01Experiment
  2. 02Test request
  3. 03Recipe
  4. 04Batch record
  5. 05QC & release

01 · Experiment (research)

A result worth scaling starts as an experiment — freeform or workflow-gated.

Capture the science with structured sections and viewers, reference registry entries and inventory lots, and sign the record. When the result is ready to move, Request QC Test carries the experiment context with it.

Experiments list

02 · Test request (lab)

Testing is a request against a method — linked to the samples and the record.

Requests come from experiments, protocols or batches. Results land against a versioned result schema and are judged against specification limits as they are captured.

Test request detail

03 · Recipe (manufacturing)

A winning process becomes a versioned, governed recipe.

The same procedure — written once — runs as an experiment, a recipe or a batch record. Only approved recipes can start a batch, and a change is a new revision.

Process designer canvas

04 · Batch record (manufacturing)

The batch executes the approved recipe, with SOPs, spec checks and e-signatures.

Deviations are raised in-line, out-of-spec values create quality events, and instruments post results directly. The recipe version is frozen when the batch starts.

Batch execution

05 · QC & release (lab)

Release is a signed state on a record whose whole history is inspectable.

QC results, deviations and signatures gate release, and the Certificate of Analysis is generated from records that were never copied.

Certificate of Analysis

Trace one of your own products from first result to release.

A working session with the team that built it — your modality, your compliance regime, your instruments.