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

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:30:10 UTC

A.6.6:4.5 - Lexical discipline

Normative lexical rule. In Tech or normative prose, do not use umbrella metaphors (anchor, attach, ground, or support) in place of the actual relation. Prefer an ordinary relation-specific sentence; add functional or arrow notation only when a named receiver benefits from it.

Red-flag rule (anchor* as dependence metaphor).

  • In Tech or normative prose, rewrite anchor* as an ordinary relation-specific sentence, or move to the already reserved primitive that actually governs the claim.
  • In Plain or source commentary, quoted umbrella wording may remain for traceability when the repaired sentence immediately names the actual relation. It must not be converted into a generic validatedBy, verifiedBy, SupportRelation, or metaphor-headed token.

Carve-outs (pattern-defined primitives). This red-flag rule does not ban uses where “anchoring” is already a pattern-defined primitive elsewhere in the spec, such as E.10 MG-DA token-to-EntityOfConcern anchoring or A.10 evidence anchors. It still acts as a review trigger: confirm you are using the reserved sense, not smuggling a basedness meaning.

Naming guard for relation vocabulary. Do not mint a new direct relation whose name merely preserves a metaphor such as Anchor*, Ground*, or Attach*. Name the actual relation kind and use the corresponding ordinary verb phrase. In an optional assertion record, the local directRelationKind field identifies that already admitted relation kind; the field is not another relation kind. Lane guard for meaning. If the intent is “say what this expression means in this source”, do not introduce an Anchor… or Ground… relation. Recover the source-local claim under F.0.1; use F.17 only when a durable SchemeSenseCell or obtaining LocalSenseBasisRelation is actually needed. Semantic meaning assignment is not a base-declaration record.

Grounding disambiguation rule. If the prose says “grounded”, its actual ordinary or governed meaning MUST be recovered. The following branches illustrate distinct meanings, not an exhaustive classification:

  • constructive grounding (tv:groundedBy, base is a trace),
  • situational/empirical grounding (base is a grounding holon or experimental setup),
  • source-local meaning lane (exact source, scheme, expression, local claim, and optional F.17 cell or basis relation; no special base-declaration object).

Bind deconfliction note. Do not use “bind/binding” as a synonym for declaring, refreshing, or changing an assertion or reusable relation declaration. This local edit vocabulary does not rename name binding or other already governed binding relations, including A.6.1 application bindings. Use the local declaration-change label only when a named receiver needs that history.