WORKSPACE

New Jewelry Design

Capture the 8 structured inputs. They become a design brief, not a prompt.

01 Product

Jewelry type

Category

02 Metal

Alloy

Finish

750/1000 · 15.8 g/cm³ · casting difficulty 3/5

03 Gemstone

Type

Shape

Carat

Colour

Clarity

Cut

Add accent / melee stones

Accent type

Count

Size (mm)

04 Style DNA

Era

Form language

Brand character

Symmetry — 0.85

Detail level — 0.55

05 Budget

Target band

The budget becomes a design constraint: the cost engine checks the result against it and reports utilisation.

06 Target customer

Age

Income level

Market

Occasion

07 Size specifications

Ring size

Setting type

Band width (mm)

Band thickness (mm)

Setting height (mm)

Inner diameter 17.3 mm — derived from the ring size, used for weight and melee capacity.

08 Reference images

Design intent

Creating this design persists the brief, then runs all 8 Jewelry MCP tools. DFM, cost and CAD are produced by the engines, not by this form.

What happens next

01 · Brief is validated and persisted as a versioned design object

02 · Agent plans the run as a DAG and calls 8 Jewelry MCP tools

03 · Style DNA and stone analysis run first, in parallel

04 · Setting and metal structure derive from the stone results

05 · DFM runs 7 check families; blocking errors gate CAD export

06 · Cost is calculated from live provider rates — or reported unavailable

Constraint

ManufacturableBudget-boundedTraceable

The brief becomes a structured design object before any tool runs. That is what keeps DFM, BOM and CAD deterministic instead of conversational.