01 · DescribeThe request, in ordinary language.Rate, belt, stations, buffers, fleets, faults and acceptance tests, in any order. Anything under-specified comes back as a question.compose
02 · Review and approveThe scenario, exactly as it will run.Layout, I/O map, timing, acceptance tests and applied defaults, laid out for review. A person approves it; any change comes back for approval.review · scenario · approval
03 · Run and compareYour controller logic in the loop; the record signed.Scheduled faults fire; results are checked against acceptance bounds; the run is recorded and signed. Approved scenarios compare like-for-like.evidence · commissioning checks