The method.
What happens between a phone scan and a mesh your tools can manufacture from. No numbers here on purpose: the validation section says how accuracy is established, and the method is open to inspection.
Scan
A good scan is one continuous pass: both feet in frame, standing, ordinary indoor light, one slow arc with the phone. The scan runs in the browser and the product guides the person through it, so the protocol travels with the tool instead of with a trained operator.
Reconstruction
Multi-view reconstruction, in plain words: the scan becomes a dense reconstruction of the scene, the feet are segmented from it, and each foot is closed into a watertight mesh grounded on the support plane. Gaussian splatting is used for visualisation.
Measurement
Dimensions and curves are extracted from the mesh, not estimated from pictures. Every measurement is declared with its definition and its loading condition, so two scans can be compared without guessing what was measured.
Validation
Accuracy is established against traceable, calibrated reference artefacts with declared ground-truth uncertainty, using a fixed registration method on an ISO 20685 style protocol. An automated regression suite runs on every pipeline release, so a change that degrades accuracy cannot ship silently. The method is on the table for any customer to inspect.
Integration
Scanning embeds in a brand's own flow, in the browser. Results arrive as files and through an API. White label is the default posture: your customer sees your product.