Public evidence

math.scientific_notation

Machine-checked verification for calculation version 1.1.1 · tier engine_tested

Open calculator API Capability Download JSON CVP Manifest MCP Review policy

CVP: CVP VERIFIED · CVP protocol 1.0.0-proposed · Core assurance · all published modes· 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. · Protocol · Schema · Production report

Declared partition coverage: PASS · 5/5 declared partitions (convert, normalize, engineering, operate, invalid-domain)
Versions: Calculation 1.1.1 · CVP protocol 1.0.0-proposed · Evidence 2026-09-16.sources-no-wolfram
Verification revision: 2026-09-16.sources-no-wolfram · 5/5 property · digest 4a53cbc5afe2

Verification

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

Three distinct suites: educational examples on the calculator page, this legacy regression count (6/6 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 1.1.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-09-16.sources-no-wolfram. Calculation version 1.1.1. CVP 1.0.0-proposed. 21/21 golden · 1/1 CVP boundary · 7/7 invalid · 5/5 property · 2/2 metamorphic · 2/2 round-trip · 4/4 cross-interface · 3/3 CVP contract. digest 4a53cbc5afe2. 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) 21 / 21
CVP boundary 1 / 1
Invalid input 7 / 7
Property 5 / 5
Metamorphic 2 / 2
Round-trip 2 / 2
Cross-interface 4 / 4
CVP contract 3 / 3
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 valid input executes PASS
engine success output validates schema PASS

Fingerprint sha256:9a238f0352b1ee8fac2433daff2b1604ed630fa6ba1278faa001a1756432dc31

Input schema sha256:8401fb09da01304188d42eb3b98befb8fc6556ac1c214494cb4e66659e678866 · Output schema sha256:c78ddeb1a0b3992927c92f7b3768727bce008e6543747be1b605dc2625f6772f · 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-09-16
Evidence core: 2026-09-16T06:41:00.884Z
Rendered: 2026-09-16T22:03:43.784Z
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

Missing/invalid numbers → INVALID_NUMBER / MISSING_REQUIRED_INPUT
Division by zero in operate → DIVISION_BY_ZERO

Sources

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

OpenStax Elementary Algebra 2e — Scientific Notation — 5.2 An application of exponents: scientific notation
Supports: A number in scientific notation is written A × 10ⁿ with 1 ≤ |A| < 10 and integer n; 0 is the exception
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

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)

Legacy published checks

Golden and boundary cases from the legacy Evidence JSON. CVP property, metamorphic, round-trip, O3, and interface statuses/checks are recorded in the Manifest — including SKIP when a suite has no vectors.

ID	Kind	Status	Detail
`dec-sci-12300`	golden	pass	Expected coef=1.23 · exp=4 · Actual coef=1.23 · exp=4
`dec-sci-1`	golden	pass	Expected coef=1 · exp=0 · Actual coef=1 · exp=0
`dec-sci-zero`	golden	pass	Expected coef=0 · exp=0 · Actual coef=0 · exp=0
`sci-dec-basic`	golden	pass	Expected 350 · Actual 350
`bad-mode`	boundary	pass	Expected INVALID_MODE · Actual INVALID_MODE
`missing-value`	boundary	pass	Expected INVALID_NUMBER · Actual INVALID_NUMBER