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:50:07 UTC

A.2.1:8 - Conformance Checklist

IDCheck
CC-A2.1-1U.SystemRoleAssignment has no permissive root RelationSignature; every occurrence belongs to one directly declared species.
CC-A2.1-2Every species declares HolderSystemSlot : U.System and one declaration-local AssignedSystemRoleKindSlot with an exact local system-role-kind domain.
CC-A2.1-3Every additional participant changes the predicate or occurrence identity and has an admitted kind and complete SlotSpec.
CC-A2.1-4The direct predicate, applicability, and occurrence-identity rule are explicit.
CC-A2.1-5One occurrence spans the maximal uninterrupted predicate-true interval for fixed participant values; after a demonstrated gap, a later resumption is another occurrence.
CC-A2.1-6assignmentInterval describes known extent and is not a participant or proof of obtaining. Ordinary interval content stays local; a relied-on positive temporal aspect uses C.27.TA, while temporal-claim adequacy uses C.27.
CC-A2.1-7Taxonomy, scheme, signature, assertion, evidence, publication, and model-use structure are not generic assignment participants.
CC-A2.1-8A specialized occurrence is itself a U.SystemRoleAssignment; no weaker generic duplicate is created.
CC-A2.1-9Every species declares the common holder slot that F.6 may use to compare an assignment’s holder with an already recovered performer. The comparison erases no additional participants and discovers no performer.
CC-A2.1-10Classification and assignment remain independent; assignment is a criterion feature only when the signature explicitly says so.
CC-A2.1-11A.13 identifies the actual performer and A.15.1 independently admits the dated Work. F.6 checks the same assignment only if the current use must also say exactly under which assignment the Work was performed; a missing or failed check leaves the Work intact.
CC-A2.1-12A ...SystemRoleAssignmentRef field is typed by U.RelationRef constrained to U.SystemRoleAssignment, resolves to one exact occurrence, and keeps its declared species recoverable.
CC-A2.1-13Missing evidence leaves whether the assignment obtained unresolved or unknown. Actual predicate cessation or participant change ends the occurrence; evidence supports a conclusion about its boundary.
CC-A2.1-14Reduced use stops before explicit individuation when no receiver needs an assignment reference.