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 14:30:10 UTC

A.2.1:1 - Problem Frame

InspectorSystemRole can classify Robot-7 for one maintenance slice without any assignment occurrence. Conversely, an assignment can obtain while no Work occurs, and a local KindSignature can use or ignore that assignment when classifying the holder.

U.SystemRoleAssignment is the common relation family. It has no permissive root RelationSignature. Concrete domain species declare the participant law that their occurrences actually satisfy. A simple inspection assignment may need only the holder and assigned kind. A project-review appointment may also depend on one exact commission. The stronger occurrence itself is the assignment; it does not sit beside a weaker generic assignment with the same projection.

The holder can be any independently admitted U.System, including a person, team, organization, service, organism, or non-human technical object. Assignment establishes neither capability, responsibility, commitment, permission, authority, access, gate passage, functioning, Method enactment, nor performed Work.

Taxonomy epistemes, reference schemes, KindSignatures, assertions, and interval descriptions can interpret or describe the assignment claim. They are not generic world-side assignment participants. A selected BoundedModelUseStructure belongs in the receiving assertion or use unless one separately admitted relation species makes that structure a required identity-bearing participant.