# Engrove Tools full public corpus ## Hello Example A deliberately small static example that documents the repository tool-folder convention and displays a browser-local greeting when the user presses a button. Canonical URL: https://tools.engroveaudio.com/tools/example-hello/ Updated: 2026-07-11 Capabilities: - Show the minimum static HTML structure expected for a repository tool. - Display a browser-local greeting containing the user's local date and time after a button press. Inputs: - button_action (user interface action, required): A user click on the Say hello button. Outputs: - greeting_text (text): A greeting rendered in the page with the browser's local date and time. When to use: - Use it as a minimal reference when creating a new static tool folder. - Use it to verify that the hub can publish and launch a simple no-build HTML tool. When not to use: - Do not treat it as a production engineering calculator or data-processing utility. - Do not use the displayed browser time as an authoritative time source. Limitations: - The page is an example rather than an engineering application. - The displayed date and time depend on the user's browser and device settings. Privacy: - Processing: local - Stores application user data on server: false - Requires account: false - Requires OAuth: false May claim: - The page demonstrates a static tool folder with an index.html entry file. - The greeting is generated locally in the browser after a user action. Negative claim boundaries: - No public backend API is provided. - No account, registration, or OAuth flow is required. Must not claim: - Do not claim authoritative timekeeping. - Do not claim engineering calculation capability. Evidence: - Hello Example source directory: https://github.com/Engrove/tools/tree/main/tools/example-hello Related tools: --- ## Engrove Manual Trace A desktop-focused, browser-local engineering trace editor for importing reference images or SVG files, detecting SVG geometry, manually refining contours, assigning technical metadata and relations, calibrating measurements, and exporting paired JSON, SVG or resumable Engrove project packages. Canonical URL: https://tools.engroveaudio.com/tools/manual-trace/ Updated: 2026-07-11 Capabilities: - Import raster reference images by file selection, drag and drop, or clipboard paste. - Import SVG files, sanitize active content, detect filled or stroked geometry, preview candidates, and create editable polyline or Bezier traces. - Create and edit paths, polylines, lines, measurements, origins, stations, rectangles, circles, semantic zones, and ignore masks. - Assign names, roles, feature kinds, descriptions, semantic metadata, and explicit reference relations to traced objects. - Calibrate pixel measurements against a real length and preserve the engineering coordinate-frame definition. - Save and reopen resumable Engrove project packages containing geometry, application state, source image data, SVG trace provenance, and panel layout settings. - Export paired JSON and SVG representations with stable object IDs, geometry summaries, source bindings, and 64-point sampled polylines. - Store calibrated top, side and front views and export a contract-validated multi-view Engrove trace project package for downstream 3D reconstruction. Inputs: - reference_image (raster image file or clipboard image): A browser-supported raster image used as the visual tracing reference. - source_svg (SVG file): An SVG source whose supported geometry can be sanitized, detected and converted to editable trace objects. - trace_json_or_project (JSON or .engrove-trace file): Previously exported trace data or a complete resumable project package. - operator_geometry_and_metadata (pointer, keyboard and form input, required): Operator-created geometry, calibration, coordinate-frame choices, metadata and relations. Outputs: - trace_json (JSON file or clipboard text): Structured trace geometry, engineering frame, metadata, relations, provenance and optional embedded image data. - bound_svg (SVG file): Visual vector export whose groups retain stable JSON object identifiers and JSON paths. - engrove_trace_project (.engrove-trace JSON package): Resumable browser project containing workspace state, geometry, source data and project metadata. - engrove_trace_project_package (.engrove-trace-project ZIP package): Contract-validated multi-view package holding one shared object, per-view calibrated geometry and stations, a SHA-256 file manifest, and the complete workspace retained as sidecars. When to use: - Use it to digitize a technical silhouette or reference drawing before downstream CAD or AI-assisted geometric interpretation. - Use it when geometry needs explicit object IDs, stations, datums, semantic zones, descriptions and reference relations rather than only a visual vector path. - Use it to refine supported SVG geometry while retaining source provenance and paired JSON/SVG bindings. - Use it on a desktop PC where a large canvas, mouse input and resizable tool and inspector panels are available. When not to use: - Do not treat traced output as dimensionally valid until scale, source projection, datum placement and operator review have been controlled. - Do not use it as a general-purpose CAD solid modeller, automatic manufacturing-tolerance system or metrology certification tool. - Do not rely on it to reconstruct unsupported SVG text, raster images, external styles, use elements or arbitrary embedded content. - Do not use the application as a mobile-first tracing interface. Limitations: - The application is designed and verified for desktop-class PC browsers; mobile layouts and touch-only workflows are outside the supported target. - SVG auto detection supports path, polygon, polyline, rect, circle, ellipse and line geometry after security sanitization; unsupported and active SVG content is removed. - Bezier smoothing, simplification and sampled polylines are geometric approximations and can deviate from the source contour. - Physical scale remains unknown until the operator defines and calibrates a reference measurement. - Projects are saved by explicit download and are not automatically synchronized or stored by an application backend. - Clipboard access, downloads and local file behavior depend on browser permissions and policy. - The output is not automatically CAD truth, metrological truth, manufacturing-toleranced geometry or mechanically verified design data. Privacy: - Processing: local browser processing; production page analytics are loaded only under the repository-wide production-host policy - Stores application user data on server: false - Requires account: false - Requires OAuth: false May claim: - The application imports browser-supported raster images and supported SVG geometry for local tracing and editing. - The application can save resumable Engrove trace project packages and export paired JSON and SVG files. - Exported trace objects retain stable identifiers, semantic metadata, source provenance and JSON-to-SVG bindings where implemented by the application. - Imported SVG active elements, external links and non-fragment URL references are removed before detection. - Application project data is processed locally and is not stored by an application backend. Negative claim boundaries: - No public backend API, server-side project store, account system or OAuth flow is provided. - No automatic claim of physical scale, CAD accuracy, manufacturing tolerance or metrological certification is made. - No mobile-first or touch-only workflow is supported as a product target. - Production-host usage analytics are separate from application project storage and follow the repository-wide analytics policy. Must not claim: - Do not claim automatic sub-pixel or metrology-grade accuracy. - Do not claim that generated contours are production-ready CAD without independent verification. - Do not claim complete SVG specification support. - Do not claim server synchronization, cloud backup or collaborative editing. - Do not claim that sanitization makes arbitrary untrusted files risk-free. Evidence: - Manual Trace source directory: https://github.com/Engrove/tools/tree/main/tools/manual-trace - Manual Trace functional documentation: https://github.com/Engrove/tools/blob/main/tools/manual-trace/README.md Related tools: --- ## Engrove Tonearm Profile Designer A PC-only, browser-local tonearm engineering application that opens with an empty session, imports calibrated JSON, Engrove project packages and paired SVG exports from Engrove Manual Trace, constructs a deterministic centerline-and-ring 3D loft, and preserves the TD053F parametric, Freeform, physics, solver, AI handoff, session, report, PNG and STL workflows. Canonical URL: https://tools.engroveaudio.com/tools/tonearm-profile-designer/ Updated: 2026-07-11 Capabilities: - Start with an empty workspace and create geometry only after an explicit import, session open or new-parametric action. - Import multiple Engrove Manual Trace JSON, .engrove-trace, .engrove-project and paired SVG files with per-file plane classification and provenance. - Import a contract-validated multi-view .engrove-trace-project package whose declared view types and engineering axes drive plane assignment directly. - Construct a deterministic Freeform centerline-and-ring loft from calibrated orthographic top and side silhouette bounds and Manual Trace station data. - Preserve TD053F parametric Cobra and classic geometry controls, Freeform AI workbench, cartridge picker, solver, LT mechanism preview and physical analysis. - Save and reopen complete sessions and export STL, Onshape sidecar JSON, 3D PNG, AI Vibe JSON and technical Markdown reports. - Scale a trace-derived casting pattern's cross-sections by a chosen percentage while keeping the traced length, and record the applied allowance. - Divide a freeform pattern across its length into two closed halves with an optional clearance, for printers whose build volume is shorter than the arm. - Add a keyed registration boss and matching socket to the split faces so the printed halves rejoin in a single orientation, sized from the cut section and refused when the pin would breach the wall. - Check whether a pattern can be withdrawn from a two-part mould along a chosen pull axis from the export panel, and report the parting line and near-vertical surface area. - Record the pattern allowance, split position, section exponent, traced and lofted lengths, recovered end stations and mould-release verdict in the technical report. - Choose the cross-section exponent used when two orthographic silhouettes are converted to sections, since the silhouettes fix width and height but not corner fullness. - Run entirely in the desktop browser without uploading operator files to an application server. Inputs: - manual_trace_files (Engrove Manual Trace JSON, project package or paired SVG files): Calibrated orthographic trace artifacts used as deterministic geometry input. - tonearm_session (Tonearm Designer session JSON): A previously saved complete application session. - operator_parameters (desktop form controls and validated AI response JSON): Explicit design, material, cartridge, solver and export settings. Outputs: - tonearm_session (JSON): A resumable application session including active geometry and Manual Trace import provenance. - tonearm_mesh (binary or ASCII STL): The explicitly selected active parametric or accepted Freeform mesh. - pattern_split_halves (binary or ASCII STL pair): Two closed halves of a freeform casting pattern cut across its length, each checked for closure before it is written. - technical_report (Markdown): A runtime snapshot of controls, analysis, source audit and stated limitations. - visual_reference (PNG): An 800 by 600 pixel image of the active 3D model. - ai_and_onshape_sidecars (JSON): Structured AI Vibe and Onshape handoff metadata for the active design. When to use: - Use after producing calibrated top and side silhouettes in Engrove Manual Trace. - Use to refine and compare tonearm profile geometry on a desktop workstation. - Use when browser-local STL, session, image or technical-report output is needed. When not to use: - Do not use an uncalibrated or axis-ambiguous trace as dimensional manufacturing truth. - Do not treat the analytical stiffness, resonance or manufacturability proxies as FEA, metrology or laboratory certification. - Do not use the tool as a replacement for final B-rep CAD cleanup, tolerancing or production validation. Limitations: - A trace-derived loft requires at least one valid top-plane and one valid side-plane Manual Trace artifact with an origin, millimetre scale and usable contour geometry. - Top and side silhouettes constrain station width, height and center position; unmeasured cross-section shape between those bounds remains a deterministic modelling assumption. - The imported Freeform kernel clamps values to its documented geometric limits and blocks inputs that would require silent dimensional loss. - Three.js rendering and browser downloads require a current desktop browser with WebGL and local download permission. - STL is a mesh reference output, not a parametric STEP or manufacturing-ready B-rep model. Privacy: - Processing: local - Stores application user data on server: false - Requires account: false - Requires OAuth: false May claim: - The tool starts with no active or rendered 3D design. - Supported Manual Trace files are parsed and converted locally in the browser after explicit operator action. - Accepted trace-derived geometry is bound to the existing Freeform render, session, report and export source path. - The original TD053F runtime modules and portable acceptance harnesses remain included in the source repository. Negative claim boundaries: - A source-level or local browser check is not proof of Cloudflare deployment or production availability. - Deterministic trace conversion does not establish that the source image, calibration or operator contour is correct. - A closed STL mesh and analytical proxy results do not prove manufacturability, structural performance or audio performance. - The two-part mould release check is a ray-sampled geometric test on the exported pattern mesh; it is not a mould-flow, tooling or process simulation. - A cross-section exponent chosen by the operator is an assumption about section shape, not a measurement derived from the traced silhouettes. Must not claim: - Do not claim metrology-grade dimensional accuracy without independently verified calibration and source imagery. - Do not claim CAD, FEA, Onshape, manufacturing or acoustic validation from this browser application alone. - Do not claim that paired SVG geometry overrides the Manual Trace JSON source-of-truth contract. Evidence: - Tonearm Profile Designer source: https://github.com/Engrove/tools/tree/main/tools/tonearm-profile-designer - Engrove Manual Trace source: https://github.com/Engrove/tools/tree/main/tools/manual-trace - Engrove Tools repository documentation: https://github.com/Engrove/tools Related tools: - manual-trace --- ## Engrove Trace to Plug A PC-only, browser-local workflow that takes a contract-validated Engrove Manual Trace project package and walks it through interpretation, casting allowance, two-part mould release checking and printable export in five explicit steps. Geometry comes only from traced views; the tool carries no parametric tonearm architecture, and every operator assumption is recorded with the exported pattern. Canonical URL: https://tools.engroveaudio.com/tools/trace-to-plug/ Updated: 2026-07-26 Capabilities: - Import a contract-validated .engrove-trace-project package and build a pattern from the traced views alone. - Choose the cross-section fullness used where two orthographic silhouettes leave the section shape undetermined, and record the choice with the pattern. - Apply a casting allowance that scales every section by a percentage while keeping the traced length unchanged. - Check whether the pattern can be withdrawn from a two-part mould along a chosen pull axis, and report the parting line. - Split the pattern across its length into two closed halves with a keyed registration boss and socket for printers with a short build volume. - Export the pattern or its halves as STL, together with a Markdown record of every operator decision that shaped it. - Prepare an AI prompt carrying the full pattern context and apply a pasted response only after it validates against the response contract. - Run entirely in the desktop browser without uploading operator files to an application server. Inputs: - trace_project_package (.engrove-trace-project package, required): A contract-validated multi-view Manual Trace package carrying calibrated top and side views. - pattern_parameters (desktop form controls): Section fullness, casting allowance, split position and registration pin settings. - ai_response (JSON pasted by the operator): A pattern adjustment proposal validated against the response contract before it may change geometry. Outputs: - pattern_mesh (binary or ASCII STL): The closed casting pattern as it will be printed, allowance included. - pattern_split_halves (binary or ASCII STL pair): Two closed halves with a keyed boss and socket, each checked for closure before it is written. - pattern_record (Markdown): The traced source, every operator decision, the mould release verdict and the stated limitations. - ai_prompt (text): A prompt carrying the current pattern context and the strict response contract. When to use: - Use to turn calibrated Manual Trace views into a pattern for a two-part mould. - Use to check whether a shape will release from a mould before printing it. - Use to divide a long pattern into printable halves that rejoin in one orientation. When not to use: - Do not use it to design a tonearm from parameters; it builds only from traced views. - Do not treat the mould release check as a tooling, mould-flow or process simulation. - Do not use an uncalibrated or axis-ambiguous trace as dimensional manufacturing truth. Limitations: - A pattern requires one top-plane and one side-plane view with a millimetre scale, an engineering origin and usable contour geometry. - Two orthographic silhouettes fix each section's width and height but not its corner fullness; that remains an operator assumption recorded with the pattern. - The mould release check is sampled on the exported mesh at the exported tessellation, so a coarser mesh is a different solid than a finer one. - STL is a mesh reference output, not a parametric STEP or manufacturing-ready B-rep model. - Three.js rendering and browser downloads require a current desktop browser with WebGL and local download permission. Privacy: - Processing: local - Stores application user data on server: false - Requires account: false - Requires OAuth: false May claim: - The tool starts empty and builds geometry only after an explicit package import. - Pattern geometry is derived from the traced views and the operator's recorded decisions, with no parametric fallback. - Imported packages and pasted AI responses are validated before they may change geometry. - Files are processed locally in the browser and are not uploaded to an application backend. Negative claim boundaries: - A source-level or local browser check is not proof of Cloudflare deployment or production availability. - A closed STL and a release verdict do not prove that a mould will produce an acceptable part. - The two-part mould release check is a ray-sampled geometric test on the exported mesh; it is not a mould-flow, tooling or process simulation. - A cross-section fullness chosen by the operator is an assumption about section shape, not a measurement derived from the traced silhouettes. Must not claim: - Do not claim metrology-grade dimensional accuracy without independently verified calibration and source imagery. - Do not claim manufacturing, CAD or FEA validation from this browser application alone. - Do not claim that an AI response was applied without passing the response contract. Evidence: - Trace to Plug source: https://github.com/Engrove/tools/tree/main/tools/trace-to-plug - Pattern pipeline, mesh and record regressions: https://github.com/Engrove/tools/tree/main/tools/trace-to-plug/test - Chromium workflow smoke against the built runtime: https://github.com/Engrove/tools/blob/main/tools/trace-to-plug/test/workflow-browser-smoke.mjs - Engrove Manual Trace source: https://github.com/Engrove/tools/tree/main/tools/manual-trace - Engrove Tools repository documentation: https://github.com/Engrove/tools Related tools: - manual-trace - tonearm-profile-designer Primary public site: Engrove Audio Tools — https://engroveaudio.com