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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:25:59 UTC · snapshot created 2026-10-03 08:26:43 UTC · last check 2026-10-03 09:05:10 UTC

B.5.2.1:5.1 - Creative-generation consistency with the declared dominance doctrine

  • When candidate generation speaks about fronts, use the declared DominanceSet for the front and keep archive retention separate when archive mode is active.
  • Do not write novelty or diversity terms into the front definition merely because they are important to archive quality or exploration value.
  • If one generator emits both a front-facing result and an archive-facing result, say which surface each result belongs to.
  • If one generator speaks about selected results, keep that language in the shortlist family rather than silently reusing front language.
  • Prefer wording like front over the declared DominanceSet, plus the corresponding ExplorationArchive when archive mode is active over wording that folds Q, novelty, and diversity into one default front by habit.
  • The local generation story should stay consistent with the declared Front, Archive, and Shortlist language so comparison stays intelligible and lawful.