Bespoke

4 components in Capsules › Bespoke.

Capsule Info

Writes <gh file name>.json next to the .gh file with the info, the merged schema and the configurator schema. Double-click to edit the stored info (name, description, tags, unique id, date).

Nickname: Capsule Info · Tab: Capsules › Bespoke

Inputs

Name	Nickname	Type	Access	Default	Description
Enabled	Enabled	Boolean	item	true	Set to false to compute the JSON without writing the file.
Info (optional)	Info	Text	item	—	Optional info JSON: replaces the stored info record (double-click the component to edit that one).
Scheme (optional)	Scheme	Text	list	—	Scheme JSONs (from the readers’ Scheme outputs). Connect several: they are merged into one object.
Configurator Scheme (optional)	Configurator	Text	item	—	Configurator scheme JSON. Empty writes {}.
Path (optional)	Path	Text	item	—	Optional file path. Defaults to the .gh file’s folder and name with a .json extension.

Outputs

Name	Nickname	Type	Access	Description
JSON	JSON	Text	item	The design JSON.
Path	Path	Text	item	Path of the written file.

Capsule Input

The input of a Knowledge Capsule: outputs the design record that arrives from Compute (or from a wired test panel; an empty record otherwise). Wire it into the readers. Compute finds it by its name, RH_IN:100:GLOBAL, with no group needed.

Nickname: RH_IN:100:GLOBAL · Tab: Capsules › Bespoke · Parameter — a single output and no inputs: it carries one value into the definition

Capsule Mode

The computation mode of a Knowledge Capsule: RENDER (default) or MANUFACTURING, as the backend sends it (or a wired test panel). Wire it into the Computation Mode inputs and into Capsule Output. Compute finds it by its name, RH_IN:000:MODE, with no group needed.

Nickname: RH_IN:000:MODE · Tab: Capsules › Bespoke · Parameter — a single output and no inputs: it carries one value into the definition

Capsule Output

The outputs of a knowledge capsule from its Parts: GLB (Base64), TECH (technical chart JSON), RESOLVED (the values the engine used, from the schemes the parts carry) and SEMANTIC (the piece in words). It sits in its own RH_OUT group, created on placement, so Compute publishes the four.

Nickname: Capsule Output · Tab: Capsules › Bespoke

Inputs

Name	Nickname	Type	Access	Default	Description
Parts	Parts	Part	list	—	Parts of the jewel: the Parts outputs of the geometry components, or Part components. Parts with the same path are joined.
Semantic (optional)	Semantic	Text	list	—	The piece in words: the Semantic component’s output, or the components’ Semantic outputs straight in (joined with a space).
Design Type (optional)	Design Type	Text	item	RING	Design type written in the technical chart (RING, PENDANT, EARRING…).
Computation Mode (optional)	Computation Mode	Text	item	RENDER	RENDER (default) or MANUFACTURING: wire the Capsule Mode. In MANUFACTURING the STL of the metal parts comes out too.

Outputs

Name	Nickname	Type	Access	Description
GLB	GLB	Text	item	The piece as a GLB, Base64 encoded: one node per part, named after it.
TECH	TECH	Text	item	Technical chart JSON: metal volume and weight per part, gems per part, the parts manifest.
RESOLVED	RESOLVED	Text	item	Flat JSON of the values the engine used (<section>.<id>.<field>), from the schemes the parts carry.
SEMANTIC	SEMANTIC	Text	item	The piece in words.
STL	STL	Text	item	The metal parts as one binary STL, Base64 encoded; only in MANUFACTURING mode (empty otherwise).