demolab has a small vocabulary for its parts, and using the words precisely saves a lot of confusion. This page defines the ones you will meet most, with the distinctions that are easy to mix up called out explicitly. If you would rather be walked through it interactively, type GLOSSARY in capitals and the coding agent will take you term by term.
experiments/exp<NNN>.py runs a tool and stages results, and writings/exp<NNN>.typ is the writeup. A tool is reusable science; an experiment is one run of it. Do not confuse the two.experiments/exp<NNN>.py file: it runs a tool’s CLI (or computes inline), renders figures from the data, and stages the record. It never imports a tool.writings/ar<NNN>.typ, with no runner and no data pipeline. Contrast an experiment, which does run one.writings/<id>.typ: an experiment’s writeup, an article, or a deck. It is a meta plus body pair the engine discovers and publishes.writings/<id>.slide.typ Touying slide deck. It is paged-only, compiled to a standalone PDF and grouped under the slides collection (or its meta.collection, if set): listed, but not an entry.artifacts/: artifacts/data/<id>/ holds a run’s figures and numbers.json, artifacts/pdfs/ holds shareable PDFs, and artifacts/site/ is the gitignored web build.numbers.json: the aggregated, committed record of a run: each command’s config plus headline metrics plus a provenance stamp. Writings read it so the numbers cannot drift.dirty flag, and a UTC timestamp, surfaced as a page and PDF footer.collection: slug in their meta, grouped together on the homepage.The full reference lives in GLOSSARY.md.