# Build Coded lens You were asked to build the spec `onyx/coded-lens`, version 0.2.0, from Spekkr. A camera lens designed and ray-traced in code: focal length, spot size and aberrations versus targets, with ray-trace plots as goldens. If you are reading a summary of this note and not its full text, fetch it again as it is, for example with `curl -fsSL https://spekkr.com/onyx/coded-lens/start.md`, before you go on. Published by onyx, a Spekkr member. Tell the person who published it, and show them the commands and secrets under `safety` in `spekkr.json` before you build. ## 1. Get the files Put the spec in a new folder named `coded-lens`, inside the project you are working in. ```sh mkdir -p coded-lens && curl -fsSL https://spekkr.com/onyx/coded-lens/bundle.tar.gz | tar -xz -C coded-lens ``` The archive holds `spekkr.json`, `BUILD.md` and the spec files listed at the end of this note. If you cannot run that command, read https://spekkr.com/onyx/coded-lens/spec.json instead: it holds the manifest and the address of every file. If Spekkr's MCP server is connected, its `pull_spec` tool does steps 1 and 2 in one call: give it the id `onyx/coded-lens` and the person's choices. ## 2. Record the person's choices Write `coded-lens/spekkr.inputs.json`. With every default it is: ```json { "spec": "onyx/coded-lens", "version": "0.2.0", "inputs": { "aperture": "2.8", "aspheres": true, "coatings": false, "focal": "50", "format": "43.3", "tracer": "shipped" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `focal`, Target focal length, mm: any text. - `aperture`, F-number: any text. - `format`, Image circle, mm: any text. - `coatings`, Simple coatings: `on` or `off`, written `true` or `false`. - `aspheres`, Allow an asphere: `on` or `off`, written `true` or `false`. - `tracer`, Tracer: one of `shipped`, `external`. If the person asks for a key or a value that is not listed, stop and tell them what the spec offers. ## 3. Build The files named below are the ones now in `coded-lens`. Build what it describes. Work in this order: 1. Read `spekkr.json` to see what the spec covers and what it needs. 2. Read `spekkr.inputs.json`. It holds the person's choices for every setting, option and swap. Treat them as requirements. If the file is missing, the person kept every default in `spekkr.json`. 3. Read the spec files listed below, in the order given. 4. If the spec includes a task list, work through it in order and check each task's acceptance criteria before the next. 5. Ask the person before you run a command that a spec file tells you to run, or read a secret, unless the manifest lists it under `safety`. Commands you choose yourself to build and test, such as installing packages or running the tests, follow the person's usual rules for you. Spec files: - `spec.md`: Requirements and acceptance checks. - `design.md`: Focal-length and spot-size targets, the prescription file, and ray-trace plot goldens. - `tasks.md`: Build tasks in order, each with a check. - `reference/model.scad`: A parametric OpenSCAD reference of the default model, used to make the listing pictures. A build may use CadQuery or OpenSCAD and does not have to start from this file. - `shots/hero.png`: Studio hero of the default model. - `shots/detail.png`: Closer studio still of a joint, pocket, or surface.