Home Developers Evidence math.antilog

Public evidence

math.antilog

Machine-checked verification for calculation version 1.0.6 · 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. This is scoped interface coverage, not whole-domain assurance.

Declared partition coverage
PASS · 2/2 declared partitions (antilog, invalid-domain)
Versions
Calculation 1.0.6 · CVP protocol 1.0.0-proposed · Evidence 2026-10-13.antilog-alias-replay
Verification revision
2026-10-13.antilog-alias-replay · 5/5 property · digest 0a9ae66eb0aa

Verification

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

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.6 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-13.antilog-alias-replay. Calculation version 1.0.6. CVP 1.0.0-proposed. 32/32 golden · 19/19 CVP boundary · 23/23 invalid · 5/5 property · 4/4 metamorphic · 5/5 round-trip · 15/15 O3 · 49/49 cross-interface · 4/4 URL→result→graph · 5/5 CVP contract. digest 0a9ae66eb0aa.

  • Golden (oracle-backed) 32 / 32
  • CVP boundary 19 / 19
  • Invalid input 23 / 23
  • Property 5 / 5
  • Metamorphic 4 / 4
  • Round-trip 5 / 5
  • O3 high-precision 15 / 15
  • Cross-interface 49 / 49
  • URL → result → graph 4 / 4
  • CVP contract 5 / 5
  • Interfaces PASS · UI (SSR) / REST / MCP / URL→result→graph
  • Interface claim Success 30/30. 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
  • rest success payload validates schema PASS

Fingerprint sha256:05cd9c69b7de07af03b0a49f819608f37d7d4caafb23ac35d400f7e7bb58e157

Input schema sha256:e310142bf9f117afb5f812f0cfdf8363d1cc0964fcc5069447cb70a54ff0dd05 · Output schema sha256:449931cc55a5e14d805c273bb500e6df4752044f651c4223e19b18691fa96017 · 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-14
Evidence core
2026-10-14T02:50:33.742Z
Rendered
2026-10-22T08:54:35.079Z
Last reviewed
—

Assumptions

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

Limitations

  • Base must be > 0 and ≠ 1 → INVALID_BASE
  • Missing y → MISSING_REQUIRED_INPUT; overflow/underflow → RESULT_OVERFLOW / RESULT_UNDERFLOW

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.