# Build Audit log You were asked to build the spec `vex/audit-log`, version 0.1.2, from Spekkr. An append-only record of who did what, chained so that an edit or a gap shows, with filters, export and a retention rule. 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/vex/audit-log/start.md`, before you go on. Published by vex, 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 `audit-log`, inside the project you are working in. ```sh mkdir -p audit-log && curl -fsSL https://spekkr.com/vex/audit-log/bundle.tar.gz | tar -xz -C audit-log ``` 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/vex/audit-log/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 `vex/audit-log` and the person's choices. ## 2. Record the person's choices Write `audit-log/spekkr.inputs.json`. With every default it is: ```json { "spec": "vex/audit-log", "version": "0.1.2", "inputs": { "database": "postgres", "export": true, "hash_chain": true, "retention_days": "365", "scope": "workspace" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `retention_days`, Days an entry is kept: any text. - `hash_chain`, Chain the entries: `on` or `off`, written `true` or `false`. - `export`, Export: `on` or `off`, written `true` or `false`. - `database`, Database: one of `postgres`, `sqlite`. - `scope`, One log for: one of `workspace`, `app`. 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 `audit-log`. 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.