← Back to catalogue
TODO

Experiment Run

vr.wm-act-022 · wm-act-022-experiment-run

Governed experiment execution with frozen manifest attempt lineage and append-only deviations

World Models Activities and processes ACT.EXP
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

3 bundles · 4 layers · 5 findings · 11 questions

Run definition What the run was supposed to do before it started.

Frozen manifest

The design, parameters and materials fixed for this run.

Manifest identity

The manifest version the run executes and the experiment it belongs to.

  1. Which experiment and which manifest version does this run execute?
  2. Was the manifest frozen before the run started, and by whom?

Planned conditions

Parameters, materials and procedures the run is meant to use.

  1. Which parameters, materials and procedure versions does the manifest fix for this run?
  2. Which approval or ethics clearance covers this run, if one is required?
Execution and lineage What actually happened during the attempt.

Attempt

The concrete execution with its own identifier and relation to earlier attempts.

Attempt lineage

How this attempt relates to earlier attempts of the same manifest.

  1. Is this a first attempt, a repeat or a replacement of an earlier attempt?
  2. Who executed the run, on which equipment or compute, and when did it start and end?

Deviation log

Append-only record of departures from the manifest.

Recorded deviations

Each departure from the manifest with time, cause and impact.

  1. Which deviations from the manifest were recorded during this run?
  2. Was any deviation edited or removed after it was recorded?
  3. Does any deviation invalidate the run for its intended analysis?
Outcome How the run ended and what it produced.

Result status

The final status of the run and its outputs.

Run outcome

Completion status and links to produced data.

  1. Did the run complete, fail or get aborted, and for what reason?
  2. Which datasets, samples or artefacts did this run produce?

Classifiers Filled

Family
World Models
Category
Activities and processes
Entry kind
standalone-mm
Navigation path
NAV.ACT.EXP
Domain
ACT.EXP
Industry
Cross-industry
Tags
experimentrunact.exptrial
Also called
Experiment, Trial

What it is Filled

An experiment run is one governed execution of an experiment: a single attempt carried out against a manifest of design, materials, parameters and procedures that was frozen before it started. Its record holds the attempt lineage and an append-only list of deviations; the experiment design itself and the resulting datasets are separate things.

Why it exists Filled

Governed experiment execution with frozen manifest attempt lineage and append-only deviations

Distinguishing features Filled

  • One run is one attempt; the experiment design and its manifest are separate records the run points to.
  • The manifest is frozen before execution, so any change during the run is a recorded deviation, not an edit.
  • Repeats keep their own identity and link to earlier attempts instead of overwriting them.
  • Distinct from the dataset it produces and from the analysis that interprets it.

What robots and AI may and may not do Filled

Must not

  • Edit a frozen manifest after the run has started.
  • Remove, rewrite or back-date a recorded deviation.
  • Report a failed or aborted attempt as completed, or hide it from the lineage.
  • Start a run that requires ethics or safety approval before that approval is recorded.
  • Select attempts for reporting only because their results were favourable.

Only with a human decision

  • Approving a manifest and freezing it for execution.
  • Deciding whether a deviation invalidates a run.
  • Abandoning a run that involves participants or animals.

May

  • Register a run against a frozen manifest and record its start, end and executor.
  • Append deviations with time, cause and observed impact.
  • Link the datasets and samples a run produced to its record.
  • Report runs whose outputs are not traceable to a manifest version.

Moral aspects Filled

  • Selective reporting of successful attempts distorts science and can harm those who rely on it.
  • Experiments involving people or animals depend on valid approval and consent for each run.
  • Honest deviation records protect the credibility of everyone who uses the results.

Who is affected

  • Research participants and animal subjects
  • Researchers and laboratory staff
  • Users of the results, including reviewers and regulators

Owners Filled

Steward

The principal investigator or study lead who answers for the experiment and its runs.

Master systems

  • Electronic laboratory notebook
  • Laboratory information management system
  • Experiment tracking system

Links to other meta-models Filled

parent

  • WM-ACT-036

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A run is identified by a run identifier issued by the laboratory or tracking system, scoped to its experiment.
  • The run record cites the manifest version and, where present, a registered study or protocol identifier.

Direct properties not applicable Not applicable

Not applicable

A run is an activity; the physical conditions and measurements it captures belong to the observation and dataset records it produces.

Recognition optional Filled

  • A run record names one manifest version, an executor, a start time and a status.
  • Often confused with the experiment design, with a protocol or with the dataset of results.

Capabilities and actions required Filled

  • Runs can be repeated against the same manifest while keeping each attempt's identity.
  • Deviations can be appended and reviewed without altering the manifest.
  • Outputs can be traced back to the run, manifest version and executor.

Hazards and failure modes required Filled

  • Silent changes to a manifest make results impossible to reproduce or audit.
  • Hidden failed attempts bias the evidence base.
  • Runs started without required approval expose participants to unapproved risk.

Standards and interfaces required Filled

  • W3C PROV-O for the provenance of runs and their outputs.
  • Electronic laboratory notebook and tracking system records.
  • Clinical trial registries where the run belongs to a registered trial.

Context of use required Filled

  • Used in laboratory science, clinical research, engineering tests and machine learning experiments.
  • Good laboratory practice and good clinical practice rules apply in regulated settings.

Sources Filled

  1. PROV-O: The PROV Ontology, W3C Recommendation
  2. OECD Principles of Good Laboratory Practice, OECD
  3. ICH E6 Guideline for Good Clinical Practice, International Council for Harmonisation

Open questions

  • Planned model: boundary questions, research and every section remain to be written.

Machine files

Card as JSON Specification AGENTS.md Card backlog vercy.card/1

Provenance

planned (registry candidate) · todo

Built from: models/runtime-index.json, ver-cy/world-models/card-supplements/wm-act-022-experiment-run.json

Planned entry, hidden from the catalogue until researched.