# Build Two-factor sign-in You were asked to build the spec `kato/two-factor`, version 0.1.2, from Spekkr. A second sign-in step with authenticator-app codes and recovery codes, added to the sign-in an app already has. 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/kato/two-factor/start.md`, before you go on. Published by kato, 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 `two-factor`, inside the project you are working in. ```sh mkdir -p two-factor && curl -fsSL https://spekkr.com/kato/two-factor/bundle.tar.gz | tar -xz -C two-factor ``` 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/kato/two-factor/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 `kato/two-factor` and the person's choices. ## 2. Record the person's choices Write `two-factor/spekkr.inputs.json`. With every default it is: ```json { "spec": "kato/two-factor", "version": "0.1.2", "inputs": { "database": "postgres", "issuer_name": "Acme", "remember_device": false, "required_for_all": false } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `issuer_name`, Name shown in authenticator apps: any text. - `remember_device`, Remember a device for 30 days: `on` or `off`, written `true` or `false`. - `required_for_all`, Required for every account: `on` or `off`, written `true` or `false`. - `database`, Database: one of `postgres`, `sqlite`. 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 `two-factor`. 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 criteria. - `design.md`: Data model, rules and flows. - `tasks.md`: Build tasks in order, each with a check.