Source: https://guthlabs.ai/docs/instruments/angular-size-physical-size/

instrument / verified-clean

# Angular Size ↔ Physical Size

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

**Evidence ID**: t4-089

**Ledger rows**: 1

No ledger note is attached.

## Review findings

The stated formula is standard for the small-angle approximation, and the honest label correctly identifies that limitation. Review is required because angular units, diameter-versus-radius semantics, validity bounds, and zero/invalid-input behavior are not fully specified.

### Formula and scope findings

- The small-angle relation θ = size/distance is correct only when θ is small and size is the full physical diameter corresponding to the full angular diameter.

- For larger angular sizes, the exact full-diameter relation is θ = 2·atan((size/2)/distance); the specification does not state the allowable small-angle range.

- The input units for angular size are unspecified even though the formula requires radians.

### Unit assumptions

- Angular size θ must be in radians before applying the formula; degrees must be converted using θ_rad = θ_deg·π/180, and arcseconds using θ_rad = θ_arcsec·π/(180·3600).

- Physical size and distance must use the same linear units.

- size is assumed to mean full linear diameter, and angular size is assumed to mean the corresponding full angular diameter.

- The geometry is Euclidean and the object is sufficiently distant for the small-angle approximation.

## Boundary hardening

**BREAK_CLAIMED** · SELF_FLAGGED

A zero-distance input produces an undefined angular size and must be rejected; additionally, an angular-size unit ambiguity can change the computed physical size from approximately 1.74533 m to 100 m.

## 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": {
    "physical_size_km": 3474,
    "distance_km": 384400
  },
  "expected_outputs": {
    "angular_size_rad": 0.00903746098
  },
  "working": "θ = size/distance = 3474 km / 384400 km = 0.00903746098 rad."
}
````

## Related workflows

[Telescope Night Kittarget size sanity](<https://guthlabs.ai/docs/instrument-workflows/telescope-night/>)

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

- `BOUNDARY_HAZARD_CATALOG.json`