Public evidence

math.scientific_notation

Machine-checked verification for calculation version 2.0.0 · 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.0 · 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 f88ab39bc1d8

Verification

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

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 2.0.0 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 2.0.0. 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 · 6/6 CVP contract. digest f88ab39bc1d8. 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 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:79247c5984f5620b9ef17a07db08f7fdd75ab6ca22af81c141e7b444cc23c9b9

Input schema sha256:5ba7e76cf93a3dbf7078ca878350bfbb77e766b6e082ecd50e24931c503afcbf · Output schema sha256:0c7f5fc2cc591d304952aa956c6d9b2ffd9e642143d9bb19fd56db601ebc4586 · 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-21
Evidence core: 2026-09-21T23:43:55.706Z
Rendered: 2026-09-22T09:23:10.126Z
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

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
`convert-12300`	golden	pass	Expected coef=1.23 · exp=4 · Actual decimal=12300 · value=1.23 × 10⁴ · mode=convert · calculation_version=2.0.0 · heading=Scientific notation · scientific=1.23 × 10⁴ · e_notation=1.23e4 · engineering=12.3 × 10³
`convert-1`	golden	pass	Expected coef=1 · exp=0 · Actual decimal=1 · value=1 × 10⁰ · mode=convert · calculation_version=2.0.0 · heading=Scientific notation · scientific=1 × 10⁰ · e_notation=1e0 · engineering=1 × 10⁰
`convert-zero`	golden	pass	Expected coef=0 · exp=0 · Actual decimal=0 · value=0 · mode=convert · calculation_version=2.0.0 · heading=Scientific notation · scientific=0 · e_notation=0e0 · engineering=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