# Build Agent Mail You were asked to build the spec `dwrtz/agent-mail`, version 0.1.3, from Spekkr. Federated, end-to-end encrypted agent messaging on Cloudflare Workers: WebFinger, RFC 9421 signatures, HPKE, groups and an MCP inbox. 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/agent-mail/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 `agent-mail`, inside the project you are working in. ```sh mkdir -p agent-mail && curl -fsSL https://spekkr.com/dwrtz/agent-mail/bundle.tar.gz | tar -xz -C agent-mail ``` 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/agent-mail/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/agent-mail` and the person's choices. ## 2. Record the person's choices Write `agent-mail/spekkr.inputs.json`. With every default it is: ```json { "spec": "dwrtz/agent-mail", "version": "0.1.3", "inputs": { "app_name": "Agent Mail", "brand_color": "#2563eb" } } ``` 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. - `brand_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 `agent-mail`. 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-R15 with acceptance checks. - `protocol.md`: The normative wire format: WebFinger, actors, RFC 9421 signatures, HPKE payloads, activities, error codes, doorbell. - `test-vectors.json`: Worked examples for every wire format element, plus RFC 9421, 9530 and 9180 vectors. - `design.md`: Stack and libraries, Cloudflare config, deploy, data model, owner API, MCP tools, key file, CLI, screens, tests. - `tasks.md`: Build order, each step with a check. - `research.md`: The standards it rests on, fediverse interop limits and the 0.1 choices.