Source: https://guthlabs.ai/docs/instruments/dilution-calculator-c1v1-c2v2/

instrument / verified-clean

# Dilution Calculator (C1V1=C2V2)

The current ledger marks this instrument verified clean within the source-bound verification corpus.

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

## Inspectable records

[01**Overview**Purpose and lifecycle](<https://guthlabs.ai/docs/instruments/dilution-calculator-c1v1-c2v2/>)[02**Mechanism**Method and assumptions](<https://guthlabs.ai/docs/instruments/dilution-calculator-c1v1-c2v2/mechanism/>)[03**Implementation**Binding and validation](<https://guthlabs.ai/docs/instruments/dilution-calculator-c1v1-c2v2/implementation/>)[04**Qualification**Evidence and errata](<https://guthlabs.ai/docs/instruments/dilution-calculator-c1v1-c2v2/qualification/>)

## Ledger state

The current ledger marks this instrument verified clean within the source-bound verification corpus.

**Area**: Chemistry & Materials

**Tranche**: tranche-3

**Evidence ID**: t3-003

**Ledger rows**: 1

No ledger note is attached.

## Review findings

The core single-dilution formula is correct, but the serial-dilution input contract and dilution-factor terminology are not sufficiently specified. NEEDS_REVIEW specifically because it is ambiguous whether dilution factor plus steps means equal per-step factors, supplied per-step aliquot/final volumes, or a requested overall factor, and because the required validity constraints are not stated.

### Formula and scope findings

- C1V1=C2V2 is the standard dilution formula for conserving solute amount, provided C1 and C2 use the same concentration units and V1 and V2 use the same volume units.

- DF=Vfinal/Valiquot is correct for a single serial-dilution step when DF means the dilution factor and Valiquot is the volume transferred from the preceding solution. It is equivalent to Cbefore/Cafter only when the aliquot and final-volume definitions are explicit.

- The serial-chain behavior is underspecified: the instrument must state whether each step has an equal dilution factor, how each step's aliquot and final volume are supplied, and how intermediate and final concentrations are calculated.

- For a dilution, the specification should enforce C1 greater than or equal to C2 and Vfinal greater than or equal to Valiquot; otherwise the calculated diluent volume can be negative or the operation is not a dilution.

### Unit assumptions

- Concentrations must be expressed in compatible units; for example, mol/L may be used with mol/L, and mg/mL may be used with mg/mL.

- V1, V2, Vfinal, and Valiquot must be expressed in compatible volume units within each calculation.

- C1 is the concentration before dilution, C2 is the concentration after dilution, V1 is the aliquot or stock volume used, and V2 is the final total solution volume.

- For each serial step, DF equals final volume divided by aliquot volume, and the final volume includes the aliquot plus diluent.

- The examples assume ideal mixing, no solute loss, additive volumes, and concentrations that are low enough for C1V1=C2V2 to be applicable.

## Boundary hardening

**BREAK_CLAIMED** · SELF_FLAGGED

A zero stock concentration creates a division-by-zero and impossible mass-balance case that must be rejected; unitless volume entry also exposes a 1000-fold convention hazard.

## Errata and corrections

No applied erratum is attached to this unique-name record.

## Inspectable example

4 review vectors are recorded. One source-bound sample is shown below.

````
{
  "inputs": {
    "mode": "single",
    "stock_concentration": "10 mol/L",
    "target_concentration": "0.5 mol/L",
    "target_volume": "1 L"
  },
  "expected_outputs": {
    "stock_volume": "0.05 L",
    "diluent_volume": "0.95 L"
  },
  "working": "V1=(C2×V2)/C1=(0.5 mol/L×1 L)/(10 mol/L)=0.05 L. Diluent=V2−V1=1 L−0.05 L=0.95 L."
}
````

## Related workflows

[Buffer Benchdilutions](<https://guthlabs.ai/docs/instrument-workflows/buffer-bench/>)

## Sources and evidence

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

- `VERIFIED_LEDGER.json · VERIFIED_CLEAN`

- `evidence-tranche3/tranche3-results.json`

- `BOUNDARY_HAZARD_CATALOG.json`