Speculative-Restrictions: decisions, and the first slice
Vdom markup: link compute-engine#390
Vdom markup: pinned head example
Vdom markup §4.2–4.3: attributes, named slots and notation in the library format
Speculative-Restrictions: induced order, completion counts, audit of the permutation families
Kernel as a job store: IndexedDB store, engine workers, progress instead of leases; replaces the pool in Kernels and Front Ends §4
Kernels and Front Ends: the service worker host, a pool of SharedWorkers under a coordinator, support
Units and dimensions: own page, with prior art; Package Scopes §5 points to it
Package scopes: units and the dimensions under them
Foreign names and package scopes: shadowing at format boundaries; packages installed, enabled per scope
Vdom markup: placed named slots, markup on pages, structural atoms as tokens
Kernels and Front Ends: the build as a kernel; roadmap: render-environment symbols, ecosystem survey, ipynb export
Examples-as-Data: own forms are built, pins live in examples.tsv
Vdom: generic elements' text is atoms, value the arguments
Epsil kernel performance: where the 10× against the TS kernels goes
Roadmap: local mutation for Epsil folds (transients / in-place)
Kernels and front ends: requires follow the hierarchy, load order joins signatures
Vdom markup: pin check built
Kernels and front ends: sessions are scopes (transient, closable, forkable)
Kernels and front ends: formats as packages (fixed syntaxes, open targets)
Vdom markup: version check built (4.3)
Vdom markup: mappings (4.4)
Vdom markup: libraries and catalogs; versioning for now; what a library tracks; viewer
Vdom markup: package hosts; what a version number promises (proposed)
Vdom markup: system range built
Kernels and front ends: dressed shorthands in StandardForm
Kernels and front ends: notation (StandardForm input, TraditionalForm output, ambiguity checks)
Vdom markup: version ranges built
Kernels and front ends: speculative design
Overloads as data: type triggers; registry rows vs overrides