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:30:20 UTC

E.10.ROLE:5.1 - Alice Is Reviewer

“Alice is reviewer” may stay as readable recognition prose when no technical classification claim is consumed. If only the local kind matters, identify ReviewerSystemRole through C.3 and A.2. If a technical classification judgment matters, use A.2 and C.3.2 and keep Alice, ReviewerSystemRole, the current KindSignature edition, the context slice, and the true | false | unknown result recoverable. If assignment identity matters, first name the declared assignment species JournalReviewAssignmentRelation and establish that its direct predicate obtains for the actual participants, including Alice as holder, under the stated applicability. Only then identify ReviewAssignment-82 as the occurrence and state its extent. A roster, appointment label, description, or evidence item may support the assignment claim but does not make the assignment obtain. If performed Work matters, first recover Alice’s A.13 core for this action and independently admit ReviewWork-82 under A.15.1. Because this branch also says that Alice performed the Work under ReviewAssignment-82, F.6 afterward relates the already admitted Work to that same assignment. Classification, assignment, Work, and attribution remain separate. None follows merely from the ordinary sentence. A short projection may omit an assignment identifier unused by its receiving claim only when every relation the claim consumes remains recoverable.