Before the simulation starts
The model assigns a speed to each released striker. A real device must first create that speed. D02 calculates ideal lower bounds on launch force, distance and time. No launcher is simulated.
D02 / DEVICE DEMANDS + C02 / CONTACT ACCESS
A numerical impact is not yet a mechanism. This iteration asks what must move, what must stay clear, and which force belongs to which part of the event.
Research direction: Ashley Kalkowski.
06 October 2026, 19:01 UTC · Numerical postprocessing and unbuilt CAD.

01 / THE MISSING CONNECTION
The model assigns a speed to each released striker. A real device must first create that speed. D02 calculates ideal lower bounds on launch force, distance and time. No launcher is simulated.
The contact law determines a collision force as the striker and specimen move. That force is not the earlier launcher command. D02 reconstructs impulse and work from the saved motion and checks the accounting.
A striker can continue moving after the recording ends. The measured-in-model 0.17-second travel span does not specify a complete guide, catcher or reset mechanism. No stopping design is validated.
The parent is an uncalibrated elastic cantilever with ideal released strikers. Attached shaker armatures, preloaded piezo elements and guided powered stages have different dynamics. This study does not silently substitute one for another.
02 / THE RETAINED NUMERICAL EVIDENCE
All36 source histories end with nonzero striker velocity. The largest observed0.17-second span is72.069630mm; the largest sampled contact force is25.093330N. These extrema come from different retained histories; each identity is recorded in the JSON.


| Profile | Force cap | Stroke | Failed bounds | Met bounds |
|---|---|---|---|---|
| H01 | 0.1 N | 5 mm | 288 / 288 fail | 0 / 288 pass necessary screen |
| H02 | 0.5 N | 10 mm | 0 / 288 fail | 288 / 288 pass necessary screen |
| H03 | 2 N | 5 mm | 0 / 288 fail | 288 / 288 pass necessary screen |
| H04 | 5 N | 2 mm | 0 / 288 fail | 288 / 288 pass necessary screen |
The four force/stroke profiles were fixed before postprocessing. They are hypothetical net mechanical caps, not product specifications. A passed energy inequality is a necessary ideal screen only; it does not establish a working actuator, a budget, or a fracture result.
144 existing input rows,288 striker assignments,1,152 algebraic screens,18 full traces and36 motion histories. No new integration. All13 author tests and the separate full computational audit passed. All R07 input hashes were retained. Failed necessary launch screens remain in the result records.
Full derived result JSON · Separate computational review · Frozen plan
03 / A SPECIFIC CAD CORRECTION
The C01 Duet concept puts its heads over solid carriage plates. For a head approaching a specimen underneath, that plate is an obstruction. C02 makes the path explicit and tests clearance against the generated geometry.
The revised polygonal apertures retain a minimum1.488756mm geometric margin after the explicitly assumed0.5mm radial positioning allowance. Undersized and touching controls remain documented.




