cv-orchestrator — CV production pipeline

Why

Keeping a CV in a Word file means every variant slowly drifts out of sync with reality. I run my CV like infrastructure instead: one source of truth, many rendered targets, all of them reproducible from a single nix run.

The pipeline

1. Master data — one structured CV (YAML/markdown sections) in git
2. Per-role builds — selected highlights and tone variations, compiled into a consistent artefact with sensible defaults
3. Validation — schema checks catch the “missing year” type of bug before the artefact ships
4. Versions — each published build is tagged, so I can reproduce the exact PDF I sent a year ago

Lesson

Declarative beats imperative everywhere, including personal documentation. The same philosophy that drives this site’s Nix environment drove the CV tool, then the hiring flow, then this whole site’s markdown pipeline.