Kinematics — Uniformly Accelerated Motion Solver mechanism

Model scope

The equations are valid for one-dimensional motion with constant acceleration, but the inverse-solving behavior is underspecified. The blank honest_label is a concern: the instrument should explicitly state 'constant-acceleration, one-dimensional kinematics' and distinguish displacement from distance. Define accepted input combinations, unit parsing/conversion, sign conventions, physical time constraints, multiple-root behavior, and degenerate-case handling before release.

• The three listed equations are standard constant-acceleration kinematics equations, but the specification does not define how to select and apply the correct equation for each combination of three known variables.
• The claim 'any 3 of {v0,v,a,s,t}' is incomplete without stating admissibility constraints and handling degenerate cases such as a=0, t=0, or insufficient information for a unique solution.
• Solving v²=v0²+2as for v requires a sign choice; the equation determines only the magnitude of velocity unless direction or a sign convention is supplied.
• Solving displacement-based cases for time can produce two mathematical roots; the specification does not state whether negative time is rejected or how multiple roots are presented.
• The formulas describe displacement s, not necessarily path distance; the instrument's terminology must not label s as distance unless that distinction is explicit.

Units and conventions

• v0, v, and s must use mutually consistent length/time units, such as m/s and m.
• Acceleration a must use the corresponding length/time² unit, such as m/s².
• Time t must use the corresponding time unit, such as seconds.
• Acceleration is constant over the interval, and the motion is one-dimensional along a defined positive direction.
• Inputs must carry or inherit an explicit sign convention; positive and negative velocity/displacement represent direction, not merely magnitude.

Inspectable vector

One of 4 source-bound review vectors:

{
  "inputs": {
    "v0": 5,
    "a": 2,
    "t": 4
  },
  "expected_outputs": {
    "v": 13,
    "s": 36
  },
  "working": "v = v0 + at = 5 + (2 × 4) = 5 + 8 = 13 m/s. s = v0t + ½at² = (5 × 4) + ½ × 2 × 4² = 20 + 1 × 16 = 36 m."
}

Failure boundary

BREAK_CLAIMED · SELF_FLAGGED

The input v0=5, v=5, t=0 creates a 0/0 division when solving for acceleration. Acceleration is undefined and the instrument should reject the acceleration result rather than return a numeric value.

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