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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:40:18 UTC

E.24:6 - Conformance Checklist

Activation rule: every candidate uses the cheap-card checks CC-E24-1, CC-E24-1b, CC-E24-1c, and CC-E24-2. CC-E24-1a activates only when a direct-relation or declaration-layer claim is recorded; CC-E24-3 through CC-E24-5 activate for a durable result; CC-E24-7 activates for bounded coordination. The remaining rows activate only when their named object or claim is current. A direct result closes from its current assertion and direct pattern. An inactive row is omitted, not filled with blanks or not current.

CheckObservable conformance condition
CC-E24-1The cheap card names the recognizable situation, one exact receiving use, one ontology disposition, any current source use, and one independently identified pre-judgment EntityOfConcern with its identity governor. That subject stays fixed; exactly one typed result points to the closing assertions, bounded episteme, durable ontic, or unresolved reason. Ordinary direct, bounded, and unresolved cases close here unless a stated full-form guard is true. Work and decision are examples of receiving use, not universal prerequisites. A working phrase, topic cluster, heading, or list is never accepted as the EntityOfConcern merely because it opened the inquiry.
CC-E24-1aThe decision keeps two layers explicit. At the instance layer, every included direct relation names actual participant meanings and kinds plus its direct governor. At the ontology/declaration layer, typed decision claims state why each kind, relation rule, declaration, pattern, and dependent reliance belongs; no world-side occurrence among those declaration-level objects is implied. Any identity-bearing relation is marked explicitly.
CC-E24-1bThe author characterizes the current case, runs existing-governor reuse, exact-identity, typed-connectivity-or-constitution, dependent-use, and non-duplication tests, and fills the ontology disposition last. Its summary placement near the top of a card is not evidence that it was selected first.
CC-E24-1cDirect use is selected when one readable governed claim closes the receiving use; bounded episteme when that use needs several governed claims read together but no pattern consumes their package as ontology; durable ontic only when multiple current patterns must reuse one independently identified ontology unit and would otherwise duplicate or disagree about identity, constitution, or the minimal relation set.
CC-E24-1dOne boundary fixture keeps the source expression, provenance, and independently identified decision subject fixed while showing the receiving use, changed evidence, exact branch payload, and stop for direct use, bounded episteme, the stronger durable-ontic threshold, and unresolved inquiry.
CC-E24-2Existing exact rule content is checked by value before a new ontic is selected. For a relation-kind candidate, the decision cites the exact direct relation pattern passage, which states participant meanings, obtaining, applicability, and occurrence identity, or an A.6.RCD result that returns a derived or primitive candidate with that proposed direct subject settlement. Local claim and predicate-definition results are not admitted as relation kinds.
CC-E24-3When the durable branch is selected, the decision states the proposed ontic’s stable identity criteria and says what does and does not change that identity.
CC-E24-4A durable ontic names the subject’s exact identity, constitution, or recognition rule and its minimal governed relation set. For every included relation it names the direct governor; when one is identity-bearing, it also names participant meanings, admitted actual-participant kinds, obtaining condition, and occurrence-identity rule. RelationSignatures and SlotSpecs are added only for typed reuse.
CC-E24-4aWhen constructive grounding is claimed, the text names the direct grounding rule. Structural identity claims use the E.14 -> B.3.5 -> C.13 chain with Working-Model, tv:groundedBy, and Γ_m; non-structural ontics use the identity, grounding, or recognition rule of their subject pattern.
CC-E24-4bOntic introduction creates no project-side relation occurrence. A designator designates and a governed reference resolves only after the direct predicate and identity rule reidentify the occurrence; an assertion or description episteme carries the claim and designation. A publication occurrence makes a selected episteme edition available and neither designates nor creates the world-side occurrence.
CC-E24-4cE.24 and E.24.UK use one E24FamilySettlementDecision. Independent positive kind admission may return the explicit direct-use or bounded-coordination conclusion that no additional durable ontic is needed, with no OnticSettlementResult. When both new outputs are independently needed, one atomic decision returns separate result references from common inputs; neither is prior evidence for the other and both remain provisional while a required branch is unresolved. An empty relation set or a nearby relation added for form supplies no coordination contribution.
CC-E24-5When the durable branch is selected, the decision states the primary governed subject kind, stable identity criterion, exact identity or constitution rule, minimal governed relation set and direct governors, the reliance basis of each named dependent pattern, existing-pattern reuse, and non-use boundary by value. E.10.ARCH wording-restoration coordinates are included only when that restoration opened the case, and the E.8 pattern nest remains publication placement; neither becomes a component or identity criterion of the ontic.
CC-E24-5aEvery current object is classified by the selection question and subject pattern in E.24:4.3a. Ontology/declaration-layer inclusion and reliance claims remain typed decision claims unless a separate direct relation is independently governed; none is silently promoted to a world-side occurrence.
CC-E24-5bAn encountered card, table, schema, diagram, file, or record is classified through E.24:4.3a; visible shape and field co-occurrence decide no governed use. Only an identified U.System performs description, rendering, or publication work.
CC-E24-5cMathematical operands, tuple components, nodes, and edges remain C.29 representation elements. A correspondence to a relation object neither identifies the two nor contributes to world-side occurrence identity.
CC-E24-6Draft ToC rows and planned pattern labels remain non-semantic locators. Until an exact defining or constraining ClaimGraph is written, a bounded local episteme contains only its stated claims for its declared use; for every exact entity and direct relation, those claims identify the current ClaimGraph and pattern-description locator.
CC-E24-7A bounded local episteme remains a U.Episteme under C.2.1, not a newly minted U-kind or durable ontic. It has one independently identified EntityOfConcern that every carried claim concerns; if no one subject survives, the claims are split or the inquiry remains unresolved. Other entities and relations stay under their subject patterns.
CC-E24-8The selected name passes F.18; the name does not hide a second ontology or one umbrella for several kinds.
CC-E24-8aDurable U.* names, reusable SlotKind heads, dependent-kind names, publication-form names, public ids, Core-facing heads, and cross-context labels use F.18; F.17 UTS and Name Card material is opened only when that name becomes public, Core-facing, or cross-context, and never replaces A.6.5 SlotSpec discipline.
CC-E24-8bA U.* spelling, type or kind wording, structural heading, title, filename, or ToC row that claims U-kind force is governed by E.24.UK before naming patterns are asked to choose or keep a public term.
CC-E24-9Pattern-quality and DRR-adequacy checks stay in E.21 and E.9.DA; they are not copied as user-facing ontic or subject-matter content.
CC-E24-10Each named dependent pattern is paired with the identified ontic identity, direct relation rule, or RelationSignature declaration on which it relies, and does not duplicate that rule or declaration.
CC-E24-11Bare role is routed through E.10.ROLE. The decision distinguishes a world-side participant under its direct subject pattern, a local system-role kind and its A.2/C.3.2 classification judgment, an exact A.2.1 assignment occurrence, and a declaration-local participant meaning in an A.6.5 reusable declaration. F.6 is opened only for current Work attribution. E.24 copies none of those patterns’ construction or occurrence rules and admits no false common head.
CC-E24-12For every selected direct relation, prose names the relation kind, participant meanings, obtaining rule, and direct governor; reusable declaration prose uses RelationSignature, SlotSpec, SlotKind, ValueKind, refMode, and RefKind. onticSlotRelation is not a universal field, and interface is used only when a governing boundary, module, signature, mechanism, or architecture pattern makes interface meaning current.
CC-E24-13Source-ontology annotation is proportional: decision-changing kind, slot, relation, admissible-use, and subject-pattern differences are recovered, while stable domain prose is not expanded into type labels. When a source expression affects the decision, the exact expression, source episteme, any current source publication occurrence, content carried forward, source-use status, current admissible use, and smallest stronger-use condition remain recoverable beside—not instead of—the ontology disposition.
CC-E24-14When candidate detection, publication-side object distinction, or contested evaluation is current, apply E.24.CD, E.24.PUB, or A.19.ECS respectively; E.24 itself stays centered on the primary governed subject kind, U.Ontic identity, exact identity or constitution rule, minimal governed relation set, subject patterns, named dependent-pattern reliance, and non-use boundary.