Preflight

Exactly budgeted local acquisitions before a maintained hardware run.

Usable means the verified error is inside the published threshold.

A hosted server cannot call a measure() function that lives beside your instrument. Client 0.5.0 therefore orchestrates the handshake: the endpoint returns a safe configuration, your process applies it and acquires one complete response, and the client posts that response before requesting the next configuration.

The default budget is six acquisitions and the endpoint enforces it exactly. Preflight setup is reported separately from controller cold start and does not debit the hosted runtime key. It is never hidden inside a four-to-six-acquisition controller claim.

The measured diagnostic compares response motion with caller-declared minimum resolution and measured repeatability. A registry DECLINE or no writable response can decline preflight. A responsive interface without a matching positive evidence cell remains BOUNDARY. FIT requires both a registered positive cell and a target observed inside tolerance.

Preflight does not infer target feasibility from configuration bounds alone, estimate an unknown plant from nothing, or apply a mesh-specific drift number to every substrate.

opt = SWCOptimizer(key, n=len(target), target=target, tolerance=0.05)
report = opt.preflight(measure, x0, budget=6)
x = opt.start(x0)
for _ in range(rounds):
    x = opt.step(measure(x))
proof = opt.end()