#U-kind Governance and Ontic Settlement Coupling

E.24.UK · Stable · Part E FPF authoring discipline pattern · Normative unless a section is explicitly informative · Part E - The FPF Constitution and Authoring Guides

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Part E FPF authoring discipline pattern Status: Stable Normativity: Normative unless a section is explicitly informative

Use this pattern when an FPF text, heading, title, filename, ToC row, table, or source passage uses a U.*, type, kind, or subkind spelling and the author must decide whether it names a durable U-kind, a dependent durable value under an existing ontic settlement, a C.3 U.Kind, a Concept-Set or naming object, a slot position, a relation structure, a record, a publication form, a lens, a local frame, or wording that must stay outside current FPF vocabulary.

#Relations

#Content

#Use This When

Use this pattern when an FPF text, heading, title, filename, ToC row, table, or source passage uses a U.*, type, kind, or subkind spelling and the author must decide whether it names a durable U-kind, a dependent durable value under an existing ontic settlement, a C.3 U.Kind, a Concept-Set or naming object, a slot position, a relation structure, a record, a publication form, a lens, a local frame, or wording that must stay outside current FPF vocabulary.

Typical moments:

• a proposed U.* name appears in a pattern title, host filename, monolith heading, or ToC row;
• a current pattern uses type, kind, or subkind wording and the governed value is unclear;
• a structural name looks useful for search, but may advertise a false root kind;
• a slot name, relation position, record field, diagram node, table column, graph expression, or publication form has acquired a U.* spelling;
• a single E.24 ontic settlement appears to govern one root value plus several dependent durable values.

Primary EntityOfConcern. The EntityOfConcern is the U-kind admission relation for one candidate U.*, type, kind, or subkind name. The pattern governs whether the candidate is retained as a durable U-kind, retained as a dependent durable value under a root settlement, governed by C.3 typed-reasoning rules, or treated as a non-U object governed elsewhere.

Primary working reader. The first reader is an FPF pattern author or reviewer deciding whether a public FPF name should remain U.*. The downstream reader is the practitioner who uses public pattern titles, headings, ToC rows, and names as orientation cues and needs those cues to point to the real governed object.

First useful move. Recover the current governed object and the current use before judging the spelling. Then ask which existing FPF rule set governs the value: E.24 ontic settlement, C.3 typed reasoning, A.8 universal-core admission, A.11 parsimony, F.8 mint-or-reuse, F.5 naming, a direct subject pattern, or E.10 precision restoration.

What goes wrong if missed. FPF grows a shadow ontology by punctuation. A slot label becomes a kind, a publication form becomes an ontic, type and kind wording becomes active beside ontic settlement, and a useful title survives because it is searchable rather than because it names the governed object.

What this buys. Public U.* names become trustworthy. Root U-kinds, dependent durable values, C.3 U.Kind values, Concept-Set rows, slot names, relation structures, records, publication forms, lenses, local frames, and source wording outside current FPF use are separated before naming.

Not this pattern when.

• If the question is whether FPF needs a durable ontic at all, use E.24.
• If the question is only detecting an ontic candidate before the durable decision, use E.24.CD.
• If the question is the difference among an ontic, its description episteme, publication, and publication form, use E.24.PUB.
• If the question is one phrase-level precision issue with no durable name pressure, use E.10, E.10.ARCH, or the direct precision-restoration pattern.
• If the current value is already recovered and only its public label must be chosen, use F.8, F.5, F.18, or F.17 according to the naming use.

#Problem Frame

FPF uses U.* names for durable universal values and nearby governed values. Recent ontic work made that spelling more visible in titles, filenames, ToC rows, slot relations, source rows, and headings. The spelling is useful, but it is not ontology.

The same token shape can name different kinds of things:

• a root durable value such as U.Episteme, U.Method, U.Work, or U.Transformation;
• a dependent durable value such as U.MethodDescription, U.WorkPlan, U.RoleAssignment, U.View, or U.EpistemePublication;
• C.3 U.Kind or U.SubkindOf typed-reasoning values;
• type, kind, or subkind wording whose governed value must be recovered before current FPF use;
• a slot position, relation structure, selected structure, record form, publication form, math lens, representation lens, local frame, or source expression.

