HR Diagram Plotter implementation

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

t6-020

Effect

Computation or source lookup only

Input and validation requirements

The zero-luminosity input produces an undefined logarithm and must be rejected. Additional hazards remain because the specification does not define an explicit input-mode discriminator, the main-sequence/giant/dwarf zone boundaries, or the exact axis-direction implementation.

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": "Teff_L",
    "points": [
      {
        "id": "Sun",
        "Teff_K": 5772,
        "L_solar": 1
      }
    ]
  },
  "expected_outputs": {
    "sampled_points": [
      {
        "id": "Sun",
        "x_Teff_K": 5772,
        "y_L_solar": 1
      }
    ],
    "rough_stage": "main-sequence-like if the overlay labels the solar neighborhood as main sequence",
    "key_curve_features": [
      "The plotted point must lie at Teff = 5772 K and L/L_sun = 1.",
      "The point is a standard solar reference anchor; no numerical zone classification can be verified without zone boundaries."
    ]
  },
  "working": "The input already uses the assumed plot units. x = Teff = 5772 K. y = L/L_sun = 1. No conversion is needed. If the implementation instead receives 3.828e26 W: y = 3.828e26 W / 3.828e26 W per L_sun = 1 L_sun."
}

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-tranche6/tranche6-results.json