F.15:9 - Static conformance rules for composed material

SCR-F15-S7 (SystemRoleKindDescription boundary). An F.4 SystemRoleKindDescription is one C.2.1 episteme about one exact local system-role kind under one effective ReferenceScheme. It makes the C.3 candidate domain, operative membership condition, intended member/non-member boundary, continuity rule, and current KindSignature recoverable. Practice or source provenance may locate the definition but does not identify the kind. The description is not the kind, NameCard, SchemeSenseCell, assignment, status, evidence template, method, or work; a cell is cited only when the naming use needs one.

SCR-F15-S8 (Name discipline without F.18 duplication). Every candidate or selected name cites the recovered governed value and the pattern containing its defining or constraining rule. Apply the F.14 and F.8 criteria to decide whether naming work continues; use F.18 to form the NameCard and choose designations; use F.17 to constitute an admitted row. In an F.15 check, verify those exact references; do not choose a name.

SCR-F15-S9 (F.17 row truth). Each cited row is one exact F.17 UnifiedTermRow episteme that records one value, its direct kind, the locator where that kind or value is defined, its NameCard, selected designations, effective scheme, one or more exact SchemeSenseCell refs, admitted and blocked uses, and reopen condition. One cell is valid when the row use is not cross-local; a row-shaped local note or table position is not a row episteme.

SCR-F15-S10 (Cell and neighbor purity). Each row cell remains an exact SchemeSenseCell. NameCard, local-sense basis relation, Bridge, Bridge description/Card, selected Structure, source publication, row id, and carrier remain separate refs and substitute for no cell component.

SCR-F15-S11 (Reuse before minting). When an existing NameCard or row supports the same governed value and admitted use, reuse it or record the exact F.8 decision that justifies another naming settlement. A new label, table, project, or edition is not a visible value difference.

SCR-F15-S12 (Actual Bridge before Bridge use). A cited F.9 Bridge has two exact endpoint cells, one exact relation-semantic profile, a currently true kind-defined predicate, and all required dependencies. Its assertion/description episteme and optional Card remain separate. A separate C.2.1 claim states whether that occurrence suits the exact direction, rule, loss tolerance, polarity, and use; A.10 or B.3 separately governs reliance.

SCR-F15-S13 (Cross-local locality). Use F.9 only for different <ReferenceScheme, LocalSenseClaim> projections and one named current correspondence use. Same-projection expression reuse stays with designation; different projections do not themselves establish a relation; when no current correspondence use exists, add no Bridge or bounded-use claim.

SCR-F15-S14 (Status honesty). A status-shaped item resolves through F.10 or another applicable status rule to the exact family and value definitions, target, scope, window, source condition, and intended use. Adjective, time, scale, phase, confidence, row presence, or display label creates no status family, value, assurance, gate decision, or evidence use.

SCR-F15-S15 (System-role-kind relation preservation). Every exact incompatibility, monotonic kind order, residual qualification, bundle, requirement, or selected SystemRoleKindRelationStructure remains an independently identified relation occurrence or selected structure. A description or convenient fused name creates neither another system-role kind nor an assignment or performed Work.

SCR-F15-S16 (Rule and locator boundary for non-naming claims). Assignment, work, result, evidence, source, publication, currentness, assurance, gate, decision, method, capability, policy, structure, and subject-relation claims cite the rule that defines or tests each exact claim and the PatternID that locates it. When a rule fails, re-evaluate that subject claim under the rule; an F.15 result neither decides nor absorbs the claim.

SCR-F15-S17 (Public naming and publication separation). Public or Core-facing naming cites an exact F.17 row only after its current gate passed. Row currentness is not availability: E.24.PUB separately governs any publication occurrence, form, carrier, audience, and bounded use, and rendering/upload work remains separate.