E.24.UK governs that separation. It is an E.24 subpattern because U-kind admission depends on ontic settlement, but it is not the head E.24 pattern. E.24 remains the head pattern for U.Ontic and ontic introduction. E.24.UK owns the detailed U-kind admission rules.

#Problem

Without this pattern:

1. U.* spelling substitutes for admission. A public name is retained because it looks like a kind.
2. Unsettled type and kind wording competes with U-kind admission rules. Type, kind, subkind, Concept-Set rows, U-kind names, and E.24 ontics become overlapping ontologies.
3. Dependent values become root values. A value whose identity is held by a root settlement gets treated as a new root kind.
4. Structural names over-admit. Titles, filenames, headings, and ToC rows advertise kindhood more strongly than the pattern body establishes.
5. Slot names and lenses become objects. Relation positions, graph expressions, tuple views, table columns, and publication forms receive U.* names.
6. Naming patterns are asked to do ontology. F.5, F.8, F.18, or F.17 is used before the governed value has been recovered.

#Forces

#Solution

Treat U-kind governance as a coupled but non-counting relation between durable U.* names and E.24-compatible ontic settlement.

Every durable U.* name needs one primary E.24-compatible settlement. That settlement may be:

• a root ontic settlement for the governed subject value;
• a dependent durable value under a root settlement;
• explicit reuse of an existing root subject U-kind;
• a C.3 typed-reasoning value when the current question is kind quantification, membership, subkind order, or kind bridge.

Every durable reusable ontic needs a named root subject U-kind or explicit reuse of one. This does not mean one full ontic pattern per U-kind, and it does not mean one U-kind per ontic. U.Ontic names the ontology-unit kind; it does not replace the subject kind governed by that ontology unit.

Use this compact decision relation:

UKindAdmissionDecision:
  CandidateSpelling:
  SourceLocationKind: prose | table | heading | title | filename | ToC row | source quote
  RecoveredGovernedObject:
  CurrentUse:
  IdentityGroundingOrRecognitionRule:
  C3KindUse:
  E24Settlement:
  RootSubjectUKind:
  DependentValueIfAny:
  NonUDispositionIfRejected:
  NamingPatternIfRetained:
  StructuralDispositionIfRejected:
  ReopenCondition:

#Positive Test For A Durable U-kind

Retain or introduce a candidate U.* name as a durable U-kind only if all of these are true:

1. It names a governed EntityOfConcern, not merely a source expression, local field, table column, reference suffix, publication form, or math-lens expression.
2. The value has stable identity across at least two uses or one load-bearing governing pattern.
3. The admission cites an identity, grounding, or recognition rule: direct governing pattern, C.3 membership and extent rule, Concept-Set witness set, A.6 SubjectBlock with RangedValueKind, imported signature symbol, CT2R/Compose-CAL constructive grounding for structural claims, formal-substrate or principle-frame declaration when current, or another accepted operational identity test.
4. FPF users need to make action-facing claims about that value, not only about a wording choice.
5. Existing root U-kinds plus slot and relation combinatorics cannot express the claim without losing reviewable distinctions.
6. The candidate has a primary governing pattern or another selected governing pattern in the same governed source set.
7. The candidate has an E.24-compatible settlement: root subject, SlotRelation when needed, semanticArea, ontologicalNeighborhood, admissible use, non-use boundary, and dependent-value policy.
8. Dependent patterns rely on this value by value or are expected to rely on it after the selected amendments.
9. F.18 and F.17 can name and publish the term without turning a local slot label into a kernel kind.
10. Source wording outside current FPF use is repaired by E.10, E.10.ARCH, or the governing pattern named by value.

If any row fails, the candidate is not admitted as a durable U-kind in the current form.

#Root And Dependent U-kinds

A root U-kind is the subject value whose identity is held by the primary settlement.

A dependent durable U-kind is a reusable public U-kind name for governed individual instances whose identity is kept through the same primary settlement as a root U-kind. The head pattern states the exact dependence relation and the governing pattern for those instances. It is not automatically:

