CC-F17-1 | One exact governed value, its kind, the pattern that defines or constrains it, and the proposed row use were recovered before the row. |
CC-F17-2 | F.14 was applied at every current card, cell, and row gate, and the lightest sufficient naming disposition was tried first. |
CC-F17-3 | Row episteme, NameCard, designation expressions, governed value, reference, exact SenseCell, basis relation, and any F.9 Bridge remain distinct. |
CC-F17-4 | Every cell resolves to an effective by-value ReferenceScheme, exact expression, and local-sense claim; no generic context field or selected structure substitutes for them. |
CC-F17-5 | Every actual LocalSenseBasisRelation has exactly the cell and basis episteme as participants; descriptions, source units, publication occurrences, forms, and carriers stay separate. |
CC-F17-6 | Any F.9 Bridge actually obtains between exact cells; the separate use claim and A.10/B.3 reliance are visible only when that row use is current. |
CC-F17-7 | Admissible use, blocked use, row edition id, currentness condition, and any exact C.2.1 edition relation are recoverable without treating designators as identity. |
CC-F17-8 | If availability is claimed, exact E.24.PUB expression, bearing, and publication occurrences are recoverable independently from the row and from rendering or upload Work. |
CC-F17-9 | Multi-view naming uses three separate rows: U.Viewpoint names same-individual P only under E.17.0’s fixed-content/selected-S predicate; U.View names same-individual E only after exact E/P conformance obtains; and EpistemeViewpointConformanceRelation names the two-participant pair-determined direct kind. References, designators, NameCards, RelationSignature, occurrences, construction, and publication grant none of those results. |