10 installed / 7 staged modules
One machine.
Understand every part.
The 3D canvas matches the installed Bevy configuration. Compare every authored module’s build route, likely source and prototype price below; staged concepts remain documented without appearing as fitted hardware.
| Part | Build route | Prototype price | Likely source |
|---|
Stock configuration / OT-01S-EU-NL
The BOM says
what is required.
Quantities belong here. Candidate sourcing links never override the specification, and concept items remain visibly unresolved.
| Item | Quantity | State | Specification |
|---|
EU / Netherlands
Source to spec.
Measure donors.
Supplier links are discovery aids. Exact quantities come from the BOM; donor listings without drawings or ratings stay candidates.
Basic instructions / stable IDs
Build the same
design we test.
Every action names canonical parts and the connection it creates. These are exploratory instructions, not released fabrication data.
Fasteners / materials / welding
Standards before
brand names.
Standards describe the required item. Supplier pages are replaceable links, and a reference here does not claim certification.
Design philosophy
The tractor is managed with code.
Geometry, interfaces, sourcing assumptions and validation rules live together. A change is reviewable. A cost assumption is traceable. A module keeps the same ID even when its donor changes.
Design/design/
├── baseline.json machine configuration
├── assembly.json geometry + declared joint limits
├── catalog.json BOM + sourcing standards
└── build.json ordered instructions