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 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:25:17 UTC

F.18:6 - What Belongs In The Label

Choose a head that helps the reader recognize the governed value and only the qualifiers needed to distinguish its local meaning. Use SystemRole morphology for an exact local system-role kind, and relation, slot, Method, Work or characteristic morphology only for the corresponding recovered value.

For a kind or value-family name, do not pack a current holder, temporary admission state, particular Work occurrence, evidence claim or gate result into the label as though it defined that family. A stable number, threshold or other qualifier belongs only when the subject’s definition makes it part of the distinction the name must preserve.

When naming an exact assignment or performed Work occurrence under §§5.2–5.3, an occurrence designator may include an identifier, holder cue or date when needed to distinguish that occurrence. For example, the worked-case designator HullAssemblyWork-42@2026-07-15T09:10–11:35 still resolves through the independent Work-admission and identity basis. The token does not establish that basis.

Quick check: identify the value being named, remove each optional word, and retain it only when the reader would otherwise lose a needed distinction. Put current evidence, permission, status and other neighboring claims under their own rules.