Public evidence

math.scientific_notation

Machine-checked verification for calculation version 2.0.1 · tier engine_tested

Open calculator API Capability Download JSON CVP Manifest MCP Review policy

CVP status

Declared CVP coverage is all four published modes (convert, normalize, engineering, operate) plus invalid-domain. Page published examples and IUT engine automated checks are separate suites.

Declared partition coverage: PASS · 5/5 declared partitions (convert, normalize, engineering, operate, invalid-domain)
Versions: Calculation 2.0.1 · CVP protocol 1.0.0-proposed · Evidence 2026-10-21.scientific-complete-contract-v2
Verification revision: 2026-10-21.scientific-complete-contract-v2 · 5/5 property · digest f1914212ac19

Verification

Legacy regression suite: 9/9 calculation tests · Production surface contract 6/6

Three distinct suites: educational examples on the calculator page, this legacy regression count (9/9 golden + boundary), and the CVP verification suite below. They are not the same number. Property, metamorphic, round-trip, O3, and interface statuses/checks are recorded in the CVP Manifest . SKIP (0/0) means that suite has no published vectors.

This calculator CURRENT · Public schema 2.0.1 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

CVP verification suite

Protocol checks from the Evidence Manifest. Distinct from the legacy regression suite above. Verification revision 2026-10-21.scientific-complete-contract-v2. Calculation version 2.0.1. CVP 1.0.0-proposed. 202/202 golden · 4/4 CVP boundary · 8/8 invalid · 5/5 property · 2/2 metamorphic · 2/2 round-trip · 4/4 cross-interface · 6/6 CVP contract. digest f1914212ac19. Convert / normalize / engineering: ≤2 ULP on scientific coefficient, exact exponent. Operate: ≤2 ULP on reconstructed binary64 plus exact normalized exponent. Invalid domain: matching error codes (overflow / underflow / division by zero / missing). Not a whole-domain guarantee beyond recorded vectors.

Golden (oracle-backed) 202 / 202
CVP boundary 4 / 4
Invalid input 8 / 8
Property 5 / 5
Metamorphic 2 / 2
Round-trip 2 / 2
Cross-interface 4 / 4
CVP contract 6 / 6
Interfaces PASS · UI (SSR) / REST / MCP
Interface claim ui-ssr is query-result HTML, not a live browser session.
Verified scope all published modes
Assurance Core

release artifacts aligned PASS
schema output required declared PASS
schema valid input executes PASS
engine success output validates schema PASS
schema rejects incomplete input PASS
rest success payload validates schema PASS

Fingerprint sha256:18ec84e2612d3f9fcba0e9b4508b97d3ac41997c24d0605abaeb38abc1d3a900

Input schema sha256:4756bfd7d99f3e794b01565b1a471e36291ed736a53492e8510ea70bd8afe8d7 · Output schema sha256:aa2cb423283955ce4ae093b9eaa7fa8f69d4d5137340ab83fe5392d68026733e · 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: scientific-notation
Engine: scientific-notation
Engine build: 2026-10-21
Evidence core: 2026-10-21T06:25:13.024Z
Rendered: 2026-10-22T08:54:35.135Z
Last reviewed: —

Assumptions

Finite IEEE-754 binary64 values. Inputs outside the supported floating-point range are rejected or reported as overflow/underflow. Very large/small in-range values use exponential display.
UI, share URLs, REST, and validation cases all call this same engine.

Limitations

Canonical Agent modes are convert / engineering / normalize / operate. dec-sci, sci-dec, numInput, coefInput, expInput, aInput, bInput are URL/engine adapter aliases, not the Agent contract.
Missing/invalid numbers → INVALID_NUMBER / MISSING_REQUIRED_INPUT
Division by zero in operate → DIVISION_BY_ZERO
Each numeric text token is at most512 characters. Normalize exponent is an integer within±10000. Decimal exponents in A×10^n are combined before one binary64 conversion; finite nonzero subnormals accepted; nonzero values rounded to zero are rejected.
Matching adapter aliases only; inactive/unknown fields and invalid mode/op are rejected. Shortest binary64 decimal display does not preserve significant figures. Shared URLs reach the server.

Sources

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

BIPM SI Brochure (9th edition) — Table 8 — SI prefixes (powers of 10³)
Supports: Engineering notation uses exponents that are multiples of 3 so values line up with SI prefixes
NIST SI prefixes — SI prefixes from 10⁻³⁰ to 10³⁰
Supports: Prefix names (milli, micro, kilo, mega, …) attached to engineering exponents
UC Berkeley CS61C Course Notes — Normalized Numbers — §2.1 Scientific Notation (Base-10)
Supports: Decimal scientific notation as a coefficient times a power of ten, normalization, and the distinction from binary floating-point representation. CalculatorX states its sign, zero and exponent policies separately. Mathematical representation reference only; not implementation validation or endorsement.

Methods

Algorithms this engine uses. Not external references.

IEEE-754 binary64 parse of decimal / E-notation / A×10ⁿ
Normalize via Number#toExponential; engineering exponent ≡ 0 (mod 3)
Test suites are not interchangeable: 20 published examples on this page · 124 automated engine checks (IUT) · CVP verification suite on Evidence (Manifest is the verification source of truth)

Verification disclosure

Aggregate outcomes, scope and artifact commitments are public. Complete test inputs, expected values, execution records and oracle infrastructure are retained privately. This summary does not independently reproduce the full verification run.