Finite conformance evidence

A conformance result identifies a comparison, input population and artifact revision. It is useful precisely when those limits remain visible.

The kit’s L0 command exercises the shipped boundary corpus. Receipt-profile tests distinguish expected agreement from intentional authority-policy differences. Browser and CLI compatibility examples can expose concrete mismatches such as decimal canonicalization, but a passing string-only receipt cannot establish the full numeric contract.

For these guides, a fresh Seal demo BLOCK receipt was checked in the product, browser and kit using the matching demo key. The browser also refused changed arguments. That is a specific cross-tool example, not a new universal conformance claim.

Keep the exact inputs, source revisions, stdout/stderr, exit status and expected negative-control diagnostic with an evidence report. A nonzero exit caused by a missing file is not a successful tamper test.

Source versions identify this pass. Correspondence and current guarantees name what remains outside its evidence.

Previous: Model-to-runtime correspondence. Up: Current evidence and gaps. Next: Source versions and captured examples.