F.18:4.2d - Pending R7 rule-content NameCard candidates
The following are candidate inputs, not current NameCard epistemes. Each uses the exact by-value FPFCoreReferenceScheme, keeps the governed U.NameToken separate from the R7 predicate or designation value it names, and asserts no Bridge because it makes no current semantic-correspondence claim. E.10’s exact TokenClass, reserved-name, and allowed-scope prerequisites remain unresolved, so PublicRowStatus = pending for all three and no UnifiedTermRowRef exists.
| Candidate expression | Exact local sense and governed value | Covered head families and rejected overread | Three-arena invariance | Reopen/close condition |
|---|---|---|---|---|
SelectedRuleContentSubgraphDesignation | use-relative designation resolving the exact nonempty base subgraph selected in one identified derivation or criterion-selection claim; governed node SelectedRuleContentSubgraphDesignation@RuleContentBasisFindingDefinition-R7 | selected subgraph/designation, selected basis/reference, and rule-bearing classifier families were compared; reject intrinsic RuleBearing..., generic Base, and reference-only heads because the value is selection-relative and by-value | manufacturing assembly-rule selection; healthcare protocol-premise selection; cloud deployment-policy criterion selection | close only when exact LEX.TokenClass, LEX.Reserved-Names, and LEX.AllowedScopes values and assertions pass under FPFCoreReferenceScheme; reopen on R7 semantic or scheme change |
derivedUsingRuleContent | predicate true only when an identified derivation claim used exact base content as a formal premise under a declared inference rule/application to produce exact dependent content; governed node derivedUsingRuleContent@RuleContentBasisFindingDefinition-R7 | derived-using, derived-from, supported-by, and based-on families were compared; reject derivedFrom because source/provenance and semantic derivation are broader, and reject supportedBy/basedOn because they hide actual formal-premise use | manufacturing configuration derivation; healthcare dosage derivation with evidence kept separate; cloud configuration derivation | same lexical prerequisites as above, plus exact R7 predicate identity |
evaluatedAgainstRuleContent | predicate true only when an identified criterion-selection claim selected exact base content for one bounded evaluation claim concerning exact dependent content; governed node evaluatedAgainstRuleContent@RuleContentBasisFindingDefinition-R7 | evaluated-against, assessed-under, governed-by, and checked-with families were compared; reject governedBy and generic checkedWith because they hide criterion selection and can imply authority, Work, or tool use | manufactured configuration evaluation; healthcare protocol-conformance evaluation; cloud release evaluation against deployment policy while operational Work stays separate | same lexical prerequisites as above, plus exact R7 predicate identity |
A collision-free text search is useful evidence but does not substitute for the missing governed lexical values. Until closure, authors may quote these candidate spellings when discussing the R7 declaration, but must not cite a current NameCard or public term row.