Source: https://guthlabs.ai/docs/instruments/wentworth-grain-size-classifier/

instrument / verified-clean

# Wentworth Grain-Size Classifier

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/wentworth-grain-size-classifier/>)[02**Mechanism**Method and assumptions](<https://guthlabs.ai/docs/instruments/wentworth-grain-size-classifier/mechanism/>)[03**Implementation**Binding and validation](<https://guthlabs.ai/docs/instruments/wentworth-grain-size-classifier/implementation/>)[04**Qualification**Evidence and errata](<https://guthlabs.ai/docs/instruments/wentworth-grain-size-classifier/qualification/>)

## Ledger state

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

**Area**: Earth & Space (astronomy, orbital mechanics, meteorology, geology, geodesy, oceanography)

**Tranche**: tranche-7

**Evidence ID**: t7-103

**Ledger rows**: 1

No ledger note is attached.

## Review findings

The logarithmic φ formula and standard Udden-Wentworth classification concept are sound, but the specification needs the inverse formula for φ inputs, an explicit complete lookup table, a boundary convention, and strict positive-diameter validation. The honest label should state that this is a Udden-Wentworth sediment-size classifier, not a complete sedimentological description; shape, sorting, composition, and depositional context are not computed.

### Formula and scope findings

- The stated φ = -log2(d_mm) formula is correct when d_mm is a positive numerical grain diameter expressed in millimetres.

- Because the input may be a φ value, the inverse formula d_mm = 2^(-φ) is required but is not stated.

- The Wentworth boundary-inclusion convention is unspecified. The expected categories below assume lower diameter bounds are inclusive and upper bounds are exclusive: [lower, upper). Without that convention, exact boundary inputs such as 1 mm or 0.5 mm are ambiguous.

- The table should explicitly define the full category intervals, including boulder (>256 mm) and clay (<0.00390625 mm).

### Unit assumptions

- The logarithm argument is the numerical grain diameter in millimetres; d_mm must be greater than zero.

- A diameter supplied in micrometres or another unit must be converted to millimetres before applying the formula; 1 micrometre = 0.001 mm.

- For φ input, φ is dimensionless and the diameter used for classification is d_mm = 2^(-φ).

- Expected category results use the convention [lower diameter, upper diameter), with the smallest category receiving an exact lower-bound value.

## Boundary hardening

**BREAK_CLAIMED** · SELF_FLAGGED

The zero-diameter input produces an undefined logarithm and must be rejected. The specification also does not explicitly define exact class-boundary endpoint ownership or enforce the diameter unit, creating boundary and unit-convention failure risks.

## 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": {
    "grain_diameter": 1,
    "unit": "mm"
  },
  "expected_outputs": {
    "phi": 0,
    "class_name": "very coarse sand"
  },
  "reference_data": {
    "rows": [
      {
        "diameter_mm": 1,
        "phi_boundary": 0,
        "class_name": "very coarse sand",
        "source_convention": "Udden-Wentworth grain-size scale, widely tabulated standard value"
      },
      {
        "diameter_mm": 2,
        "phi_boundary": -1,
        "class_name": "granule",
        "source_convention": "Udden-Wentworth grain-size scale, widely tabulated standard value"
      }
    ],
    "boundary_convention": "[lower diameter, upper diameter)"
  },
  "working": "φ = -log2(1.0) = -log2(1) = 0.0. The diameter is at the 1.0 mm boundary and, using [lower, upper), belongs to the 1–2 mm very coarse sand interval."
}
````

## Related workflows

No source-defined multi-instrument workflow membership is recorded.

## 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-tranche7/tranche7-results.json`

- `BOUNDARY_HAZARD_CATALOG.json`