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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 13:30:20 UTC

E.10:8.5a - Entry lexeme support and lexical-query discipline

Public first-entry scenario text, ToC query rows, local Problem-frame recognition text, or worked entry comparisons in E.11 may use one compact entry lexeme cue block when the lexical issue changes the first useful FPF entry. That cue block should not be copied into every pattern body by default. Keep it instead in:

  • FPF readme section,
  • E.11 public-entry positions,
  • worked entry comparisons in E.11,
  • Table of Contents query rows,
  • or one bounded lexical-query record governed by F.17, UTS, or F.18.

This block remains one editorial lexical-query set. It does not mint names, aliases, durable U-kinds, bridges, or semantic equivalences by itself. When visible, it should distinguish at least:

  • canonical label,
  • plain-language twin,
  • domain alias,
  • lexical-query cue,
  • rejected cue,
  • false friend or inadmissible synonym.

Minimal visible lexical-query shape may therefore use one compact field set such as:

canonical
noncanonical_visible
domain_query_examples
forbidden_aliases

Ordinary lexical-query support should stay compact:

  • ordinary Table of Contents rows: prefer 2-5 query phrases;
  • ordinary README scenario or E.11 entry-distribution cues: keep only the most discriminating domain phrases and false friends;
  • fuller lexical sets belong under F.17, F.18, and E.10 only when one real naming, alias, bridge, or collision claim exists.

Lexical support should increase entry precision, not maximize keyword recall. The same boundary should be kept explicit in lexical support:

  • lexical_hook is not one alias;
  • one alias is not one canonical name;
  • one search cue is not one semantic equivalence;
  • one entry_orientation_label is not one RelationKind.

Language-specific query cues may be added as entry-lexeme support. They do not become canonical names, aliases, or semantic equivalents unless an accepted F.18 naming settlement admits that use; otherwise keep the phrase as ordinary local query wording. Such a practitioner phrase may help recover a canonical FPF pattern while remaining lexical-query support only.