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

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:2 - Problem frame

Name explosion usually begins with a helpful shortcut:

  1. Hybrid-system-role shortcut. RequestApproverSystemRole, DevOpsEngineerSystemRole, or IncidentLeadOnCall is minted because several local system-role kinds often appear together.
  2. Modifier-as-system-role shortcut. NightOperatorSystemRole, RemoteOperatorSystemRole, or APIApproverSystemRole is minted because a qualifier is visible.
  3. Status-as-type shortcut. AtRisk, Grace, PreValidated, or TemporarilyBreached is minted as if time stance or status value were a new essence.
  4. Source-suffix shortcut. EvidenceRole, RequirementRole, AccessRole, or ProviderRole is minted because a source tradition uses role-like language.
  5. Prestige shortcut. SeniorReviewer or LeadApprover is minted to bypass a separation, capability, or assurance question.
  6. Locality shortcut. The same spelling under two local-sense bases is treated as one value, or every difference is answered with a Bridge, card, cell, and row before a receiving use exists.

F.14 prevents those shortcuts from becoming durable ontology or automatic naming infrastructure.