Source: https://guthlabs.ai/docs/instruments/magnitude-flux-ratio/

instrument / verified-clean

# Magnitude ↔ Flux Ratio

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

## Ledger state

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

**Area**: Earth & Space

**Tranche**: tranche-2

**Evidence ID**: t2-005

**Ledger rows**: 2

- duplicate: also verified in calibration-1 (double-verified, consistent) — counts once

## Review findings

The forward formula is standard and correct under the stated assumptions. The blank honest_label should be replaced with a clear label such as: 'Magnitude difference from positive, same-band flux ratio; inverse available. Fluxes must use compatible units.' The exact output mode and inverse formula must be specified before release.

### Formula and scope findings

- The stated formula is correct for the magnitude difference: m1−m2 = −2.5·log10(F1/F2).

- The claimed reverse calculation is not explicitly specified; it must use F1/F2 = 10^(-(m1−m2)/2.5) = 10^(-0.4·(m1−m2)).

- The spec does not define how the interface selects whether the output is magnitude difference or flux ratio, creating an output-mode ambiguity.

### Unit assumptions

- F1 and F2 must be positive, finite fluxes measured in the same units and the same photometric bandpass; their ratio is dimensionless.

- Magnitudes are dimensionless apparent magnitudes using the conventional astronomical sign convention.

- Flux values in different units must be converted before forming the ratio; compatible units cancel only after conversion.

## Boundary hardening

**BREAK_CLAIMED** · SELF_FLAGGED

A zero flux denominator produces an undefined flux ratio and non-finite logarithm; without explicit positive-flux validation, the instrument can emit an invalid result. The specification also has a sign/order convention hazard that can silently produce the reciprocal ratio.

## 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": "flux_to_magnitude_difference",
    "F1": 10,
    "F2": 25,
    "flux_unit": "Jy"
  },
  "expected_outputs": {
    "magnitude_difference_m1_minus_m2": 0.9948500218
  },
  "working": "F1/F2 = 10/25 = 0.4. log10(0.4) = -0.3979400087. m1−m2 = -2.5 × (-0.3979400087) = 0.9948500218."
}
````

## Related workflows

[Telescope Night Kitbrightness comparisons](<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-tranche2/tranche2-results.json`

- `BOUNDARY_HAZARD_CATALOG.json`