# The technical introduction

`rarelens.tex` is a standalone technical write-up of the platform — pipeline, event-driven
execution, infrastructure, the ranking, the model, and the parts that turned out to be wrong.
`rarelens.pdf` is the built article (10 pages).

```bash
make            # build the PDF (uses a Docker TeX Live; nothing to install locally)
make figures    # re-capture every figure, then rebuild
make clean
```

## Where the figures come from

Both kinds of figure are produced by one headless-browser script, `diagram-sources/shoot.mjs`, so
the article cannot drift away from the thing it describes:

- **Screenshots** (`01`–`06`) are taken from the running application. `make figures` needs it up —
  `make up && make migrate && make hpo`, the API on `:8000`, the UI on `:5173` — and a case that
  has been analysed. The published Loeys–Dietz case is the default; override with `CASE_ID`.
- **Diagrams** (`arch`, `events`, `pipeline`, `evidence`, `benchmark`, `model`) are HTML pages in
  `diagram-sources/`, styled from the same palette as the application, rendered to PNG by the same
  script. They are hand-written rather than generated, so any number in them has to be updated
  deliberately when the measurement changes — which is the point.

Figures are committed because rebuilding them needs a running stack and a browser. If a
measurement in the article changes, change it in the diagram source, re-run `make figures`, and
say so in the commit.