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 17:24:51 UTC · snapshot created 2026-10-03 17:30:20 UTC · last check 2026-10-03 18:25:10 UTC

E.24.UK:4.2c - Open Prerequisites, Blocked Candidates, and Non-admission Results

The shared decision can also encounter public kind names that do not yet have a resolvable accepted admission result. They remain explicit prerequisites rather than being smuggled into the accepted registry. Existing by-value use of an exact current value may continue under its subject pattern, but no new admission may cite the unsettled kind itself as already accepted.

Exact result or blocker referenceCurrent dispositionExact missing or closing basis
E24UK-OPEN-UREFERENCESCHEME-01U.ReferenceScheme prerequisite unsettledF.18 identifies the current FPFCoreReferenceScheme value and C.2.1 consumes an effective scheme, but no current subject pattern and accepted result state the kind’s identity, extent, and non-use boundary
E24UK-OPEN-UCLAIMGRAPH-01U.ClaimGraph prerequisite unsettledC.2.1 consumes exact claim content and distinguishes it from graph representations, but no current accepted admission result and direct kind-admission pattern are resolvable from this host set
E24UK-NAR-U-CAPABILITY-01U.Capability; rejectA.2.2 planning, promise, fit and development uses require a holder System and qualified ability claims, not another individual or classificatory distinction. Use U.System and C.2.1 epistemes when an assertion needs an identified account.
E24UK-NAR-LSMT-01U.LanguageStateMoveTrajectory; rejectA.16.0 needs an ordinary C.2.1 history account and an E.24.PUB expression/publication form. The recovered branch, loss, lineage and responsibility uses require no additional individual or durable classification.
E24UK-NAR-AIPR-01U.ActionInvitationPrecisionRestoration; rejectA.6.A governs a precision-restoration move; the title admits no further kind, and any exact relation claim still needs its direct obtaining predicate and identity rule
E24UK-NAR-EPUB-01U.EpistemePublication; rejectan episteme keeps C.2.1 identity while an exact EpistemePublicationRelation may obtain; Plain published episteme names that participation and not another kind

Generic reuse and local-kind are decision exits, not accepted example results. Close reuse only with an exact ReusedUKindRef that resolves to this registry; close local-kind only with one exact current C.3.2 LocalKindDeclarationRef. If either reference is absent, keep the candidate unsettled.

Consumer repair follows the disposition, not one replacement word. Method-description claims retain U.MethodDescription; exact viewpoint and view claims retain U.Viewpoint and U.View only under E.17.0 membership. Every lexical or source use of the rejected spelling U.EpistemePublication is recovered by its claim as the selected U.Episteme, exact EpistemePublicationRelation occurrence, publication form, or U.PresentationCarrier; the rejected kind has no occurrences to retype.

Thus dependent describes an admission and identity architecture. It is not a shorthand for every object named in a record, every participant of a relation, or every qualifier used to interpret an episteme.