Uniform Circular Motion Calculator 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

t3-011

Effect

Computation or source lookup only

Input and validation requirements

The specification does not state validation for r=0, which makes a_c and F_c undefined and represents an invalid circular-motion state. It also does not define whether a signed v is treated as a directional velocity or as a nonnegative speed for T and f.

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": {
    "v": 10,
    "v_unit": "m/s",
    "r": 5,
    "r_unit": "m",
    "mass": 2,
    "mass_unit": "kg"
  },
  "expected_outputs": {
    "a_c": 20,
    "a_c_unit": "m/s^2",
    "F_c": 40,
    "F_c_unit": "N",
    "T": 3.1415926536,
    "T_unit": "s",
    "f": 0.3183098862,
    "f_unit": "Hz"
  },
  "working": "a_c=v²/r=10²/5=100/5=20 m/s². F_c=ma_c=2×20=40 N. T=2πr/v=2×π×5/10=π=3.1415926536 s. f=1/T=1/π=0.3183098862 Hz."
}

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