# Build Async video You were asked to build the spec `dwrtz/async-video`, version 0.1.2, from Spekkr. Record your screen and camera in the browser, share a link, get comments and emoji pinned to the moment. Cloudflare Workers, R2 and D1. 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/async-video/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 `async-video`, inside the project you are working in. ```sh mkdir -p async-video && curl -fsSL https://spekkr.com/dwrtz/async-video/bundle.tar.gz | tar -xz -C async-video ``` 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/async-video/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/async-video` and the person's choices. ## 2. Record the person's choices Write `async-video/spekkr.inputs.json`. With every default it is: ```json { "spec": "dwrtz/async-video", "version": "0.1.2", "inputs": { "accent_color": "#0d9488", "allowed_emails": "", "app_name": "Async Video" } } ``` 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. - `allowed_emails`, Who may have an account: 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 `async-video`. 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–R17 with acceptance checks: allowlisted accounts, recorder with camera bubble, review before saving with real cuts made in the browser (trim, removed section, mute; only the kept part is uploaded), MP4-first recording, multipart upload, share page and player that plays on phones, re-cutting a saved video, chapters, timestamped comments, reactions, views, library, limits, phones, deploy. - `design.md`: Stack, Cloudflare config and deploy steps, data model and migrations (including the two-step live upgrade to real cuts), R2 layout, recording pipeline, WebM header repair, review step, in-browser cutting with WebCodecs and a real-time fallback, the replace API and time remapping, upload protocol, API, player details, screens and look, test setup including ffprobe and timecode checks. - `tasks.md`: Build tasks in order, each with a check, plus testing notes for fake media devices and for proving cuts. - `research.md`: What the design was modelled on, how it was studied, where it differs (including why cuts are made in the browser), the mobile playback investigation, and how each version was checked.