A.8:0 - Use This When
Use this pattern when a candidate durable U-kind is proposed as a kernel-level universal primitive rather than as a local concept, C.3 U.Kind, direct subject-pattern value, Concept-Set row, slot, relation, record, publication form, or dependent durable value.
What goes wrong if missed. A local domain noun enters the kernel as if it were universal, or a genuinely universal primitive is rejected because its domain projections use different words.
What this buys. Kernel admission becomes a falsifiable cross-domain claim: the candidate must keep the same abstract contribution across diverse domain families while losses and local differences stay visible.
Typical moments:
- a candidate U-kind is proposed because several domains use similar words;
- a local subject value starts being treated as universal because it is useful in one field;
E.24.UKadmits a durable U-kind candidate, and the remaining question is whether it belongs in the universal core;- source or draft type wording claims kernel-level status and must be recovered into current U-kind governance.
Primary EntityOfConcern. The EntityOfConcern is the universal-core admission claim for one candidate U-kind.
First useful move. Apply E.24.UK first. If the candidate survives as a durable U-kind and claims kernel-level status, test whether it makes the same abstract contribution in at least three foundationally different domain families.
Not this pattern when.
- If the issue is C.3 typed claim quantification, use
C.3andC.3.1. - If the issue is whether the public
U.*spelling should survive at all, useE.24.UK. - If the candidate can be expressed by composition, dependent value, slot relation, or direct subject pattern, use
A.11and the direct pattern before A.8.