Parameters, references and reusable functions¶
Expose dimensions that express engineering intent: channel width, material thickness, port diameter or feature count. Give each parameter a clear name, unit, valid range and description. Avoid making incidental preview settings the primary design controls.
Document inputs are typed. Features can use literal inputs or references, and reusable functions can encapsulate a repeated group of operations. Read DesignInput, Feature and FunctionDefinition before constructing their JSON.
Preserve meaning during edits¶
Keep stable feature and output IDs, document identity, units and parent revision. Use the edit design operation for typed edit requests and inspect the returned candidate. Reject unresolved references and incompatible input types before evaluation.
For a family of channel designs, for example, expose channel count, width and pitch separately. Add constraints that leave enough material between channels and keep the final channel inside the envelope. A UI group organizes parameters; it does not imply that all members change together.
Reuse deliberately¶
A reusable function should state its input types, coordinate convention and output meaning. Use explicit dimensional inputs and stable output names. Keep construction bodies distinct from physical outputs. Self-contained documents are required for the durable custom-geometry job path; external assets and arbitrary executable code are not accepted there.
For studies, record the baseline document and vary only the declared controls. Validate every candidate, retain failures with reasons, and compare designs under identical operating conditions. Study support and physical-model availability are discovered through the central API/MCP service.