Skip to content

SDLX Technical Documentation

SDLX connects autonomous scientific planning, deterministic workflow execution, laboratory gateways, simulated and physical devices, operator-assisted tasks, and evidence-aware experiment loops. This site is the maintained entry point for system boundaries, contracts, operations, and delivery status.

Live system statusUpdated waiting for first update · refreshes every 15 seconds
devices online / registered
devices intentionally disabled
control services healthy
active operations and human tasks

System Flow

Each module owns a different source of truth. ASCEND coordinates hypotheses, campaigns, and decisions; Composer builds reviewed packages; PACE owns loop runs and result bundles; LabFlow owns workflow execution; LabBridge owns device, operation, artifact, spatial, and Human Task state.

What SDLX Already Demonstrates

Agentic experiment lifecycleASCEND turns scientific intent into iterative campaigns, delegates composition, evaluates evidence, and proposes bounded next rounds.
Hardware-neutral executionPhysical and simulated controllers implement the same semantic capability contract, so workflows do not contain simulation branches.
Human work as a durable operationManual preparation and data upload use schema-bound Human Tasks with revisions, artifacts, rejection, resubmission, and automatic continuation.
Spatially aware roboticsStations, service ports, leases, routes, carrier custody, and reviewed robot modes connect instruments without hard-coding raw poses into agent plans.
Evidence-native resultsDevice controllers return semantic parameters or object-store URIs; PACE assembles traceable Result Bundles for scientific decisions.
Recovery as a contractThe live integration suite force-stops nine service processes and verifies persisted device, workflow, loop, and campaign records after restart.

Validated Scope

31maintainable simulated instrument and robot profiles
2end-to-end scientific exemplars: powder/XRD and ORR RDE LSV
135 + 16LabBridge tests and subtests in the current verification baseline
5separated authority modules with explicit API boundaries

Read by Task

Production Boundary

The deterministic software loop and simulated device fleet are implemented. Production work is concentrated on identity-provider integration, physical controller adapters, calibrated spatial mappings, and safe recovery of interrupted robot transfers.

SDLX technical documentation