engineering.process.cpm

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.1 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-24.o2-o3. Calculation version 1.0.1. CVP 1.0.0-proposed. 4/4 golden · 3/3 CVP boundary · 6/6 invalid · 1/1 property · 1/1 metamorphic · 8/8 O3 · 3/3 cross-interface · 6/6 CVP contract. digest 0ea009ab8875. O2: design-stage Taguchi Cpm vs a separate-module identity (≤2 ULP). Not Cp/Cpk, not Pp/Ppk, and not a Cpm≥1.33 verdict. ≤2 ULP vs O3 applies only to the published tabulated Cpm vectors (on target, off target, below target, an alias, a wider σ, a target away from the midpoint, one awkward sample, and a tiny offset). It is not a whole-domain guarantee and does not cover Cp/Cpk, Pp/Ppk, or a Cpm≥1.33 verdict.

• Golden (oracle-backed) 4 / 4
• CVP boundary 3 / 3
• Invalid input 6 / 6
• Property 1 / 1
• Metamorphic 1 / 1
• O3 high-precision 8 / 8
• Cross-interface 3 / 3
• 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 Design-stage Taguchi Cpm from stated μ, σ, LSL, USL, and a target, + O3 mpmath tabulated Cpm.
• Assurance Engineering
• Deferred Not Cp/Cpk, not Pp/Ppk from a sample, and not a Cpm≥1.33 verdict.

• 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:4d5079bedeacf57f26de17fba952d2f1562e4798037b7bf4fab7c3553a27d18d

Input schema sha256:df0231edd4b959b812174c682b498b44b1219713e181874c708c6b4979359733 · Output schema sha256:a76bedd43a0e3384a5a3ace2e1a509aa726fbed2ff0d1c5fc3675e001d05bac7 · 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.

Tool

cpm

Engine

cpm

Engine build

2026-09-23

Evidence core

2026-09-23T21:21:00.816Z

Rendered

2026-10-23T01:27:11.164Z

Last reviewed

—

Assumptions

• Taguchi Cpm = (USL−LSL)/(6√(σ²+(μ−target)²)) from stated μ, σ, LSL, USL, and target.
• Not Cp/Cpk (those ignore the target in the denominator), not Pp/Ppk, and not a 1.33 verdict.

Limitations

• Design-stage from stated μ and σ — not measured in-control SPC
• Not Cp/Cpk (those ignore the target in the denominator)
• Not Pp/Ppk (those use sample s and have no target)
• This page does not issue a Cpm≥1.33 verdict