Diatech Make

List the names and interface tables this compiler accepts: op kinds (stone settings included — <setting type='prong'> is the prong_setting op kind), distribute modes, curve shapes, profiles, stdlib solids and components, gem cuts, expression functions, planes, tones, export formats. Check a name here before writing it; unknown ops and params are did-you-mean errors. The heavy per-field tables come only when named in `section` — param_specs (each op's params: type, default, hint), tag_attrs, attr_options (each attribute's values), gem_size_presets — narrowed by `kind`. Contextual child parameters (edge picks, prong overrides) are in diascript_docs, not tag_attrs.

diascript_catalog

Statically check whether two DiaScript sources are equivalent: after parse and resolve, every $var is replaced by its value, every constant expression folded and the commutative operands put in one order (+ and * in expressions; a + b and b + a, a - b - c and a - c - b in a <bool>), then the nodes are compared by content, so renamed ids do not matter — no geometry is built (milliseconds, no CAD kernel). Use it after reparameterizing a design (literals lifted into <var>s or component params whose defaults keep the old values): equivalent means both build the same solids and show them the same way (hidden=, tones). A gem's pavilion_z / crown_z fold to numbers, and a literal written to 4+ decimals matches the formula it rounds (8.035256 for 9.475 * sin(58)): such nodes are listed in rounded and still count as equivalent. Returns equivalent, renamed pairs, rounded, and changed / added / removed node ids — a changed node is where its own inputs differ, so it names the value that moved. Not equivalent does not prove the geometry differs (a default written out, a parameter added inside a component a <repeat> template expands): render both to compare those.

diascript_equivalence

Fetch one example by name (from diascript_examples): a bundled file, or an organization example whose name is org:<id>. Returns its full commented DiaScript source plus, by default, a server render of what it builds, so you can see the design you are about to copy. An organization example is readable only by that organization; anyone else gets the same not-found as a missing file. Pass render=false when you only need the text. A long source comes in parts of about 20 000 characters (part 1 says how many and carries the render); pass `part` for the rest. Engine overrides are example-specific; read diascript_docs(topic='booleans') before copying them into a new design.

diascript_example

Inspect named nodes, including consumed cutters and intermediate results. Returns representation (brep/mesh/mixed), triangle topology, boundary and non-manifold edges, winding errors, every connected shell counted (tiny fragments included), and up to eight shell bounds/volumes and problem-edge locations in CAD millimetres. Use after a cut or union: watertight alone does not mean one connected casting. Exact bodies are tessellated for this check; it does not prove absence of self-intersections, stone retention, or manufacturing clearance. ok means inspection completed, not that the geometry passed. Default quality is export; draft checks the coarse preview. Read diascript_docs(topic='verify').

diascript_inspect

Rewrite spellings the language has retired into their current equivalents (same geometry). Use it when diascript_validate rejects an attribute or value in an older design. Returns the rewritten source and a note per change or per spot that needs a hand edit; formatting and comments are kept.

diascript_migrate

Price a design from the signed-in account's Studio price book, as the editor's Report panel does. Weighs it like diascript_report (one server compile; `vars` apply), then prices the `alloy` weight (default the <design metal=> alloy; any report alloy id) at today's metal spot and each stone row at the book's per-carat rate for its type, cut, largest girdle dimension and the `color`, `clarity` and `make` grades (blank: DE, IF-VVS1, EX). Returns each line's rate and amount (null where no rate matched), total and complete (every line priced). A design with errors is not priced; its errors come back instead, as do Studio's refusals.

diascript_price

Publish a finished design to a link and give the user its `url` (the Review page; `showcase_url` is the render-only page anyone with the link can open or embed). Without design_id it creates a new design you own, and needs a name. For every later change pass that design_id: it publishes a new version and the link the user already has shows it. Before changing a published design, read its latest source with diascript_design: the user may have edited it in the editor since. Every version is kept; the same text again changes nothing (changed=false).

diascript_publish

Read the DiaScript language reference. Call with no arguments first: a one-page primer (the design model, conventions, a complete first design, the workflow) and the map of topics. Then pass `topic` — a topic name from the map ('sweeps', 'settings', 'head', 'repeat'), a tag ('<gem>'), or a heading's words ('engine selection', 'reusing a cut boundary') — for that page or section, each sized to read in one reply; a page ends with its related topics and the bundled examples that show it (diascript_example). `query` keyword-searches every page. A reply longer than about 20 000 characters comes in parts; `part` fetches the rest.

diascript_docs

Read a published design by design_id: its latest source (or `version`'s), its links and its version history, newest first. Read it before changing a published design, since the user may have edited it in the editor, then publish the change with diascript_publish and the same design_id. Without design_id, lists the designs you own or that are shared with you.

diascript_design

Render a design to look at it after every change. Compiles on a shared server and returns a shaded PNG per view plus a JSON summary: bounds_mm (renders are auto-framed; this is the real size), metal volume, grams and pieces, stones, errors and warnings. checks=true adds the design rules (min wall, stone overlap, melee sizes, stones in the finger bore). A design that fails to compile returns its diagnostics instead.

diascript_render