Home Developers Evidence mechanical.statics.slip_or_tip

Public evidence

mechanical.statics.slip_or_tip

Machine-checked verification for calculation version 1.0.0 · tier engine_tested

CVP status

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance · Level surface: P_slip = μW and P_tip = W b/(2 d); P is the smaller. + O3 mpmath tabulated P.

O3 tabulated vectors only.

Declared partition coverage
PASS · 5/5 declared partitions (slip, tip, alias, 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 fcf2cdd2fb94

Verification

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

Three distinct suites: educational examples on the calculator page, this legacy regression count (7/7 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 · 4/4 CVP boundary · 6/6 invalid · 1/1 property · 1/1 metamorphic · 8/8 O3 · 2/2 cross-interface · 6/6 CVP contract. digest fcf2cdd2fb94. O2: P vs a separate-module identity (≤2 ULP). Not an incline, not wedges, not screws, and not belts. ≤2 ULP vs O3 applies only to the published tabulated slip-or-tip vectors.

  • Golden (oracle-backed) 4 / 4
  • CVP boundary 4 / 4
  • Invalid input 6 / 6
  • 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 Level surface: P_slip = μW and P_tip = W b/(2 d); P is the smaller. + O3 mpmath tabulated P.
  • Assurance Engineering
  • Deferred Not an incline, not wedges, not screws, and not belts.
  • 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:dc42fbe4b796b5ff53f2a28767251849b8f1db6c2b324139a1f2f0f775075e51

Input schema sha256:3f06e14f0ea2ed86e3868e51a88039f2ca32bf4fa75e61e11d96c88cad993e5e · Output schema sha256:4154efade7cc81b1596a2ac33880a0326cd0e241674e0474bc48b172b0f1f4d4 · 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
slip-or-tip
Engine
slip-or-tip
Engine build
2026-09-27
Evidence core
2026-09-27T08:15:46.336Z
Rendered
2026-11-10T05:18:42.164Z
Last reviewed
—

Limitations

  • The surface is level and the force is horizontal
  • The weight acts through the center of a base of width b
  • mode is slip, tip, or either
  • Not an incline, a wedge, a screw, or a belt

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.