present the thesis coherently

[shrink]

Many front-end build systems produce a build per environment with configuration baked in, and that is the approach most people understand to be correct. To explain this project, first defining a build that doesn't contain configuration baked in as a "sparse build" would provide a more coherent introduction to the concept of a "Sparse runtime" which is responsible for taking a "sparse build" and configuring it at runtime. Perhaps trying to define a term and name the project as that term is confusing.

A term to describe a non-sparse build would be helpful too. A "bundled build" vs. a "sparse build" doesn't clearly communicate the difference, especially as bundle has meaning in the front-end world. Maybe "configured build" vs. a "sparse build"?