Manuscript XV-F-patch-ii@1 · XV-F-patch-ii.tex · section · 9674ac67
The question
Scope, gates, and the stop rule › The question · lines 206–235
XV-F-patch XVFpatch ended at F0 with Proposition
prop:F0, cited in the commissioning plan as
prop:F0patch. Its blocking list has four frozen gaps:
the residual codomain of the target space is undefined (D0.5);
the generators, coefficient class, and module action of the presentation package are not reproduced, so is not computable (D0.1–D0.4);
the ingredients of the six operational entries—, , , , , , , , , —are not fixed (D0.13–D0.14);
the correction class is a class of contact values whose parametrization (, , ) and presentation-level form are not supplied (D0.17);
together with the domain item (D0.8): is a named domain whose equality with is refused at three located places. This manuscript asks whether (a)–(d) and the domain item can be closed under the original F0 rule.
F0 rule. A core item passes when its frozen member is identified in a direct sheet, or when a convention is adopted here and explicitly offered as the frozen choice. A displayed parameter family is an open datum. A locator, a role, or a search term is not a member.