A workbook is a committed folder outside the queue whose pages are HTML the learner opens in a browser — and the agent never writes that HTML. A lesson is authored as markdown carrying front-matter and small widget declarations, and a renderer in the toolkit turns it into the page: chrome, a stylesheet inherited from the token system Nexus documentation already uses, the interactive components, assets that resolve with no network at read time, and styles that survive printing. Markup is mechanical and costs several times the output tokens of the prose it wraps, so generating it is waste that recurs on every lesson written; as code it is also testable, consistent across pages, and unable to drift. Everything the workbook retains per learner — the concept ledger, progress, the learning records and the hint log — sits under a single parent folder inside the store, so a repository that would rather not commit a person's stumbles excludes it with one .gitignore line and still shares the workbook itself.
Meta
- feature: docs/features/roadmap-driven-learning
- estimate: M
- candidate stories: The store is created outside the queue and excluded from the distiller's behavioural diff analysis; Everything retained per learner lives under one parent folder that a single .gitignore line excludes; A lesson's markdown and front-matter render to a page without the agent writing markup; Widget declarations resolve to components from a shared library; Lesson pages inherit the existing Nexus token system rather than a new palette; Vendored assets resolve offline at read time; Generated pages are marked so review reads the authored markdown, not the HTML; Interactive components survive printing
- source: decomposition of "A teaching stage that turns a planned roadmap into hands-on exercises, placing the required theory immediately before each one — /nxs.teach, producing a workbook" (2026-08-31); re-scoped 2026-09-01 to own the renderer rather than generate pages (S → M)
A workbook is a committed folder outside the queue whose pages are HTML the learner opens in a browser — and the agent never writes that HTML. A lesson is authored as markdown carrying front-matter and small widget declarations, and a renderer in the toolkit turns it into the page: chrome, a stylesheet inherited from the token system Nexus documentation already uses, the interactive components, assets that resolve with no network at read time, and styles that survive printing. Markup is mechanical and costs several times the output tokens of the prose it wraps, so generating it is waste that recurs on every lesson written; as code it is also testable, consistent across pages, and unable to drift. Everything the workbook retains per learner — the concept ledger, progress, the learning records and the hint log — sits under a single parent folder inside the store, so a repository that would rather not commit a person's stumbles excludes it with one
.gitignoreline and still shares the workbook itself.Meta