JSON acceptance implies output-query safety #
crown_query_v1 describes an exact rational dense/ReLU network, an input box, proposed ReLU
α values, and affine output inequalities. The checker recomputes affine bounds using existing
CROWN transfers. Parameters use integer or fraction strings; numeric JSON literals are rejected.
The theorem concerns the real TorchLean model and query decoded from these bytes. It does not identify this model with an ONNX file or a floating-point deployment. This is a separate format from the binary32 node-replay transcript; β dual variables, cuts, and branch trees are unsupported.
Decode and check a query document; malformed documents are rejected.
Instances For
Parse and check a query document given as text. This is the CLI verdict.
Instances For
Text acceptance implies the universal real output property, without a producer axiom.
Why acceptsText rejected a document, for error messages. The verdict is acceptsText.