# Build Whiteboard You were asked to build the spec `dwrtz/whiteboard`, version 0.1.1, from Spekkr. A hand-drawn whiteboard kept in your browser, with encrypted share links and live collaboration on Cloudflare Workers. 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/dwrtz/whiteboard/start.md`, before you go on. Published by dwrtz, 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 `whiteboard`, inside the project you are working in. ```sh mkdir -p whiteboard && curl -fsSL https://spekkr.com/dwrtz/whiteboard/bundle.tar.gz | tar -xz -C whiteboard ``` 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/dwrtz/whiteboard/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 `dwrtz/whiteboard` and the person's choices. ## 2. Record the person's choices Write `whiteboard/spekkr.inputs.json`. With every default it is: ```json { "spec": "dwrtz/whiteboard", "version": "0.1.1", "inputs": { "accent_color": "#4c6ef5", "app_name": "Whiteboard" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `app_name`, Product name: any text. - `accent_color`, Accent colour: any text. 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 `whiteboard`. 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 R1–R27 with acceptance checks: drawing tools, styles, files, library, export, the browser canvas, encrypted share links, live collaboration, limits, deploy. - `design.md`: Stack, Cloudflare config and deploy, browser and R2 storage, element model and file format, restore and ordering rules, rendering, encryption, live session protocol, API, limits, unit and end-to-end tests, screens, look. - `tasks.md`: Build tasks in order, each with a check. - `research.md`: Provenance only, not needed to build: sources, how the spec was checked, and where it differs from the app it was modelled on.