Docs/Build/Evidence envelope
CLIENT 0.5.0PYTHON 3.8+

Evidence envelope

One authority for registered fit, measured boundary, and structural decline.

The envelope registry is the authority for application profile, substrate, operating mode, component observability, timing, target type, coupling structure, hardware declaration, baseline, and named evidence cell. Preflight composes with it rather than creating a second, competing verdict system.

A numeric drift or coupling condition can drive a decision only when its units, plant family, topology, and evidence cell match the declaration. The photonic drift collapse in the manuscript is expressed in mesh radians for one simulated family and is explicitly not universal. The coupling boundary is scoped to a radius-one, row-normalized stencil.

EVIDENCE maps to preflight FIT only when the bounded diagnostic also passes. MARGINAL maps to BOUNDARY. A structural registry DECLINE remains DECLINE. The composition always takes the more conservative outcome.

Unknown information is not a technical decline. Missing structure, an unmatched hardware declaration, or a topology outside the registry returns BOUNDARY with the exact missing or extrapolated fields.

A fair pilot compares the active default and the best credible incumbent on the same physical trajectory, acquisition budget, target, bounds, and stopping rule. Counterfactual shadow candidates do not count as a measured race.

PYTHON
opt = SWCOptimizer(key, n=len(x0), mode="regulation", target=target)
x = opt.start(x0)
for _ in range(rounds):
    x = opt.step(measure(x), target=target)
proof = opt.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