Home Developers Evidence math.antilog

Public evidence

math.antilog

Machine-checked verification for calculation version 1.0.7 · tier engine_tested

CVP status

CVP VERIFIED · CVP protocol 1.0.0-proposed · Core assurance

b > 0, b ≠ 1; canonical base/baseId/b and baseInput/yInput aliases reviewed, with canonical-field precedence. Selected inputs use strict decimal/scientific text≤512; nonzero-tozero and unknown keys reject; baseId/base/b/baseInput precedence is explicit.51 independent scalar vectors, not whole-domain assurance.

Declared partition coverage
PASS · 2/2 declared partitions (antilog, invalid-domain)
Versions
Calculation 1.0.7 · CVP protocol 1.0.0-proposed · Evidence 2026-10-27.full-review-v1
Verification revision
2026-10-27.full-review-v1 · 5/5 property · digest 0100576ce0d3

Verification

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

Three distinct suites: educational examples on the calculator page, this legacy regression count (33/33 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.0.7 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-27.full-review-v1. Calculation version 1.0.7. CVP 1.0.0-proposed. 54/54 golden · 19/19 CVP boundary · 46/46 invalid · 5/5 property · 4/4 metamorphic · 5/5 round-trip · 15/15 O3 · 71/71 cross-interface · 4/4 URL→result→graph · 6/6 CVP contract. digest 0100576ce0d3.

  • Golden (oracle-backed) 54 / 54
  • CVP boundary 19 / 19
  • Invalid input 46 / 46
  • Property 5 / 5
  • Metamorphic 4 / 4
  • Round-trip 5 / 5
  • O3 high-precision 15 / 15
  • Cross-interface 71 / 71
  • URL → result → graph 4 / 4
  • CVP contract 6 / 6
  • Interfaces PASS · UI (SSR) / REST / MCP / URL→result→graph
  • Interface claim Success 52/52. Error-path engine·REST·MCP 19/19 (status, code, calculation_version). SSR compared on URL-canonical requested calculations; empty query is idle (not an error) and JSON-typed object/array inputs are REST/MCP-only. Integration: URL → SSR result → Live graph current point (4/4). Hydration/slider/history are URL-canonical contracts, 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
  • schema rejects incomplete input PASS
  • rest success payload validates schema PASS

Fingerprint sha256:15b944be0d7f3ec555e76a36b458b40349daa61ec414ed8507a17b44719126ea

Input schema sha256:d7f0a91df9f97ea561577d07c91bb7270886c6e597b1db4749377c9f4e641a12 · Output schema sha256:66582a746c086441bd82d72139063a197673f181b866ca4d55f7053a35c625d4 · 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
anti-log
Engine
antilog
Engine build
2026-10-27
Evidence core
2026-10-27T04:15:34.062Z
Rendered
2026-10-28T03:01:57.874Z
Last reviewed
—

Assumptions

  • Real arithmetic; base b > 0 and b ≠ 1.
  • Result x is positive for real y when b > 0.

Limitations

  • x=b^y for finite y and positive finite b≠1. Omitted base defaults10. Scalar output remains unrounded binary64; overflow and result rounding tozero reject.
  • Selected alias precedence: y then yInput; baseId then base; selected explicit preset/numeric base overrides b/baseInput; custom uses b then baseInput; absent base token uses b then baseInput. Nullish aliases fall through. Ignored shadow fields do not change the selected value.
  • Selected numeric text is strict decimal/scientific up to512 characters; nonzero text rounding tozero rejects NUMERIC_UNDERFLOW. Explicit blank/invalid base rejects instead of defaulting. Unknown keys reject; compare/digits are validated presentation-only options.
  • Symbolic e means Math.exp(y); numeric/custom Math.E remains binary64 Math.pow. No proximity snapping.51 independent Decimal150/250 scalar references use2ULP fixed-vector budget; existing O3 budget retained, no whole-domain guarantee.
  • Display precision is rounding only. Inverse uses unrounded x and is not independent verification; x rounded to1 cannot recover nonzero y. Conditioning depends on |y| nearbase1 and |y ln b| for exponent perturbations.
  • Typing local; shared URLs/REST/MCP send inputs and may enter logs. Native exports retain scalar output and raw provided inputs.

Sources

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

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.