# Next phone ## What this builds A small studio where a person kits a handset: size, corner radius, camera bump, material. Each control changes a documented mesh parameter. A design can be serialised to a state string and a URL under `share_prefix`. The object is a fictional device, not a branded flagship. A fixture design must render to a golden image and round-trip through the state string. Read `spekkr.inputs.json` first. `title` labels the stage. `body` is the starting family. `camera_light` and `annotations` change the render. `share_prefix` is used when minting a URL. ## Out of scope - A real manufacturer's name, logo, or CAD in the files. - A production cost model or a factory export in this version. - Network, accounts, or a public gallery in the checks. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Controls and mesh - Parameters are listed in `design.md`: width, height, thickness, radius, bump count, bump size, material. - Each control, moved to a stated value, changes only the documented mesh measure, within 0.05 mm. - An illegal combination (radius more than half the smaller side, bump count 3 on `fold`) is refused with a message. Accept when: the parameter fixtures in `design.md` match the mesh measures, and the two illegal cases are refused. ### R2. Fixture design and share - `fixtures/phone-alpha.json` is a complete state. It renders to a golden (`fixture-design`) within the tolerance. - The state string is a compact query, documented in `design.md`. Loading the string restores every parameter. - The share URL is `share_prefix` plus the state string, and must be parsed back to the same state. Accept when: the fixture renders to the golden, and a round-trip of its URL restores the same JSON (key order excepted). ### R3. Files - One command runs the mesh, refuse, render, and URL tests, and writes the four screenshots. No network. Accept when: the command passes for both body families. ### R4. Inputs - The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key. Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check. ## Verification Each control changes a documented mesh measure, checked in millimetres. Illegal combinations are refused. A fixture design renders to a golden image and round-trips through a shareable state URL. No brand assets and no network. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to kit a device, how to share a state, and how to run the checks.