Fungibot extrusion tool

Project notes

Resolve the CAD payload rather than stopping at Git LFS

The repository's small .3dm blobs are Git LFS pointers, not the actual geometry. The original auger and parking-post payloads were retrieved separately and matched to the pointer SHA256 values and sizes. A Rhino file reader decoded the 25.4 MB auger into sixty objects, including boundary representations, extrusions and instance references; the parking post contained five objects. These are actual source geometry objects rather than a photograph or unexamined filename. [5] [6]

This does not establish a complete resolved tool assembly, fabrication tolerances, printable parts or fit with a specific Jubilee coupling. Inspect the instance references and any external component bodies separately: the geometry-type counts do not establish whether purchased-component bodies are present or identify their provenance. The separate plunger file's pointer identifies a much larger payload that was not retrieved or decoded in this review. Do not treat the auger inspection as validation of the plunger variant. [3] [5] [6]

The documentation leaves central build work unfinished

The README says fabrication settings and assembly instructions will be available later. Its BOM, milling, printing, assembly and operating sections are unfinished headings rather than a complete procedure. A maker must therefore resolve the selected variant's reservoir, printhead, motor, coupling, fabrication and controller configuration before procurement. No current complete build cost or matched shopping list was established. [1]

The same limitation applies to firmware provisioning, Z calibration, mixture selection and purging. The repository contains experimental platform modifications, but this bounded entry does not establish a verified end-to-end tool setup or extrusion protocol. A parent motion platform and an actual tool interface are separate requirements; available CAD does not commission them. [1]

Use the design within its evidenced boundary

At reviewed revision b81862f773de77e3ab48b0c557a2e48cc42bcce1, start with CADs/fungibot_auger.3dm, resolving its LFS payload before inspection. The recorded route used rhino3dm 8.35.0 File3dm.Read; use that source context when inspecting the geometry and unresolved assembly dependencies. The plunger remains a separate uninspected variant. The auger payload can support a concrete design investigation even though the complete build route remains unestablished. This is narrower than a promise that the tool can presently be reproduced from the README alone. [1] [5]

No project-wide reuse grant was identified in the inspected tree and documentation. Public geometry is not an unrestricted manufacturing or redistribution permission, and vendor models retain separate rights. No native assembly-fit check, fabrication, firmware installation, tool connection, extrusion, material preparation, biological outcome or performance test was performed. [1] [5] [6]