MODULE 02 · Infrastructure

Lab in a box

Start with a software-controlled simulation of a single low-risk research workflow, then work with a lab to validate one hardware interface at a time.

THE FIRST USEFUL PRODUCT

Start with a bounded problem.

Who it is for
Teaching labs, independent researchers and labs that need repeatable workflows.
First product
A reference lab bill of materials and a simulator that records the steps and outputs of one workflow.
Next decision
The task, exclusions and operator responsibilities are documented and reviewed.
Product boundary

A research infrastructure project. Equipment qualification and trained supervision are separate from software completion; this is not a home medicine-manufacturing kit.

PRODUCT 0 → 1.0

The Phase 0–5 strategy.

Each phase has a concrete deliverable and an acceptance gate. These are proposed development plans, not completed scientific or product validations.

PHASE 0 / 0% MILESTONECurrent planning

Choose one lab workflow

Define a task small enough to reproduce reliably.

Work to do

  • Map the operator steps and required measurements.
  • Separate simulation from physical execution.
  • Ask a lab partner to review hazards and measurement requirements.

Acceptance gate

The task, exclusions and operator responsibilities are documented and reviewed.

Publish: Workflow brief and initial equipment inventory.

PHASE 1 / 20% MILESTONEPlanned

Specify the interfaces

Describe how instruments and software exchange information.

Work to do

  • Publish the bill of materials and compatible interface requirements.
  • Define calibration, measurement and run-record schemas.
  • Build mock instrument adapters with deterministic responses.

Acceptance gate

A complete simulated run can be represented without untracked manual steps.

Publish: Interface contracts, bill of materials and simulator fixtures.

PHASE 2 / 40% MILESTONEPlanned

Build the simulator

Let users understand and replay the workflow before hardware integration.

Work to do

  • Build a visual sequence and run timeline.
  • Record inputs, errors and outputs for each simulated step.
  • Support replay and export of a complete run.

Acceptance gate

The same fixture produces the same recorded outputs; injected failures are visible.

Publish: Lab simulator prototype and example run.

PHASE 3 / 60% MILESTONEPlanned

Validate one instrument

Compare recorded measurements with an accepted reference.

Work to do

  • Integrate one instrument in a supervised partner lab.
  • Record calibration and measurement uncertainty.
  • Test disconnects, out-of-range values and operator intervention.

Acceptance gate

The lab signs off the measurement and failure-handling criteria for the defined use.

Publish: Instrument validation report and reviewed adapter.

PHASE 4 / 80% MILESTONEPlanned

Replicate with a partner

Check whether another operator can reproduce the workflow.

Work to do

  • Run the documented workflow with a second operator.
  • Compare measurement consistency and setup effort.
  • Resolve ambiguous instructions and record deviations.

Acceptance gate

A second operator meets the predefined repeatability target with the published instructions.

Publish: Replication report and revised setup guide.

PHASE 5 / 100% MILESTONEPlanned

Release the research kit

Package a maintainable reference system.

Work to do

  • Publish supported hardware and software versions.
  • Provide installation, calibration and troubleshooting guides.
  • Separate experimental adapters from supported releases.

Acceptance gate

Supported configurations pass acceptance checks; scope and maintenance ownership are explicit.

Publish: Product 1.0 reference kit and console.

Progress stays at 0% until the starting scope is accepted and subsequent milestone evidence is published. Phase 1–5 targets are 20%, 40%, 60%, 80% and 100%. These percentages track development, not treatment effectiveness.

WHAT THIS DEPENDS ON

Build with the right foundations.

  • Manufacturing module: transparent equipment cost assumptions.
  • Datasets & models library: protocol versions and reference outputs.
  • Lab partner: equipment access, calibration and safety review.

Partner roles above are requirements. No partner participation or endorsement is claimed.

FUTURE INTERACTIVE PRODUCT

Lab workflow console

Simulation first. Hardware control remains unavailable until partner review and instrument tests pass.

  1. Select a reference workflow.
  2. Simulate its steps and resource requirements.
  3. Review instrument readiness with a lab operator.
  4. Record an approved run and export its audit trail.
View the portal specification
PUBLIC CHANGELOG

What changed. What is still planned.

Lab in a box

Phase 0–5 strategy and portal plan published

Published the module strategy, concrete phase deliverables, acceptance criteria and future portal workflow. This is a planning update; product completion remains 0%.

Entries are published with site updates. Planned work is labelled separately from completed product milestones.