HomeCalculatorsEngineeringConformity Decision Rule Calculator
Engineering calculator

Conformity Decision Rule Calculator

Apply a binary ILAC G8-style decision to a measured value y: simple acceptance (w=0) or guarded acceptance (LSL+w ≤ y ≤ USL−w). Runs locally. Not JCGM 106 risk tables and not TUR.

Instant result
Result
—

Enter values to calculate.

Inputs—
Mode—
Formula—
Trust summary CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance · Simple and guarded acceptance of y against lsl and usl, + O3 mpmath tabulated decision limits.
Input interpretation
Enter values to calculate.
Result
—
Verified scope
Simple and guarded acceptance of y against lsl and usl, + O3 mpmath tabulated decision limits.
Assurance
Engineering
Declared partition coverage
PASS · 7/7 declared partitions (alias, upper, guarded, fail, edge, pass, invalid-domain) · Matrix
Deferred
Not consumer risk and not an ILAC G8 guard-band width design.
Numerical scope
O2: simple and guarded acceptance limits vs a separate-module identity (≤2 ULP). Not consumer risk. ≤2 ULP vs O3 applies only to the published tabulated decision-rule vectors. Not consumer risk.
Known limitations
  • Core CVP does not include live graph, viewport, or pointer interaction.
Model
Binary simple or guarded acceptance on a measured y.
Scope
ILAC G8-style binary simple (w=0) or guarded acceptance
Verification
Engine tested · Source checked · v1.0.1 · CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance · Simple and guarded acceptance of y against lsl and usl, + O3 mpmath tabulated decision limits.· View Manifest · CVP overview · Specification
Versions
Calculation 1.0.1 · CVP protocol 1.0.0-proposed · Evidence 2026-09-25.o2-o3
Verification revision
2026-09-25.o2-o3 · 1/1 property · digest 2681fed0d989
Legacy regression
11/11 tests · Production surface contract 6/6
Trust layers
Verification VERIFIED · Production CURRENT · Overall CVP state: VERIFIED under CVP 1.0.0-proposed
Reference
O1 model · O3 expected_values · O3 numerical_behavior · O2 expected_values · O2 numerical_behavior
Interfaces
PASS · UI (SSR) / REST / MCP — 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.
Supplemental domain review
Not performed
Named expert review
Not performed
CVP suite
4/4 golden · 6/6 CVP boundary · 5/5 invalid · 1/1 property · 1/1 metamorphic · 8/8 O3 · 2/2 cross-interface · 6/6 CVP contract · Manifest
Sources
Sources
Evidence
1 legacy golden · 6 legacy boundary · legacy regression suite · 4/4 oracle-backed golden · 5/5 invalid · Artifact integrity PASS
This calculator CURRENT · Public schema 1.0.1 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓
Semantic contract
PASS
Full verification

Manifest identity, reference classes, interfaces, suite, and production records.

Formulas

Core equations used by this calculator.

SimpleLSL ≤ y ≤ USL
GuardedLSL + w ≤ y ≤ USL − w
iBinary pass/fail only. This page does not compute consumer/producer risk. Guard band computes GB without y. TUR is a ratio, not a decision.

How to use

1

Enter the measured value y

Same unit as the specification limits.

2

Enter LSL and/or USL

Two-sided when both are set (USL > LSL). One-sided when only one limit is present.

3

Choose simple or guarded

Simple uses w = 0. Guarded needs w or an already-expanded U (w = U). The band is fail, not conditional.

Example calculations

Common configurations with formula and result.

ϟ

Simple pass

y=6 · LSL=0 · USL=12

0 ≤ 6 ≤ 12
pass
ϟ

Guarded fail in the band

y=0.5 · LSL=0 · USL=12 · U=1

0.5 < 0+1
fail

Conformity Decision Rule calculator specification

Version 1.0.1 · Engine tested

Calculation status

Review policy · Evidence

Definition
Simple acceptance: pass if LSL ≤ y ≤ USL (w = 0). Guarded acceptance: pass if LSL+w ≤ y ≤ USL−w. The guard-band zone is fail. One-sided limits are allowed. Default rule is simple.
What it calculates
Binary simple or guarded acceptance on a measured y.
Inputs
  • y
  • lsl
  • usl
  • rule
  • w
  • U
Outputs
  • decision
  • rule
  • y
  • w
  • accept_lsl
  • accept_usl
Formula
simple: LSL ≤ y ≤ USL; guarded: LSL+w ≤ y ≤ USL−w
Assumptions
  • ILAC G8-style binary simple (w=0) or guarded acceptance
  • Default rule is simple
  • Guarded w from w or already-expanded U; the band is fail
  • Not JCGM 106 risk tables, not TUR, and not GB = k·u as a product
Units
  • same as y / LSL / USL; dimensionless decision
Boundary conditions
  • missing y or missing spec → MISSING_REQUIRED_INPUT
  • rule=guarded without w or U → MISSING_REQUIRED_INPUT
  • empty acceptance interval or unknown rule → INVALID_INPUT
Example
y=6 lsl=0 usl=12 rule=simple → pass
Validation cases

2 published on this page · 11/11 tests · Production surface contract 6/6 · View evidence

  • y=6 lsl=0 usl=12 rule=simple → pass
  • y=0.5 lsl=0 usl=12 rule=guarded U=1 → fail
Sources
Calculation version
1.0.1

Background

Interpretation and common distinctions.

Apply a binary simple or guarded acceptance to a measured value.

Supported and not supported

Supported — simple (w=0) and guarded (w or U) on y · one-sided or two-sided limits · API engineering.conformity.decision_rule

Not supported — JCGM 106 risk tables, conditional third outcome, TUR≥4 verdict, GB = k·u as a product, RSS of u_i

Agent / API notes

Capability id: engineering.conformity.decision_rule · tool id: decision-rule · pin 1.0.1.

{ "y": 6, "lsl": 0, "usl": 12, "rule": "simple" }

rule defaults to simple. Guarded needs w or U. Errors: MISSING_REQUIRED_INPUT, INVALID_NUMBER, VALUE_MUST_BE_POSITIVE, INVALID_INPUT.

Calculator URL stays /calc/engineering/decision-rule. There is no /calc/metrology.

Frequently asked questions

Key distinctions behind the calculation.

Is this the same as the Guard band page?

No. Guard band computes GB = k·u and optional acceptance limits. This page takes a measured y and returns pass or fail. Use Guard band to size w, then this page to decide.

Is a result in the guard band conditional?

No. This contract is binary. If y is inside the specification but outside the acceptance interval, the decision is fail. It does not implement a three-way conditional statement from JCGM 106.

Where does this run?

Locally in the browser by default. REST and MCP call the same metrology-engine conformity decision op.