Home Developers Evidence math.lcm

Public evidence

math.lcm

Machine-checked verification for calculation version 1.0.3 · tier engine_tested

Historical evidence. This page is version 1.0.3 · engine_tested · 20/20 tests. It is not the current published claim. Current evidence is 1.0.4 (20/20 tests) · latest.

CVP status

CVP VERIFIED · production STALE · CVP protocol 1.0.0-proposed · Core assurance

≥2 integers; any zero → 0

Declared partition coverage
PASS · 8/8 declared partitions (lcm, zero, negative, beyond-safe-integer, multi-input-fold, method-unavailable, xcal, invalid-domain)
Versions
Calculation 1.0.3 · CVP protocol 1.0.0-proposed · Evidence 2026-09-16.sources-no-wolfram
Verification revision
2026-09-16.sources-no-wolfram · 3/3 property · digest 243e5df78591

Verification

Legacy regression suite: 20/20 calculation tests · Production surface contract 5/5

Three distinct suites: educational examples on the calculator page, this legacy regression count (20/20 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.

    STALE · Build schema 1.0.4 matches page · production binding STALE · Semantic contract ✓ · Last attestation PASS · current evidence changed · re-attestation required · CVP STALE · attestation STALE — Production CURRENT withheld · 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.0.3. CVP 1.0.0-proposed. 6/6 golden · 7/7 CVP boundary · 3/3 invalid · 3/3 property · 1/1 metamorphic · 1/1 cross-interface · 5/5 cross-calculator · 3/3 CVP contract. digest 243e5df78591.

  • Golden (oracle-backed) 6 / 6
  • CVP boundary 7 / 7
  • Invalid input 3 / 3
  • Property 3 / 3
  • Metamorphic 1 / 1
  • Cross-interface 1 / 1
  • Cross-calculator 5 / 5
  • CVP contract 3 / 3
  • Interfaces PASS · UI (SSR) / REST / MCP
  • Interface claim ui-ssr is query-result HTML, not a live browser session.
  • Assurance Core
  • release artifacts aligned PASS
  • schema output required declared PASS
  • schema valid input executes PASS
  • engine success output validates schema PASS
  • rest success payload validates schema PASS

Fingerprint sha256:62a0e9019643f335db75c98d5c88ecee0126aa9f73cf7bf254e05ebe0a8df03d

Input schema sha256:406a5bb31353872aa4fe85e38681683b0888c28cf55e160479c44d913b2e2676 · Output schema sha256:f1ed2b6e695a6cfece646896e9d9bedd8a4f1bb989bcbf17c38ca66e061106cf · 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
lcm
Engine
lcm
Engine build
2026-10-14
Evidence core
2026-10-14T04:17:16.233Z
Rendered
2026-10-21T01:08:25.778Z
Last reviewed
—

Assumptions

  • Integer inputs; negatives treated by absolute value.
  • If any input is 0, LCM = 0. LCM(0,0)=0 is a CalculatorX/Python convention, not a GCF-identity derivation.
  • For nonzero inputs the result is a positive integer.

Limitations

  • Integers only; negatives treated by absolute value
  • Each integer ≤ 48 decimal digits (product bound, not a mathematical bound)
  • If any input is 0, LCM = 0. LCM(0,0)=0 is a CalculatorX/Python convention (not a GCF-identity derivation)
  • Need at least two numbers → NEED_TWO_NUMBERS
  • Non-integers → INVALID_NUMBER
  • Integers beyond MAX_SAFE_INTEGER must be decimal strings in JSON

Sources

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

Methods

Algorithms this engine uses. Not external references.

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.