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 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 14:20:15 UTC

C.18:4.4 - Front And Archive Are Different Returns

  • Start from one declared candidate or eligibility set.
  • Return the non-dominated front from the relation-token set under the declared comparator or dominance set.
  • Return the exploration archive separately when retained exploration value, coverage, novelty, diversity, stepping-stone value, or future reachability is current.
  • Keep tie-breakers and telemetry explicit so diversity, illumination, or popularity signals do not rewrite front semantics.
  • Before promoting telemetry or a popularity-like signal into the comparator, dominance set, or selected-set criteria, check which intended archive/front uses or values become worse or more fragile when that signal improves. State the affected uses or values, or the checked loci when none worsened, and cite the policy or decision authority that admits the promotion and any trade-off. If this basis or authority is missing, keep the signal as telemetry or an explicitly bounded tie-breaker rather than silently promoting it.
  • Use RetentionIntent=steppingStone when retention exists for frontier expansion or later curriculum value rather than current dominance.
  • If one source line keeps both returns, say that the front answers current non-domination while the archive answers retained exploration value.