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 13:10:03 UTC

A.2.7:6 - Conformance Checklist

CheckQuestion
CC-A2.7-01Is the current object one exact relation among system-role kinds, one C.3.1 U.SubkindOf occurrence, or one dependent SystemRoleKindRelationStructure whose exact kind constituents, selected obtaining relation occurrences, applied constraint claims, and named selection-use frame are all recoverable?
CC-A2.7-02Are all individual kind-slot values and all members of the bundle set exact context-local system-role kinds?
CC-A2.7-03Does each direct context-local species declare exact SlotSpec ValueKinds and one by-value predicate?
CC-A2.7-04Does the predicate state the actual receiving, incompatibility, allocation, or residual-restriction rule, applicability, and only meaning-changing semantic basis?
CC-A2.7-05Are system-role-taxonomy and scheme epistemes absent as generic participants and included in predicate identity only when they change meaning?
CC-A2.7-06Is relation obtaining distinct from assertion, evidence, identifier, publication, representation, and receiving-check outcome?
CC-A2.7-07Is substitution directional, incompatibility symmetric, and bundle membership order-insensitive?
CC-A2.7-08Does incompatibility name its exact species, holder rule, applicability and temporal test, with the actual-Work identity condition or the separately declared prospective-action identity/continuation condition of §4.3? Are actual assignments and the proposed action receiving inputs rather than new kind-relation participants?
CC-A2.7-09Does a bundle state its joint-admission and holder-allocation rule without creating a compound kind?
CC-A2.7-10Is U.SubkindOf used only after independent paired judgments establish monotonicity under the exact C.3.1 basis?
CC-A2.7-11Does a non-monotonic restriction remain a separately predicated residual relation?
CC-A2.7-12When occurrence identity matters, does it use fixed kind participants, fixed predicate, and maximal continuous truth interval rather than a row, graph key, or temporal SlotSpec; and is any target evaluation window kept in the receiving assertion or check?
CC-A2.7-13Does an explicit continuity decision cover a compatible edition before predicate and occurrence identity are preserved?
CC-A2.7-14Are current assignments and A.2.5 state occurrences inputs to the receiving check rather than relation participants?
CC-A2.7-15Does the system performing the check, its selected Method, checking Work, and exact outcome kind remain visible?
CC-A2.7-16Are graphs, tables, matrices, algebras, policies, taxonomies, and publications kept as descriptions, lenses, or epistemes?
CC-A2.7-17Does a negative, candidate, counterfactual, or unsupported claim avoid fabricating a positive occurrence reference or actual extent?
CC-A2.7-18Does cross-scheme use keep the Bridge, bounded-use assertion, reliance, local relation, assignment, authorization, and Work distinct?