LABFLOW / SYSTEMS ONLINESESSION ID · LF-23421-U8-FWD·3 INSTRUMENTS CONNECTED·BENCH · BAY 04·v4.2.1
SECTION · LF-PROTO
DSL · TYPED
CTRL · SCPI / VISA / IVI
SIGNED · SHA-256
04 / PROTOCOLS

Plain English in. Calibrated measurements out.

A Labflow protocol is the contract between you, the agent and the bench. Authored in natural language, compiled into a typed instrument graph, validated against your safety policy, and signed for replay.

PIPELINE

From brief to bytes.

STAGE / 01

Brief

Describe the experiment the way you would to a grad student. Constraints, sweeps, dwell, abort conditions — natural language is enough.

EXAMPLE
"Sweep VGS from 0 to 3.2 V on K2400.CH1, settle 50 ms, log Id, stop if Id > 10 mA."
STAGE / 02

Compile

Labflow lifts the brief into a typed protocol — an instrument graph, with explicit channels, units, settle times and abort predicates.

EXAMPLE
protocol pmos_transfer { sweep(K2400.CH1, V, 0, 3.2, 204, dwell=50ms) capture(Id) abort(Id > 10mA) }
STAGE / 03

Validate

The protocol is checked against the bench safety file. Compliance ceilings, ramp limits, dwell minimums and probe-temperature gates are evaluated before any output is enabled.

EXAMPLE
✓ within K2400.CH1 compliance · ✓ ramp < 100 V/s · ⚠ requires operator-confirm @ VGS > 3.0
STAGE / 04

Arm & run

The bench runs in lock-step. The agent watches the waveform, the operator watches the agent, and any policy breach pauses the run for a signature.

EXAMPLE
k2400.ch1 → 0..3.2V, n=204, compliance=100mA · scope.trig=rising@1.65V
STAGE / 05

Replay

Every protocol carries a signed manifest. Same protocol + same manifest = identical SCPI, identical setpoints, identical compliance — three years from now.

EXAMPLE
lf replay LF-REP-4821 → matched bytes-for-bytes (SHA-256 9f2a…b4c1)
LIBRARY

Pre-flight protocols.

Battle-tested protocols shipped with Labflow. Fork one, tune it for your DUT, and check it back in — the agent honors your version.

SMU

Transfer curve

Vth, SS, Ion, Ioff, Ion/Ioff. Parametric pass/fail with outlier flagging.

SMU

Output characteristic

Id(Vds) at stepped Vgs. Saturates the family on one chart.

PSU + SCOPE

PSRR sweep

Frequency-domain rejection, dB and linear views, with annotation at unity-gain crossover.

FG + SCOPE

Step response

Edge speed, overshoot, settling, ringing. Auto-fits rise / fall with R².

PSU + DMM

Burn-in 24h

Datalogged temperature, drift, current creep. Auto-resumes after lost-link.

SCOPE

Jitter histogram

TIE, period, cycle-cycle. p99 / p99.9 callouts with eye overlay.

DMM

4W resistance map

Pad-by-pad 4-wire characterization on a contact array.

DAQ

Climate run

Multi-channel temp / RH log with event annotations from the chamber controller.

SAFETY POLICY

The policy file is the floor.

Every protocol inherits from a per-bench policy file. The agent literally cannot ask for more than the policy allows.

Per-channel ceilings

V, I, ramp-rate, dwell. Defined once per bench, inherited by every protocol.

Operator-confirm gates

Any setpoint above the policy threshold pauses for a signature.

Auto-shutdown predicates

Compliance hit, probe-temp breach, runaway current — clean ramp-down without waiting for a human.

Signed manifests

Every run hashes its protocol + setpoints + driver versions. Replay is provable.

Author a protocol with the agent.

FLOW will draft the typed protocol with you, line by line, and walk through every safety hook before you check it in.

Read the schema.

The full protocol DSL — fields, units, predicates, abort conditions, manifest hashing — lives in the docs.