The app
soldermask serve runs a small web application around the pipeline. It has four pages and an API.
| Page | What it is for |
|---|---|
Projects (/) | Every board on this machine, with a thumbnail, its state and its cost. Start a new one from a sentence or a design.json; fork, rename, archive, delete. |
Workbench (/p/<project>/<version>) | One version of one board: copper, 3D and schematic views, the conversation that produced it, parts, nets, stock, and the version history with diffs and downloads. |
About (/about) | What is running: version, commit, model backend, router, data directory, changelog. |
Benchmarks (/benchmarks) | What the shipped models scored on boards they never fit on, and what the pipeline scores on boards it wrote from a prompt. Read off disk; nothing is computed on the page. |
Everything the pages do goes through the HTTP API, so a script can do it too.
- Projects — the library.
- Workbench — the three views, the four regions round the stage, and the chain.
- Chat and decisions — how a board is edited by talking to it.
- Versions and history — what a version is, diffs, restore, fork, labels.
- Exports and files — Gerbers, KiCad, the standalone viewer.
- Builds and live sync — what happens while a turn runs, and two devices on one board.
- Benchmarks — the model scores, the eval runs and the rubric, and which of them are training-day numbers.