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

instrument / verified-clean

Lorentz Force Calculator

The current ledger marks this instrument verified clean within the source-bound verification corpus.

Status: VERIFIED_CLEANLifecycle: verified-clean

Inspectable records

Ledger state

The current ledger marks this instrument verified clean within the source-bound verification corpus.

Area
Physics — Kinematics/Projectiles/Orbits, Forces/Energy/Momentum, Rotational Dynamics, Gravitation, Oscillations/Waves, Optics, E&M Fields, Relativity, Quantum, Statistical Thermo
Tranche
tranche-5
Evidence ID
t5-201
Ledger rows
1

No ledger note is attached.

Review findings

Core physics formula passes under the stated SI assumptions, but the unqualified input units and omitted explicit magnitude formula require review. The honest_label value 'n/a' does not disclose the SI-unit requirement, three-dimensional-vector constraint, or signed-charge behavior; the user-facing label should state those limitations.

Formula and scope findings

  • The vector formula F=q(E+v×B) is correct for the Lorentz force, provided q is a scalar charge and v, E, and B are three-dimensional vectors in compatible units.
  • The specification claims to output force magnitude but does not state its formula; it should explicitly define |F|=sqrt(Fx^2+Fy^2+Fz^2).
  • The specification does not state that all vectors must contain exactly three components.

Unit assumptions

  • The examples assume SI units: q in coulombs (C), v in metres per second (m/s), E in volts per metre (V/m, equivalent to N/C), B in teslas (T), and F in newtons (N).
  • The electric and magnetic terms are dimensionally compatible because (m/s)·T=N/C.
  • All vector components must use mutually compatible units; the current input specification does not identify or enforce units.
  • For the fourth test vector, the velocity is supplied in km/h and must be converted to m/s before applying the formula.

Boundary hardening

BREAK_CLAIMED · SELF_FLAGGED

The extreme-magnitude vector causes the magnetic cross-product component (1e308)(1e308)=1e616, which overflows ordinary JavaScript IEEE-754 arithmetic to Infinity. The instrument should reject or explicitly flag this input instead of treating Infinity as a normal finite result.

Errata and corrections

No applied erratum is attached to this unique-name record.

Inspectable example

4 review vectors are recorded. One source-bound sample is shown below.

{
  "inputs": {
    "q": 0.000002,
    "v": [
      0,
      2000,
      0
    ],
    "E": [
      30000,
      0,
      0
    ],
    "B": [
      0,
      0,
      0.5
    ],
    "units": {
      "q": "C",
      "v": "m/s",
      "E": "V/m",
      "B": "T"
    }
  },
  "expected_outputs": {
    "F": [
      0.062,
      0,
      0
    ],
    "magnitude": 0.062
  },
  "working": "v×B = [vyBz−vzBy, vzBx−vxBz, vxBy−vyBx] = [2000×0.5−0×0, 0×0−0×0.5, 0×0−2000×0] = [1000,0,0]. E+v×B = [30000,0,0]+[1000,0,0] = [31000,0,0]. F = q(E+v×B) = 2×10^-6×[31000,0,0] = [0.062,0,0] N. |F| = sqrt(0.062^2+0^2+0^2) = 0.062 N."
}

Related workflows

No source-defined multi-instrument workflow membership is recorded.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • VERIFIED_LEDGER.json · VERIFIED_CLEAN
  • evidence-tranche5/tranche5-results.json
  • BOUNDARY_HAZARD_CATALOG.json