← Home

Runbooks#

Runbooks are demolab’s procedure layer: named, repeatable jobs the agent runs step by step, showing each result and confirming before it moves on. Where a guide is always-on reference, a runbook is invoked when you want it: type its name in capitals (LINT, DOCTOR, GETTING-STARTED) and the agent opens it and drives it. Say HELP for the full menu. The canonical text is the Markdown source, linked below.

Getting in#

• GETTING-STARTED: set up a fresh lab end to end: scaffold, brand, pick a stack, get it building and optionally published, then land a first experiment.
• TOUR: a guided walk through an existing repository, so you (or a new collaborator) learn where everything lives.

Checking the work#

• LINT: audit the prose and the figures against the house style.
• DOCTOR: audit the repository’s structure against the rules.

Bringing work in#

• MIGRATE-CODE: wrap an existing codebase, one experiment at a time, without rewriting the science.
• MIGRATE-STACK: switch the language your tools are written in (MATLAB, R, Julia, Octave).
• FROM-JUPYTER: convert a notebook into a tool, a runner, and a write-up.

Housekeeping#

• EMBED-DOCS: use demolab as a docs subfolder inside another project.
• UPDATE: bump the demolab-cli dependency to the latest engine and review what changed between versions.

Their always-on counterpart, the guides, each has its own page in this collection.