Beaufort-to-Wave-Height Sea State 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

t7-117

Effect

Computation or source lookup only

Input and validation requirements

The lookup has an undefined out-of-domain input at Beaufort 13, which must be rejected, and an unlabeled wind-speed value such as 10 produces materially different results depending on whether it means m/s or km/h.

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": {
    "beaufort_number": 0
  },
  "expected_outputs": {
    "wave_height_range_m": {
      "minimum": 0,
      "maximum": 0
    },
    "sea_state_description": "Calm (glassy)",
    "wmo_sea_state_code": 0
  },
  "reference_data": {
    "wmo_sea_state_code": 0,
    "wave_height_range_m": [
      0,
      0
    ],
    "description": "Calm (glassy)",
    "source_convention": "WMO standard sea-state code table, widely tabulated standard value",
    "beaufort_to_sea_state_assumption": "Beaufort 0 -> WMO sea-state code 0; provisional identity mapping"
  },
  "working": "1. Read Beaufort number: B=0.\n2. Apply the stated test convention: sea-state code = B = 0.\n3. WMO code 0 gives wave-height range 0.0–0.0 m.\n4. Therefore the expected output is 0.0–0.0 m, Calm (glassy)."
}

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