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 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:45:17 UTC

C.18:2 - Problem

Without C.18, a team often compresses several different objects into one word such as archive, front, Q-front, portfolio, style pool, or candidate set. That loses the distinctions between front, archive, and telemetry use:

  • a front answers current non-domination under a declared comparator or dominance set;
  • an archive answers retained exploration value, coverage, stepping-stone value, or future reachability under a declared retention policy;
  • telemetry reports search health, coverage, novelty, diversity, or lineage but does not by itself dominate alternatives.

Use G.5 for downstream selected-set result declaration, C.11 for local choice, the applicable C.30 or C.32 pattern for an architecture claim or candidate, C.36 for cultural-evolution case work, A.15.2 for planning, A.15.1 for performed Work, and G.11 for currentness and refresh.