• a C.3 subkind;
• a slot name;
• a record form;
• a publication form;
• a synonym for the root;
• a title convenience.

Read the words carefully:

• A U-kind name such as U.WorkPlan, U.RoleAssignment, U.MethodDescription, or U.Capability names a reusable governed kind admitted by this pattern and by its direct owner.
• An individual instance of that U-kind is one concrete governed object under that kind, for example one work plan, one role assignment, one method description, or one holder capability. It is not a second kind named Value, not a slot filler by that fact, and not a record field.
• Dependent durable means that the individual instance has durable identity for FPF use, but its identity is held through another settlement and declared dependence relation. It is not a root beside that settlement.
• The dependency relation is an identity and governance relation, not parthood by default. A U.RoleAssignment depends on role, holder, bounded context, and window; that does not make the assignment a part of the role. A U.Capability may depend on a holder U.System; that does not make the capability a system part or a U.Characteristic.
• A statement, record, evidence relation, publication, dashboard row, source expression, or fit predicate about a dependent individual remains a neighboring object unless its own governing pattern admits it as a governed object.
• Avoid bare value when the contrast is kind versus instance. Use individual, instance, or concrete governed object. Reserve slot-filler wording for actual slot relations and record-field wording for records.

Use this small reading table when authoring:

Examples:

#Combined Admission Order

Use existing rules in this order:

1. Recover the source use and governed EntityOfConcern.
2. If the current question is typed claim quantification, apply C.3 and C.3.1 first. U.Kind is the context-local intensional value; U.SubkindOf is a partial-order relation over those values.
3. Recover the identity, grounding, or recognition rule for the candidate: direct governing pattern, C.3 membership and extent rule, Concept-Set witnesses, A.6 SubjectBlock with RangedValueKind, imported signature symbol, CT2R/Compose-CAL constructive grounding when the claim is structural, formal-substrate/principle-frame declaration, or another accepted operational identity test.
4. If durable FPF kindhood is claimed, apply E.24-compatible settlement, A.11 parsimony, and A.8 universal-core testing when kernel-level status is claimed.
5. If the object is a slot, relation position, record, form, lens, local frame, expression, or source wording, do not admit a U-kind; apply the direct governing pattern for that object or claim.
6. Only after the recovered value and admission decision are stable, use F.8 for mint-or-reuse and F.5, F.18, or F.17 for naming and publication.

#Source Ontology Conversion Guide

Use this short conversion guide when a source ontology, schema, standard, class hierarchy, or top-level ontology uses words such as type, class, category, object type, entity type, kind, or subtype. BFO-style, ISO-style, OWL/RDF, database-schema, programming-language, and discipline-local type systems are source ontologies or representation regimes; they do not become FPF U.* names by translation.

First recover the source construct by value:

• source name and source ontology or schema;
• source identity rule, membership rule, extent rule, or recognition rule;
• source relations such as is-a, part-of, realizes, participates-in, depends-on, or equivalent local relations;
• intended source use: classification, query, modeling, exchange, validation, reasoning, implementation, or documentation.

Then select the FPF object:

A source "type" may become an FPF kind and may require an ontic, but only after these tests. If the source construct only supplies local classification or exchange syntax, keep it as C.3 typed reasoning, bridge material, representation material, or source wording. Do not create a rival FPF type layer beside durable U-kind governance and E.24 ontic settlement.

#Structural Location Rule

A U.* spelling in a pattern title, host filename, monolith heading, or ToC row is stronger than a prose occurrence. Structural locations orient readers to the governed object.

Use this rule:

• Prose occurrence: recover the local claim and direct governing pattern.
• Table row or record field: ask whether the field is a slot, record field, publication-form element, or governed value.
• Heading: retain U.* only when the section really governs that value or directly references an already governed value.
• Pattern title or host filename: retain U.* only when the pattern's primary EntityOfConcern is that root or dependent U-kind.
• ToC row: retain U.* only when the row points to a pattern that carries the settlement; otherwise name the direct governed object or repair the wording with E.10.

