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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 07:10:10 UTC

F.15:13.3 - Rename a SystemRoleKindDescription without changing the described kind

IncidentReviewerSystemRoleKindDescription@t0 and ServiceIncidentReviewerSystemRoleKindDescription@t1 describe the same exact IncidentReviewerSystemRole only if F.4’s candidate domain, operative membership condition, intended member/non-member boundary, continuity rule, current KindSignature, effective scheme, and description claims support that continuity. A changed source, practice, or name alone decides neither sameness nor difference.

F.15 result:

  • RSCR-F15-E7 compares the two exact description epistemes and the described local system-role kind.
  • RSCR-F15-E8 permits F.13/F.18 alias or rename treatment only for expression change with value, scheme, sense, and use preserved.
  • F.18 updates the NameCard; F.17 updates a public row only if that row use is current and its gate passes.
  • If the described system-role kind or description claim changed, F.4 and the naming patterns create the corresponding new objects; F.15 does not declare continuity.