Home Developers Evidence math.numerical.optimize_1d

Public evidence

math.numerical.optimize_1d

Machine-checked verification for calculation version 1.0.0 · tier engine_tested

Verification

11/11 calculation tests · Production surface contract 2/2

  • Golden tests 3 / 3
  • Boundary tests 2 / 2
  • Property tests 6 / 6
  • Production surface contract 2 / 2
  • }
  • Engine tested Yes
  • Source checked Yes
  • Artifact integrity PASS
  • Production attestation Embedded snapshot: unpublished · Build schema 1.0.0 ready · Semantic contract ✓ · Attestation report not published on origin · Live production status STALE (1 capability; 163 remain CURRENT) @ 2026-09-19T00:00:17.039Z
  • Semantic contract PASS
  • Evidence attested at 2026-09-18T21:41:55.460Z
  • Last production check 2026-09-18T21:41:55.460Z
  • Public / cache
  • Origin
  • Supplemental domain review Not performed
  • Named expert review Not performed
  • release artifacts aligned PASS
  • schema rejects incomplete input PASS

Fingerprint sha256:166f7a18078f6c958bdda6bd86054d3af99e726cef52674f8f0b19e33725406d

Input schema sha256:054bcf7bdce29f2d27436749efabac89d72b99ac5288263fe6215c049207dc33 · Output schema sha256:3001316ee8d423d444434b0562895d683f1457f75074dd025a90e50282b5b783 · 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
one-dimensional-optimization
Engine
one-dimensional-optimization
Engine build
2026-09-19
Evidence core
2026-09-19T02:09:40.933Z
Rendered
2026-09-19T02:14:29.321Z
Last reviewed

Assumptions

  • Minimize only; f treated as unimodal on [a, b]
  • Not multivariate and not CAS
  • Polynomial degree ≤ 8

Limitations

  • Not multivariate / Nelder–Mead / gradient descent
  • Not maximization (min only)
  • a ≥ b → INVALID_INPUT
  • Polynomial degree ≤ 8
  • Not a CAS

Sources

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

Published checks

Golden, boundary, and property cases included in this evidence build.

IDKindStatusDetail
golden-x2goldenpassExpected exact_xmin=0 · exact_fmin=0 · Actual method=golden · integrand=poly · a=-1 · b=2 · xmin=-3.18796831533e-10 · fmin=0 · iterations=41 · n_eval=44
golden-singoldenpassExpected exact_xmin=4.71238898038469 · exact_fmin=-1 · Actual method=golden · integrand=sin · a=3.141592653589793 · b=6.283185307179586 · xmin=4.71238898725 · fmin=-1 · iterations=41 · n_eval=44
golden-brent-x2goldenpassExpected exact_xmin=0 · exact_fmin=0 · Actual method=brent · integrand=poly · a=-1 · b=2 · xmin=0 · fmin=0 · iterations=5 · n_eval=6
boundary-nelderboundarypassExpected INVALID_MODE · Actual INVALID_MODE
boundary-intervalboundarypassExpected INVALID_INPUT · Actual INVALID_INPUT
property-opt-x2propertypassmin x² at 0
property-opt-x2-fpropertypassmin x² f=0
property-opt-shiftpropertypassmin (x−1)² at 1
property-opt-sinpropertypassmin sin on [π,2π]
property-opt-exppropertypassmin eˣ on [0,1] at 0
property-opt-linpropertypassmin 1+2x at left end