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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:00:09 UTC

F.14:10.2 - Operators across shifts

Candidate family: OperatorSystemRole, NightOperatorSystemRole, RemoteOperatorSystemRole, OnCallOperatorSystemRole.

Premise: A.2 with C.3 has independently admitted OperatorSystemRole as an exact local system-role kind. Without that basis, OperatorSystemRole is still a candidate name and the case makes no kind claim.

Result after that premise:

  • Reuse the admitted OperatorSystemRole kind.
  • night, remote, and on-call are qualifiers in the proposed wording. Recover the claim each qualifies—for example, a schedule, location relation, SystemRoleAssignmentStatePredicate, WorkPlan, or policy condition—and use the pattern that defines, constrains, or tests that claim.
  • A new system-role kind is blocked unless A.2 with C.3 independently recovers a distinct local kind through its U.System candidate domain, operative work-facing membership condition, useful member/non-member boundary, and continuity rule. Its criterion may use, for example, a capability, Work, or an assignment established separately, but assignment conditions, a Method, and Work implications are not universal requirements. A practice, source, suffix, or naming ReferenceScheme does not create the kind or its difference.