The build-a-machine concept jam

01

Why this challenge

Every real machine embodies a decision about what mattered most to its designer. A gantry built for stiffness fights vibration at the cost of mass and therefore speed; a lightweight frame chases acceleration at the cost of ringing artifacts on tall prints. Firmware-level documentation of resonance compensation makes this trade-off concrete, describing how a machine's own frame and belt dynamics show up as visible defects in a finished print, and how compensating in software only goes so far against a genuinely under-built frame ¹.

Naming the constraint before sketching the machine is the actual discipline this jam teaches. It is easy to draw an appealing motion system; it is harder to say, out loud, envelope over speed, or cost over precision, and then let every subsequent decision answer to that choice. Firmware introductions that describe what a controller actually manages, motion, heating, and safety interlocks, are a useful reference for what a concept needs to account for even at sketch stage ².

02

The brief

Sketch an original printer or motion-system concept, any process family, cartesian, CoreXY, delta, rotary, or something new, and state the single governing constraint it optimizes for: stiffness, speed, build envelope, or cost. A CAD model, a hand drawing with dimensions and reasoning noted, or a cardboard-and-skewer mockup of the motion geometry are all valid formats; the point is showing how the constraint shaped frame layout, motion type, and toolhead mass, not building a working machine.

Explain your reasoning in a short caption: why this constraint over the others, and what you gave up to get it. If you reference a standard test geometry to describe how you would validate the concept's capability, national test-artifact programs document the kind of feature set, small features, overhangs, and thin walls, that a credible validation print would need to check ³. Use standard motion-system terms so readers unfamiliar with your specific layout can still follow the trade-off you made.

• One governing constraint named explicitly: stiffness, speed, envelope, or cost
• CAD, dimensioned drawing, or cardboard mockup, concept only
• Frame, motion type, and toolhead choices traced back to that constraint
• Standard motion-system vocabulary used throughout
• No mains-voltage wiring, laser modules, or chemical systems built or solicited

03

Safety and rights boundaries

This jam solicits concepts, not hardware. Do not build, wire, or power any mains-voltage electronics, laser diodes or modules, or chemical delivery or vat systems as part of an entry, and do not post build instructions for any of those as though they were being requested here; a cardboard mockup, drawing, or CAD file carries none of those risks and is exactly what this challenge asks for. If your caption references firmware concepts like resonance compensation, treat that as vocabulary for describing the idea, not as an instruction to wire a live controller.

Original concepts only: describe your own motion-system idea rather than reproducing a commercial machine's proprietary layout as your own design. If you share sketches or CAD files, license them clearly so others know what they may build from them; Creative Commons Attribution 4.0 is a common, permissive choice requiring only credit back to you ⁴. Credit any specific existing machine your concept deliberately riffs on rather than presenting a variation as wholly original.

04

How to participate

Post your concept publicly on Instagram or X and tag @print.mason or @printmasons with the hashtag #PrintMasonChallenge, or email sketches, CAD screenshots, or mockup photos and your reasoning caption to right.just.right@gmail.com. There are no on-site accounts, uploads, or comments; the jam lives on your own platforms and by email, gathered by the shared hashtag. Include your named constraint and the trade-off you accepted in the caption itself, not only in the image.

There is no deadline and no prize, and revisiting a concept with a different governing constraint, the same frame idea optimized for cost instead of stiffness, for instance, is a welcome second entry. Beginners are as welcome as anyone with mechanical background; a clearly reasoned cardboard mockup that names its trade-off honestly outperforms an elaborate CAD file with no stated constraint.

05

What a strong entry shows

A strong entry states its constraint in one clear sentence and then makes every visible design choice answer to it. A stiffness-optimized concept shows a heavier frame and explains why; a cost-optimized concept shows where corners were deliberately cut and what was protected instead. The reasoning caption matters as much as the sketch, because the jam is testing trade-off thinking, not drafting polish.

The quiet test is whether a reader could predict the concept's weaknesses from its stated constraint alone. If stiffness was the priority, the reader should already expect a slower top speed before being told; if cost was the priority, they should expect a smaller envelope or coarser precision. An entry that owns its trade-offs honestly, rather than implying it optimized everything at once, is the one worth studying.