This hub gathers material on how technical concepts get *explained* — both a design decision and the deck/communication choices around it. The load-bearing decision is to [bundle Snapshot and Ontology into one State type] (Decision_StateAbstraction), justified as simplifying tool signatures, enforcing synchronization, and enabling session-level caching. Around it sit two deck-revision notes that flag where explanations currently fall short: [adding a context-window management explanation] (DeckUpdate_ContextWindowMgmt) via layered compilation (layer0/1/2/3) to answer a metadata-heavy-docs concern, and [clarifying propagation mechanics] (DeckUpdate_PropagationMechanics) through the git submodule hierarchy, presently left vague. Two style observations annotate register rather than content: one notes the [colloquial 'hand waving'] (StyleObs_HandWaving) metaphor as a vagueness signal, the other flags [domain jargon like 'context windows'] (StyleObs_Jargon) as presupposing a technical audience. The region is about explanation quality — what to simplify, what is under-specified, and the informal-vs-technical register the explanations adopt.
Witness phrases
verbatim Simplifies tool signatures, enforces synchronization, enables session-level caching, maps to Standard Context Tier (15K tokens)
verbatim One parameter instead of two; ontology always matches snapshot version; compile once, use many times
verbatim Clarify propagation mechanics (git submodule hierarchy); currently hand-waved as 'all materials update automatically'
verbatim it's great to like do hand waving and go oh, it'll propagate and it does this and it does that
verbatim how do you manage context windows, especially in large docs?
verbatim Register pulls two opposite ways: jargon ('context windows') assumes a technical audience while 'hand waving' signals over-vague under-explanation — the explainers are simultaneously too technical and too loose.
verbatim Two explanations are flagged as currently inadequate (propagation hand-waved as 'updates automatically'; context-window mgmt needs adding), in tension with the decision child's confident simplification claims.
verbatim These are mixed-kind children — a settled design decision, two open to-do revisions, and two meta style observations — not a single coherent argument.