Do not keep a false U.* structural name for memory or search convenience. Use a Plain label, local heading, Name Card, Concept-Set row, relation name, record field, or quoted source wording when that is the actual object.

#Non-U Dispositions

If the positive test fails, select the actual governed object:

#Archetypal Grounding

#False Structural U-kind Title

A structural title that names an action-invitation precision-restoration move as U.ActionInvitationPrecisionRestoration looks like it names a durable U-kind. E.24.UK asks for the governed object. If the pattern governs a precision-restoration move for action-invitation wording, the U.* spelling misnames the public object. Rename the title to the actual pattern object unless the pattern writes E.24.UK evidence that a durable U-kind exists.

#Retained Root U-kind

U.Work can remain a root U-kind because the direct work pattern governs a dated performed occurrence with identity, use boundary, relations to role assignment and method, and action-facing claims. A heading or title may reference U.Work only when that governed value is current.

#Dependent Durable Value

U.WorkPlan is not performed work. It may remain a dependent durable value when the work-plan pattern states dependence on method, role, time, and intended work relations. The dependence relation is not U.SubkindOf unless C.3 typed-reasoning rules explicitly say so.

#Type And Kind Governance Passage

A passage that says a proposed type must pass A.8 or A.11 is a kernel-level U-kind admission question. A passage that says U.Kind and U.SubkindOf are used for typed reasoning remains under C.3 rules. A naming passage in F.5 or F.8 waits until the recovered value and admission decision are stable.

#Lower-level Heading

A C.2.1 heading such as U.ClaimGraph or U.Viewpoint does not admit kindhood by heading shape. The heading must be read through the episteme slot relation: retain as dependent value or slot component only if C.2.1 states the settlement; otherwise rename the heading to the actual slot, relation, or publication object.

#Bias-Annotation

This pattern blocks punctuation-bias and taxonomy-bias. A U.* spelling, title, filename, table row, or imported type word is not enough to create a durable FPF kind. First recover the governed object, its current use, the owning ontic settlement or typed-reasoning rule set, and the slot or relation position. Only then decide whether the public name should be a root U-kind, dependent durable value, C.3 U.Kind, Concept-Set row, slot name, relation structure, record, publication form, lens, or local frame.

#Conformance Checklist

#Common Anti-Patterns and How to Avoid Them

#Consequences

Positive consequences:

• public U.* names become reliable orientation signals;
• dependent values can be named without pretending to be roots;
• type and kind wording is governed by C.3, E.24.UK, A.8, A.11, F.8, and F.5 rather than preserved as overlapping ontology;
• structural names are settled before they become misleading public names.

Costs:

• pattern authors must read the governed object before keeping a convenient U.* spelling;
• some familiar host filenames, headings, and ToC rows must be renamed;
• structural inventory work becomes part of U-kind governance, not an afterthought.

#Rationale

FPF needs U-kind names to stay rare and load-bearing because they orient many patterns at once. Without a separate U-kind governance rule, ordinary type words, source-ontology classes, slot labels, filenames, and memorable headings create a second ontology beside E.24 ontic settlement and C.3 typed reasoning.

The coupling rule keeps the architecture compact: a durable U-kind needs an E.24-compatible settlement or an explicit C.3 typed-reasoning status; dependent durable values remain dependent on their root settlement; non-U objects keep their ordinary governing patterns. This lets FPF reuse source ontologies and discipline vocabularies without importing their taxonomy as FPF U-kinds.

#SoTA-Echoing

#Relations

• Specializes: E.24 for durable U-kind admission and structural-name U-kind settlement.
• Coordinates with: E.24.CD for candidate detection, E.24.PUB for publication and structural-name pressure, C.3 and C.3.1 for typed reasoning, A.8 and A.11 for kernel admission constraints, F.8 and F.5 for naming decisions, E.10 and E.10.ARCH for source wording outside current FPF use.
• Does not replace: direct subject patterns for method, work, role, episteme, transformation, relation, characteristic, view, measurement, publication, evidence, gate, source, or decision claims.

#E.24.UK:End

Last Updated: 2026-06-18 — this section last modified in upstream FPF commit cf12b979 (github.com/ailev/FPF)