Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

instrument implementation / implementation-contract

Exoplanet Transit Depth implementation

A source-bound implementation contract for Exoplanet Transit Depth; deployment and executable qualification remain separate.

Status: VERIFIED_CLEANLifecycle: 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
t4-029
Effect
Computation or source lookup only

Input and validation requirements

A zero star radius produces an undefined division, and an oversized planet produces a raw depth above 100% unless the instrument validates or caps the result. Negative-radius input also reveals an unguarded sign-convention hazard.

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": {
    "planet_radius_km": 69570,
    "star_radius_km": 695700
  },
  "expected_outputs": {
    "depth_fraction": 0.01,
    "depth_percent": 1,
    "depth_ppm": 10000
  },
  "working": "1. Rp/Rs = 69570 / 695700 = 0.1. 2. ΔF/F = (0.1)^2 = 0.01. 3. Percent depth = 0.01 × 100 = 1%. 4. Ppm depth = 0.01 × 1000000 = 10000 ppm."
}

Other records

Sources and evidence

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

  • VERIFIED_LEDGER.json
  • evidence-tranche4/tranche4-results.json