NAMING - Name a governed value for its readers

Preface node heading:naming-name-a-governed-value-for-its-readers:566

What this page is

This is generated FPF reference text from the specification preface or supporting sections. It helps interpret FPF; it is not FPF Reference product documentation.

Methodology

Use it to understand how the specification wants to be read, then return to a route, pattern, or work packet for active work. Cite generated IDs only when the wording changes the task decision.

Content

  • Situation and question. A governed value needs a stable Tech or Plain label across a bounded context. Ask: which name lets readers recover the value without changing its kind or scope?
  • Optional obstacle. Candidate labels carry conflicting senses, hidden kinds, or misleading morphology.
  • Template A. F.18 Solution -> NameCard. Local basis adds governed value, governing pattern, bounded context, candidate set, rejected candidates, rationale, bridges, lineage, and refresh condition.
  • Boundaries. Stop at a complete NameCard when no public term publication is current. Return when governed value, context, candidate evidence, reader interpretation, or bridge changes. Wrong-turn recovery restores the governed value before selecting a label. F.17 becomes the stronger neighbor only when actual term-row publication is current.
  • Public coarsening. "Naming card" restores to NameCard.

Last Updated: 2026-07-12 — upstream FPF commit 44dd8818 (github.com/ailev/FPF)