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

instrument implementation / implementation-contract

# Magnitude ↔ Flux Ratio implementation

A source-bound implementation contract for Magnitude ↔ Flux Ratio; deployment and executable qualification remain separate.

Status: **VERIFIED_CLEAN**Lifecycle: **implementation-contract**

## Binding contract

This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.

**Record owner**: Guth Instruments

**Lifecycle**: verified-clean

**Evidence ID**: t2-005

**Effect**: Computation or source lookup only

## Input and validation requirements

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.

## Required corrections

No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.

## Inspectable interface fixture

The sample below is evidence for interface and validation tests, not a production implementation.

````
{
  "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."
}
````

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/magnitude-flux-ratio/>)[02**Mechanism**](<https://guthlabs.ai/docs/instruments/magnitude-flux-ratio/mechanism/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/magnitude-flux-ratio/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`