Home Developers Evidence mechanical.statics.triangular_load_max_deflection

Public evidence

mechanical.statics.triangular_load_max_deflection

Machine-checked verification for calculation version 1.0.0 · tier engine_tested

CVP status

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance · one-sided triangle max |δ| = w0 L⁴ √(1−√(8/15)) (2+5√(8/15))/(450 E I); + O3 mpmath tabulated δ.

O3 tabulated vectors only.

Declared partition coverage
PASS · 5/5 declared partitions (main, alias, signed, awkward, invalid-domain)
Versions
Calculation 1.0.0 · CVP protocol 1.0.0-proposed · Evidence 2026-09-27.o2-o3
Verification revision
2026-09-27.o2-o3 · 1/1 property · digest b84f0c9fe61e

Verification

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

Three distinct suites: educational examples on the calculator page, this legacy regression count (2/2 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.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-27.o2-o3. Calculation version 1.0.0. CVP 1.0.0-proposed. 4/4 golden · 1/1 CVP boundary · 3/3 invalid · 1/1 property · 1/1 metamorphic · 8/8 O3 · 2/2 cross-interface · 6/6 CVP contract. digest b84f0c9fe61e. O2: delta vs a separate-module identity (≤2 ULP). Not midspan under the same triangle, and not a station curve. ≤2 ULP vs O3 applies only to the published tabulated triangular-load-maximum vectors.

  • Golden (oracle-backed) 4 / 4
  • CVP boundary 1 / 1
  • Invalid input 3 / 3
  • Property 1 / 1
  • Metamorphic 1 / 1
  • O3 high-precision 8 / 8
  • Cross-interface 2 / 2
  • CVP contract 6 / 6
  • Interfaces PASS · UI (SSR) / REST / MCP
  • Interface claim ui-ssr is query-result HTML, not a live browser session. Error-path engine·REST·MCP 1/1 (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.
  • Verified scope one-sided triangle max |δ| = w0 L⁴ √(1−√(8/15)) (2+5√(8/15))/(450 E I); + O3 mpmath tabulated δ.
  • Assurance Engineering
  • Deferred Not midspan under the same triangle, and not a station curve.
  • 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:384b824df333578b65313f7a652e4bc97c29d5ce92869461aff8de4f241c5b9f

Input schema sha256:f3a952a17d5b7aae8dca04ec78b31baa8273d54dbddff80c048ef0701e4f0f7f · Output schema sha256:dd3e1322aad6cb4452370243ed0926ca9f809c9206041787ab7fc92830cfa976 · 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
triangular-load-maximum
Engine
triangular-load-maximum
Engine build
2026-09-27
Evidence core
2026-09-27T08:15:46.336Z
Rendered
2026-11-10T05:18:42.198Z
Last reviewed
—

Limitations

  • Simply supported span
  • Largest deflection, not the midspan value
  • I is an input

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.