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

instrument implementation / implementation-contract

Shallow-Water Wave Speed & Breaking Depth implementation

A source-bound implementation contract for Shallow-Water Wave Speed & Breaking 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
t5-135
Effect
Computation or source lookup only

Input and validation requirements

The specification does not define validation for zero depth, so the division H/d can become undefined. It also leaves wave-height convention and unit handling unspecified, allowing materially different breaking-depth results.

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": {
    "water_depth_m": 4,
    "incoming_wave_height_m": 1.2
  },
  "expected_outputs": {
    "wave_speed_m_per_s": 6.264184,
    "estimated_breaking_depth_m": 1.538462
  },
  "working": "c=√(gd)=√(9.81×4)=√39.24=6.264184 m/s. Breaking criterion H/d=0.78 gives d_break=H/0.78=1.2/0.78=1.538462 m."
}

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