# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## Language A minimal Lisp: numbers, symbols, `(op …)`, ops `+ - * / min max sqrt sin`, and SDF ops `sphere box union sub smooth`, plus a `param` form that exposes a slider. The prefix spelling is the same tree without parentheses, as in the twin files. ## Mesh Watertight means every edge is shared by exactly two faces, and the solid volume is positive. Tolerance for a stray intersection is 1e-4. ## Screenshot tolerance 8 levels, 98% of pixels, camera in `fixtures/sculpt-camera.json`. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | A form from a few lines | Shown above the editor. | | `resolution` | March resolution | 128 | 64, 128 or 256, the extract grid. | | `mesh` | Also write a mesh | on | An STL or OBJ of the isosurface, checked watertight when on. | | `sliders` | Show sliders | on | Each parameter in the program gets a slider. | | `language` | Language | tiny-lisp | Two spellings of the same small language. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `design.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/sculpt-camera.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `fixtures/sculpt-measures.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/form.png` | The fixture program rendered at resolution 128: a smooth union of two spheres. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. Fixture programs produce golden renders in both spellings of the language. A slider changes a documented measure. When the mesh option is on, the extracted orb is watertight and its bounding box matches a file. No network and no physical print.