Authority and Audit Survive Abundance

Joint answer to two #oq/now questions. (1) At a model upgrade neither prescription governs the other: shrinkage governs instruction scaffolding (request-form lines — ablate and delete), crystallization governs authority scaffolding (evidence-gated permissions, which a capability jump cannot earn and circularity forbids delegating into the model) — sort each line by what it encodes (request vs constraint/record), not where it lives, and the demotion circuit-breaker makes the upgrade moment decision-free on the authority side. (2) The retrieval layer survives ~free long context because only its cost leg is token-priced: per-chunk governance cannot live inside the window it polices ('model promised to ignore' is not a boundary), and in-window attribution is model testimony where an audit needs a checkable log — selection is what makes a citation log non-trivial, a requirement that binds compiled wikis too. Cost dissolves with price; governance and audit dissolve only with the requirements themselves.