| Check | Nominal model result |
|---|---|
| Minimum guarded port-edge margin | 1.488756 mm |
| Rail margin | 28.5 mm |
| Post margin | 24.5 mm |
| Head-to-head guarded margin | 21 mm |
| Undersized port control | Interference, as expected |
| Exact nominal tangency control | Touching, as expected |
The revision uses a stated lateral separation between two ports. The one-dimensional R07 reference can place both ideal forces at the same axial point; it does not resolve this lateral layout or its torsional effects. The geometry is not a verified implementation of that simulation.
Geometry checks cover the declared aperture and motion envelope. Component fit, fasteners, stiffness, cable routing, actual travel drive, capture, thermal behavior and physical performance remain engineering tasks. The original C01 files stay unchanged and accessible.
04 / CHANGE THE ASSUMPTIONS
Explore a separate, ideal launch from rest. The force cap is the net accelerating force on the chosen moving mass. Gravity, friction, driver dynamics, attached mass, transfer losses and reset are excluded.
Kinetic energy is ½mv². With a nonnegative net force bounded by F, the minimum ideal stroke is E/F and the minimum ideal time is mv/F. A constant force over the chosen stroke would require E/s. This calculator does not find a resonant frequency, drive hardware or select a device.
05 / READ THE RATINGS IN CONTEXT
Sine peak, random RMS, shock peak and travel are separate ratings. They do not describe a single simultaneously achievable operating point.
Primary specificationAn attached armature or moving stage changes the mass and dynamics. Continuous force, duty-limited force, stroke and back EMF constrain different parts of the event.
Primary specificationFree displacement and blocked force are endpoints of a load-dependent relationship. Preload, stiffness and frequency affect the operating displacement.
Primary specificationThese primary sources explain specification boundaries. No product is selected, priced or certified as compatible. Third-party PDFs and product imagery are linked rather than redistributed.
06 / REPRODUCE THE CHECK
Trace postprocessing, ideal launch bounds, tests, frozen plan, results, independent verification and generated plots. Original R07 traces remain separate downloads.
Download D02 · 0.63 MBSHA-2569ec63cc50e53ed5286bcf07a31ad9043d519f7b2291cb2520695040ae4b1d72d
Parametric source, part meshes, assembly views, geometric clearance checks and deliberately failing controls. An unbuilt geometry study.
Download C02 · 0.99 MBSHA-25617a1cede9b0e75a60eb737a595514d58c1702018fc14aba63797375ec6718b12
Exact public file manifest · Parent R07 source and full traces
D02 portable supplement - public packaging instructions Place device-demand/ beside efficiency/ from the prior numerical releases. The calculator uses Python 3.10+ and NumPy 1.26+. Plotting also uses Matplotlib. The 13 author unit tests and ideal launch CLI do not require the R07 archive. From device-demand/: python -m unittest test_device_demand -v python device_demand.py launch --mass-kg 0.01 --speed 1 --force-cap 0.5 --stroke 0.01 --output launch-001 To reproduce all D02 numerical outputs, first extract the R04, R05, R06 and R07 core overlays and obtain all 18 separate R07 NPZ files. Preserve their recorded paths under efficiency/results/iteration07/traces/. Then: python device_demand.py study --r07-root ../efficiency --output rerun-001 To regenerate the published figures using the provided frozen summary: python plot_demands.py --summary results/D02_summary.json --output figures-rerun-001 Every output argument above must name a new path. Existing evidence is refused, including an existing empty directory. A numerical rerun can have different elapsed time and its source inventory can include the optional plot script added after the original calculation freeze. This does not alter the original report's four-file source map. Compare numerical fields and retained input hashes, not the entire JSON file's hash across reruns. The final published figure directory is figures-v2/. Its separate manifest binds the plotting source, exact D02 summary and all seven plot/data files. The first figure layout was retained privately; v2 fixes legend placement. No numerical input, trajectory, or calculation result changed for the plots. PUBLIC-FILES.json is an exact allowlist relative to device-demand/. It does not include itself, local bytecode, prior drafts, parent archives or traces. The independently prepared reviewer public subset is packaged separately from output/device-demand-review/public using its own exact allowlist. D02 performs 1,152 algebraic source/profile screens and derives 36 histories from 18 existing full traces. It runs zero new trajectory integrations and zero physical trials. Its four force/stroke profiles are hypothetical. The observed 0.17 s motion window is not complete launch, guide or catcher travel. All 36 strikers are still moving at the endpoint. No hardware capability, fracture, heat limit, repeat-cycle throughput or assembly fit is validated.
Extract to a fresh folder and follow the included README. Preserve the original evidence when reproducing calculations. Python and its listed dependencies are separate installations. The programs do not operate instruments.
07 / WHAT MUST IMPROVE NEXT
Continue to the E01 component assemblies and operating models
The next physical connection needs a specified moving assembly, measured force and motion, a known contact geometry and a complete energy boundary. A clear port does not prove that a housing can carry a load; a favorable energy bound does not identify a viable actuator. Calibration and withheld-condition tests must precede claims about a chosen split in rock.
Research direction: Ashley Kalkowski. Computational implementation and review used Codex assistance. Established mechanics and dependency terms remain attributed. This release makes project files inspectable; it does not add a blanket reuse licence or a patent-status claim.