Bench roadmap
The design benches are the product now, not a side project. Four instruments, one brand, an ongoing optimization phase: build what gets used, measure what it saves, retire what does not.
Shipped
- Design lab: 3D lattice at 10 cm, eight part types, weld/hinge/pin/motor joints, live watch on the selected part, trace, gravity and single-step, four presets, STL and BOM export, local scene save.
- Drivetrain bench: flywheel inertia, up to three gear stages, flywheel on slow or fast shaft, generator curve, drag, reflected inertia, ratio sweep, cycle and burst panel, generator bank split.
- Hydro sizer: Darcy friction with bore comparison, gross to net head, output and annual energy, hydrokinetic rotor mode, recirculating loop card, vacuum lift versus ram pump.
- Power plan: three household tiers, water and solar sizing, storage with autonomy, auxiliary self-consumption, component list.
- Shared bench bar across all four instruments, 44 px touch targets, brand palette.
Now in progress
- Touch and phone pass on the 3D lab: pointer capture, pinch zoom, one-finger orbit, larger joint buttons.
- Design links: encode a scene into the URL so a build can be bookmarked, shared, or reopened tomorrow.
Next queued
| Item | Why it earns its place |
| Beam calculator in the lab | Static load, sag, and safety factor for the frame the mechanism sits in. |
| Load-case recorder | Log peak joint force and speed during a run, so a linkage is tuned against numbers instead of eyeball. |
| Two-point measurement tool | Click two parts to read distance, angle, and resulting lever arm without arithmetic. |
| CSV export of the sweep | Turns a bench result into something a customer can paste into their own report. |
Later parked
- Belt and pulley mode, springs and dampers, and a cam profile generator.
- Flow overlay for the hydro benches: simple open-channel and penstock layout sketch.
- Accounts and saved projects if the benches ever go on sale as a subscription.
How the phase runs
- Every pass ships something usable and keeps the self-tests green. A bench that stops computing is worse than no bench.
- Nothing ships to the public store until it has been used on a real problem at least once.
- The binding constraint is usefulness, not features. If a bench goes a month without being opened, it gets simplified or cut.