Home Developers Evidence engineering.msa.hysteresis

Public evidence

engineering.msa.hysteresis

Machine-checked verification for calculation version 1.0.0 · tier engine_tested

Verification

8/8 calculation tests · Production surface contract 4/4

  • Golden tests 0 / 0
  • Boundary tests 5 / 5
  • Property tests 3 / 3
  • Production surface contract 4 / 4
  • }
  • Engine tested Yes
  • Source checked Yes
  • Artifact integrity PASS
  • Production attestation Embedded snapshot: unpublished · Build schema 1.0.0 ready · Semantic contract ✓ · Attestation report not published on origin · Live production status STALE (1 capability; 156 remain CURRENT) @ 2026-09-14T03:54:53.650Z
  • Semantic contract PASS
  • Evidence attested at 2026-09-14T00:43:05.498Z
  • Last production check 2026-09-14T00:43:05.498Z
  • Public / cache
  • Origin
  • Supplemental domain review Not performed
  • Named expert review Not performed
  • release artifacts aligned PASS
  • schema valid input executes PASS
  • engine success output validates schema PASS
  • schema rejects incomplete input PASS

Fingerprint sha256:b634e7051166eaf150ddc82867a3f461e27e01d7d0fb4dfb6d48767da5846b54

Input schema sha256:629ef1b645a802b27d191bd3564c170f1221795f8acd7fa679ce17955ece99c2 · Output schema sha256:7d72b54ae4ea5c131ff694ba735e95c04a149f46d54e6e5351274e5a14ffeba8 · Build-time SHA-256 digests prove published artifacts agree with each other (release_integrity.scope=workspace). Production attestation GETs canonical URLs twice (public/cached view and origin), including Capability HTML, via npm run attest:production --write (published at /.well-known/calculatorx-production-attestation.json) and fails if the public Capability page advertises a different calculation_version. This is artifact consistency, not an independent immutable release log.

Build & scope

Engine identity and declared limitations.

Tool
hysteresis
Engine
hysteresis
Engine build
2026-09-15
Evidence core
2026-09-15T22:49:35.937Z
Rendered
2026-09-15T23:38:12.912Z
Last reviewed

Assumptions

  • VIM 4.17 hysteresis as max |y_up − y_down| at index-paired stations
  • n≥2; pairing is by index, not interpolated vs xref
  • Not OLS linearity, not a %Hysteresis verdict, and not AIAG GRR

Limitations

  • Maximum paired |y_up − y_down| — not a %Hysteresis / process-variation verdict
  • Not OLS of ε versus xref (Linearity) and not a single-shot measurement error
  • Does not take T and does not issue pass/fail
  • n≥2 index-paired points; not AIAG GRR

Sources

Standards and references supporting this tool specification. Methods are listed separately — they are algorithms, not bibliographic sources.

Published checks

Golden, boundary, and property cases included in this evidence build.

IDKindStatusDetail
boundary-hystboundarypassExpected n=3 · hysteresis=1 · Actual n=3 · hysteresis=1 · mean_abs=0.3333333333333333
boundary-hyst-zeroboundarypassExpected n=3 · hysteresis=0 · Actual n=3 · hysteresis=0 · mean_abs=0
boundary-hyst-n1boundarypassExpected VALUE_OUT_OF_RANGE · Actual VALUE_OUT_OF_RANGE
boundary-hyst-lenboundarypassExpected INVALID_INPUT · Actual INVALID_INPUT
boundary-hyst-missingboundarypassExpected MISSING_REQUIRED_INPUT · Actual MISSING_REQUIRED_INPUT
property-hystpropertypass1
property-hyst-zeropropertypass0
property-hyst-aliaspropertypass1