engineering.process.cpmk_performance

Three distinct suites: educational examples on the calculator page, this legacy regression count (10/10 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 · 6/6 CVP boundary · 6/6 invalid · 1/1 property · 1/1 metamorphic · 8/8 O3 · 3/3 cross-interface · 6/6 CVP contract. digest 49bb2b418d18. O2: overall Taguchi Ppmk vs a separate-module sample identity (≤2 ULP). Not design-stage Cpmk, not Ppk, and not a Ppmk≥1.33 verdict. ≤2 ULP vs O3 applies only to the published tabulated Ppmk vectors (on target, off target, below target, an alias, a wider sample, a target away from the midpoint, one awkward sample, and ddof=0). It is not a whole-domain guarantee and does not cover design-stage Cpmk, Ppk, or a Ppmk≥1.33 verdict.

• Golden (oracle-backed) 4 / 4
• CVP boundary 6 / 6
• 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 Overall Taguchi Ppmk from a sample, LSL, USL, and a target, + O3 mpmath tabulated Ppmk.
• Assurance Engineering
• Deferred Not design-stage Cpmk, not Ppk, and not a Ppmk≥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:06ad4314f175cea0a5c115e154709e7133eef518e4f5a44b891ce23d03eab603

Input schema sha256:f7de48327bd4697a7a21aeb1e479a5789091dcfd0eceecfa40f3604d0617c75e · Output schema sha256:2fbca1a04606e89fbc19a7be7782debb87e1b86781cfacd2287f3b0e1e0793f8 · 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

cpmk-performance

Engine

cpmk-performance

Engine build

2026-09-24

Evidence core

2026-09-24T13:23:24.810Z

Rendered

2026-10-22T08:54:34.759Z

Last reviewed

—

Assumptions

• Overall Taguchi Ppmk = min(USL−x̄, x̄−LSL)/(3√(s²+(x̄−target)²)) from a sample. s is summarizeSample.
• Not design-stage Cpmk, not Ppk (no target), not Ppm (two-sided span), and not a 1.33 verdict.

Limitations

• Overall sample s — not design-stage Cpmk from a stated σ
• Not Ppk (Ppk has no target in the denominator)
• Not Ppm (that uses the two-sided span USL−LSL)
• This page does not issue a Ppmk≥1.33 verdict