Figures: selection is a binding the author shows; gesture handling
Figures: layers in shared frames, queries, caption and legend as controls
CI, Contributing: production ships from Cloudflare Pages
Examples-as-Data: rewrite to the current design; roadmap: tabular data idea
Speculative: statistics and maps as fields of a collection's elements
Contributing, CI: cached dists, affected-only CI, data built not committed
Roadmap: fast paths replace kernel retirement; wasm kernels idea; completion-count speed landed
Restrictions: vexillary's declared work
Restrictions: vexillary by a state table
Restriction counts: reference algorithms for Baxter, Vexillary and Smooth
Restrictions: separable and non-crossing counts; what the other classes need
Epsil-Kernel-Performance: taken and prefix state, fast paths, words and trees
Per-Package-Repos: §4.1 steps 2–4 built
Sessions as data: notebook answers kept and shown at once; .ipynb export (#630)
Sessions as data: notebooks keep their document (built, #630); transcripts keep a journal
Per-package repos §4.1: step 1 built; declares comes with step 4
Vdom markup: notation extensions built; four packages as data
Vdom markup §4.4: scanning a library
Vdom markup §4.2: hosts read libraries through the kernel
Epsil-Kernel-Performance: per-params tables and the lattice-path families
Examples as data: known.convention and known.gap
Vdom markup: reference/
Library records in reference/<Name>/, as the system's packages keep theirs
Per-package repos §4.1: the manifest per library (proposal, BL-79)
Per-package repositories: the engine builder exists (#607)
Nucleus facade: decisions so far
Nucleus facade: Epsil definitions with optional cross-verified kernels
Nucleus facade survey (speculative)
Per-package repositories: the nucleus and its facade (direction, exploring)
Per-package repositories: only core knows compute-engine