Source: https://guthlabs.ai/docs/instruments/percent-yield-calculator/mechanism/

instrument mechanism / verified-clean

# Percent Yield Calculator mechanism

The inspectable method record for Percent Yield Calculator, kept separate from implementation and qualification.

Status: **VERIFIED_CLEAN**Lifecycle: **verified-clean**

## Model scope

The arithmetic engine is appropriate, but the catalog specification needs explicit validation rules for a positive, nonzero theoretical yield, nonnegative actual yield, matching product and stoichiometric basis, and unit compatibility. Values above 100% should be displayed honestly rather than clipped.

- The formula %yield=(actual/theoretical)×100 is the standard formula. The specification does not explicitly constrain actual and theoretical yields to represent the same substance on the same basis and in compatible units.

- The specification does not state that theoretical yield must be nonzero.

## Units and conventions

- Actual and theoretical yields must use the same unit before calculation, such as grams with grams or moles with moles.

- Actual and theoretical yields must refer to the same product and equivalent stoichiometric basis.

- The output is a dimensionless percentage.

## Inspectable vector

One of 4 source-bound review vectors:

````
{
  "inputs": {
    "actual_yield": 8.5,
    "theoretical_yield": 10,
    "unit": "g"
  },
  "expected_outputs": {
    "percent_yield": 85
  },
  "working": "%yield=(actual/theoretical)×100=(8.5 g/10.0 g)×100=0.85×100=85.0%"
}
````

## Failure boundary

**BREAK_CLAIMED** · SELF_FLAGGED

A theoretical yield of exactly zero causes division by zero and must be rejected. Negative yields also expose an unstated sign-validity convention.

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/percent-yield-calculator/>)[03**Implementation**](<https://guthlabs.ai/docs/instruments/percent-yield-calculator/implementation/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/percent-yield-calculator/qualification/>)

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `VERIFIED_LEDGER.json`

- `evidence-tranche2/tranche2-results.json`

- `BOUNDARY_HAZARD_CATALOG.json`
