Torque Calculator mechanism

Model scope

The single-force magnitude formula is standard under the stated angle interpretation. The specification needs an explicit angle-unit policy, a direction-input/sign convention, and a signed summation formula for multiple forces before it can receive PASS.

• τ=rFsinθ is the correct scalar magnitude of torque only when θ is the included angle between the position vector r and the force vector F; it does not by itself determine clockwise versus counterclockwise direction.
• No explicit formula is provided for net torque from multiple forces. A standard 2D implementation should assign a sign by rotation sense and compute τ_net=Στ_i, commonly taking counterclockwise as positive and clockwise as negative.
• The inputs do not specify how the clockwise/counterclockwise sense is supplied or inferred. The scalar values r, F, and θ alone cannot uniquely determine torque direction.

Units and conventions

• r must be a length, typically in meters; F must be in newtons; torque is then in newton-metres (N·m).
• θ must be interpreted as the included angle between r and F and supplied in degrees or radians consistently; the implementation must explicitly document and convert the chosen input unit.
• For multiple forces, all torque values must use the same length and force units before summation.
• The test vectors use counterclockwise as positive and clockwise as negative for net torque.

Inspectable vector

One of 4 source-bound review vectors:

{
  "inputs": {
    "r_m": 0.4,
    "F_N": 50,
    "theta_deg": 30,
    "rotation_sense": "CCW"
  },
  "expected_outputs": {
    "torque_Nm": 10,
    "direction": "CCW"
  },
  "working": "sin(30°)=0.5. τ=rFsinθ=(0.4 m)(50 N)(0.5)=20×0.5=10 N·m. The supplied rotation sense is CCW, so direction=CCW."
}

Failure boundary

BREAK_CLAIMED · SELF_FLAGGED

The extreme finite inputs r=1e308 and F=1e308 overflow the plain JavaScript arithmetic result to Infinity instead of producing a finite torque. The specification also leaves angle units and sign conventions implicit, creating additional ambiguity.

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
• BOUNDARY_HAZARD_CATALOG.json