u/FeverForest

1850 Nodes, 6761 Edges(353 Negative). Independently in a growing world..

Sleep time.

Contriver Guitars Foundation Series - Echo Six

Fresh off the bench, up there on my list of favourites so far. Maple board, maple neck, and crisp lines, definitely starting another one when time aligns.

Built in Hamilton, Ontario, Canada. 🇨🇦 

FINGERBOARD:
- 27.00” Scale Length
- Blistered Maple w/Black Underlay
- 11-20” Compound Radius
- Jescar 47095 Fretwire
- Semi-Hemi Ends
- Polyurethane

NECK:
- 3 Piece Maple+Sapele
- Flamed Black Walnut Front+Back Head
- Carbon Fibre Reinforcements
- Blistered Maple Logo Plate
- Bone Nut
- Luminlay Blue Side Dots 

BODY:
- Flamed Black Walnut Top
- Ash Body(3.0lbs/BF) 
- Matching Pickup Covers
- “Bound” Pickup Routes
- Matching Magnetic Back Plate
- Ebony+Chechen Retainer Block

ELECTRONICS: 
- Volume 550K CTS
- Tone 450K Alpha
- Barrel Output
- Bridge Pickup: 16K 
- Neck Pickup: 12k

HARDWARE: 
- Hipshot Fixed Bridge
- Hipshot Open-Gear Locking Tuners

FINISH:
- Rubio Monocoat
- Black Forest Wood co Ceramic

Weight: 7.5lbs

Tossed together this doodle last week, asking “what if I made a headstock using only the exciting primitive, arcs” part of a circle!!! But parametric so the computation runs deep.

Constraints and relationships, its scales out almost generatively.. though the options get exhausted quickly unless I change how that spiders web pulls.

*edit: Replace the AI with the coworker you can’t trust, reason over their boneheaded model structure, and correct it. Same story, this one is just scripted.

Fresh out of the Autodesk Submission gauntlet, Contriver Node Atlas.

Your Fusion design parametric dependencies, as an interactive node graph.

The browser is the table of contents.

The timeline is the construction log.

Node Atlas is the Utility Map, so you know what goes dark when you start digging.

Design and Make Marketplace trial available for Windows.

MacOS update deploying shortly.
—————

Hello! A project of mine has recently been deployed on the Autodesk Design and Make Marketplace.

For this demo I admittedly used Claude to run the sequence, demonstrating the difference between Form and Shape, or the Recipe and the Cake.

More programmatic, less human, but runs the test for a 60s clip, and maybe higher representation of structure will lead to less schloppity schlop and glumpity glup, glumping up the ponds where the humming fish hum.

The add-in is not AI powered, is read only. Connecting to an agent is your decision, outbound calls containing design IP should be considered cautiously.

Here we see Claude working across two MCPs.

The Fusion MCP creates the geometry.

The Node Atlas MCP reveals the model’s underlying structure. Its dependencies, parameters, relationships, and design intent, so you, a colleague or a new hire, can later understand how the model was built, not just what it looks like.

Claude generates a six-arm radial organizer using duplicated sketches and features.

Node Atlas then exposes the repeated geometry, dependencies, and lack of shared parametric control.

Claude restructures the model around a single seed feature, a circular pattern, and user parameters—reducing the timeline from 27 features to 8, while the Node Atlas graph shrinks from 33 nodes / 72 edges to 14 nodes / 27 edges.

Finally, a single parameter changes the design from 6 arms to 9, while the repaired structure remains unchanged and healthy.

This is the difference between generating a shape and understanding its form.

Together, Fusion MCP and Node Atlas MCP create a development loop for geometry and Fusion add-ins while preserving the human authority required to validate design decisions.

The bigger picture is, if the robot can understand, reason over, and correct structure, so can we. Probabilistic vs Deterministic, rented intelligence vs owned mechanisms.

A different lens.

Happy building!

Years of building parametric systems for instrument builders, I kept running into the same issue.

The challenge not creating the geometry, the challenge was understanding the structure tha produced it.

A fretboard isn’t a just collection of sketches and features, and a neck is not just a sequence of operations.

Each are living structures made from relationships that depend on one another.

When something breaks, or when you want to change the scale length, you’re not navigating a timeline. You’re navigating a constellation of consequences, often held in your head.

So I built something to make them visible.

The video shows it running on a real fretboard design. Nodes for parameters, sketches, features, and bodies. Click on a node, edit its parameter in place. Trace upstream and downstream, and package operations as Script Nodes, to become reusable units of design knowledge that transfer between documents.

It’s called Node Atlas.

Happy to answer any questions about how it works, or the thought process it took to build it.

Fun!

It fits, so it sits.

37” - 34.5”

Blue-Black Ceruse Finish. 😬 it’s a trickier one…

Wash coat, sand back, paint, wash coat, fill grain, seal seal seal, top coat.

Just trying to keep the grain open so the pores remain deep enough to fill with the accent colour.

Took the most recent one out for a walk with the Sony A7II.

Rather than dumping a spec sheet here, AMA, I’ve got some time today.

EDIT: I bumbled out a spec list. Still AMA

SPEC ⬇️⬇️

Scale Length: 654mm / 25.75”
Neck: 3-piece White Maple w/ Sapele Core
Fretboard: Figured Chechen
Body: Select Northern Ash
Top: Black Walnut
Finish: Rubio Monocoat
Construction: Bolt-on
Headstock: Foundation Series
Hardware: Hipshot Products
Pickups: Seymour Duncan Pegasus/Sentient

3 Way Toggle, 550k Volume w/1Meg Resister(350k), Master Series Parallel Switch.