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 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 10:05:06 UTC

A.3:5.2 - System-role assignment (U.SystemRoleAssignment) for actor-side enactment

When a performed-work claim relies on an assignment, identify its directly declared species under U.SystemRoleAssignment, the participant meanings and predicate that species defines, and the actual participant values that satisfy that predicate. Preserve the holder System, the assigned local system-role kind, and any real additional participant, such as a commission or position, required by that species. Use A.2.1 for its declaration and occurrence identity.

  • An assignment assertion or occurrence description may state assignmentInterval for the currently known temporal extent. That description does not make the predicate obtain or add a generic assignment participant.
  • Cite a taxonomy episteme and effective ReferenceScheme when they matter to interpretation. They, a generic U.BoundedContext, and a selected BoundedModelUseStructure are not generic assignment participants. When a receiving claim about Work depends on a selected interpretation structure, designate it through that receiving use’s relation.
  • The same System may hold several assignments to local system-role kinds when their direct compatibility rules admit them; labels or shared context wording do not decide compatibility.
  • When work on an episteme or carrier is claimed, the acting performer remains a System; episteme identity, carrier change, Work, publication, and evidence retain separate governors.
  • An independently grounded A.3.4 occurrence supplies none of the assignment participants or temporal facts by itself.