Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:40:20 UTC

C.3.1:7 - Archetypal Grounding

SituationC.3.1 moveBoundary
CoolingPumpKind is below PumpKind.Use criterion entailment: the cooling-pump condition already requires the governed pump condition. State the readable relation and its applicability.Do not infer a public U.CoolingPump, and do not use current extension rows as the truth-maker.
A closed inspection lot has five cabinets.If the declared candidate domain is exactly those five cabinets, check admissibility and evaluate every candidate. The domain-bounded subkind relation from InspectedCabinetKind to the proposed broader kind can obtain when every narrower true is broader true.The same observations do not establish an open-ended order over all future cabinets.
MorningShiftQualifiedOperatorKind and UnionRosteredOperatorKind happen to select the same people in a closed current roster.Mutual domain-bounded subkind facts may obtain, giving classification equivalence for this roster.The kinds remain distinct because their operative membership conditions differ; antisymmetry does not merge them.
A signature adds an aligned unit conversion.Apply section 6, keep the kind, identify the new signature edition, and retain edition-specific judgments.Do not rewrite earlier judgments as if the new edition had been used.
A signature changes from physical cooling performance to a schema label.The boundary probes expose a changed candidate domain and discriminator; identify another kind.Do not hide the mismatch by editing the extension.
Pump #14 changes state in a later plant slice.Re-evaluate the admissible candidate and allow the extension to change.Candidate-state change alone does not create a kind, signature, or relation occurrence.
InspectionWorkKind is used locally.Classify only an independently identified W : U.Work.U.Work, a plan, or a log row cannot occupy W’s candidate position.
WorkPlan depends on Work.Use the governing work or E.24.UK relation.Do not encode dependency as U.SubkindOf.
SafetyCriticalFunctionKind is proposed as a subkind of FunctionKind.First recover both function senses under A.6.F, then use exact criterion entailment or the deliberately closed-domain branch.The word function, a risk label, or current examples establish neither the kinds nor the subkind fact; another public U.* name still requires E.24.UK.
A project proposes public U.CoolingPump.Take the recovered kind to E.24.UK, then apply naming patterns if admitted.Local typed use and U.SubkindOf do not admit or publish another durable kind.