fpf.tools
Library / First Principles Framework (FPF) - Core Conceptual Specification
Jump to passage
In this reading
Source · lines 13728–13740

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:50:05 UTC

A.6.REL:5.1 - Repeated occurrence of one direct system-role-assignment species

Start with Robot-7 is assigned as inspector through InspectionAssignment-17 and trace only the objects needed by the current use.

  1. World-side participants and occurrence. Robot-7 remains an admitted U.System; InspectorSystemRole remains one exact local C.3 kind. InspectionAssignment-17 is an occurrence of directly declared MaintenanceInspectionAssignment <: U.SystemRoleAssignment. Robot-7 participates as the holder system and InspectorSystemRole as the assigned local system-role kind. Those two values are the complete participant set of this direct species.
  2. Direct settlement. A.2.1 supplies the species’ participant meanings, direct predicate, applicability, and same-versus-new-occurrence rule. The occurrence continues while that predicate obtains without interruption for the same complete participant set. A demonstrated predicate-false gap ends it; later resumption starts another occurrence. An evidence gap by itself does neither.
  3. Reusable declaration. For typed reuse, the MaintenanceInspectionAssignment RelationSignature contains HolderSystemSlot : U.System / U.EntityRef and the declaration-local AssignedSystemRoleKindSlot with MaintenanceSystemRoleKindDomain as ValueKind and ByValue as refMode. In InspectionAssignment-17, InspectorSystemRole is the assigned-kind participant value. A stronger direct species adds only its real identity-bearing participants. assignmentInterval remains assertion or occurrence-description content, not another participant SlotSpec.
  4. Assertion and participant designations. An InspectionAssignmentAssertion carries designations corresponding to the species’ declared SlotSpecs and states the currently known assignmentInterval separately. Its claim may say that Robot-7 is currently assigned as inspector through InspectionAssignment-17. If later use only needs that current report, keep the assertion and stop without adding another occurrence object.
  5. Occurrence identity, designator, and reference. Suppose two episodes of the same direct species have the same complete participant values but occur in inspection shifts separated by a demonstrated predicate-false period. To prepare a history or Work-attribution claim that must distinguish the episodes, a practitioner applies the A.2.1 continuity rule, distinguishes the second occurrence, and assigns a designator only if stable reference is needed. A roster-row identifier, copied field set, taxonomy edition, reference scheme, or reused source key cannot collapse or split the two episodes.
  6. Representation. A roster row or diagram edge may represent the assignment assertion or an occurrence-description episteme. A roster row’s fields and key retain their representation-side meanings; the source elements of a diagram edge retain their representation-side meanings. An explicit declaration or representation correspondence relates a source field to the exact SlotKind and the carried value or reference to the participant designation; using the same spelling for field and SlotKind is optional and establishes no identity. Representation identity does not replace the A.2.1 occurrence rule.

The practical payoff is visible at each stop. In a current staffing report, keep the readable direct sentence. For typed reuse, consult the existing declaration. When history or Work attribution must distinguish a repeated episode, apply the A.2.1 continuity rule and distinguish that episode; assign a designator only if stable reference is needed.