Docs/Build/Integration preflight
CLIENT 0.6.0PYTHON 3.8+

Integration preflight

The legacy name for the client-orchestrated preflight workflow.

The shipped client exposes start(), step(), and end(). There is no separate calibrate() method.

Client 0.6.0 exposes contract.preflight(measure, x0); the default budget is seven, one acquisition of which is a timed return-to-x0 read that measures drift and configures the session. Client 0.5.1 added layer.preflight(measure, x0, budget=6). The client applies the exact inversion-of-control handshake documented at /docs/preflight; the hosted endpoint never attempts to invoke your local instrument function.

Preflight setup acquisitions are counted separately from controller cold start. A boundary result is not fit. A decline must be corrected before starting the maintained session.

PYTHON
layer = StabilityContract(key, n=len(target), target=target, tolerance=0.05)
report = layer.preflight(measure, x0)
x = layer.start(x0)
for _ in range(rounds):
    x = layer.step(measure(x))
proof = layer.end()
Need the answer on your plant?

Run preflight, inspect the evidence scope, then compare the active default and your incumbent under one measured budget.

Start evaluation