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

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

A.0:QF.1 - Early set-result and metric-kind vocabulary

  • Use Palette for a plurality-preserving set with no dominance semantics yet.
  • Use TraditionPalette only when the members are traditions gathered before later comparison or choice semantics are declared.
  • For methods, hypotheses, environment-method pairs, candidate explanations, or other member kinds, use Palette plus explicit SubjectKind instead of borrowing the TraditionPalette head.
  • Use Front only for a non-dominated set under one declared DominanceSet.
  • Use Q-Front when the declared DominanceSet is the declared Q components.
  • Use Archive for a retained set whose purpose is coverage, stepping-stone retention, or frontier expansion rather than current non-domination.
  • Use ExplorationArchive for the broad retained exploration surface; it is the exploration-specific specialization of Archive.
  • Use SteppingStoneSet only for one narrower retained subset whose stated purpose is future frontier reach rather than the whole archive. It is not part of the ordinary first-pass public-head family for retained exploration.
  • Use Shortlist for the set chosen from one declared source set by one named lens.
  • Use RankedShortlist only when that shortlist is explicitly rank-ordered.
  • Use JointUseSet when every exact member is included for one named use; keep that use, keyed member entries, inclusion conditions, and basis pins under G.5.
  • Use ShortlistId for the stable public token of one emitted shortlist; it is not the shortlist itself.
  • Use ChoiceSet only when the mathematical set object underlying one shortlist must be named explicitly; do not let it replace the public shortlist head.
  • Use Q-set for the declared current objective tuple that may ground the current DominanceSet.
  • For a result or claim used by a pool policy, retain its direct pattern’s reference name and kind; for example, A.2.2 supplies capabilityHolderRef and capabilityStatementRef. Use C.19 for the resulting pool treatment. Citing an input does not add it to Q or dominance.
  • Use competenceModelRef under C.19 only for one exact model episteme used by the policy; identify the capability and supporting results separately.
  • When the pool treatment relies on an evidence-bearing or source-bearing claim, use a10RelianceRef for the exact claim and bounded pool-treatment reliance under A.10.
  • Use goalSpaceExpansionPolicyRef under C.19 when an independently declared archive or curriculum expansion policy governs goal- or task-space growth; that policy does not place a candidate on a front or add a dominance coordinate.
  • When future reach depends on a transition or transfer relation, cite its direct rule and supporting result references together with any model episteme actually used. Keep their use in archive/pool policy separate from any explicitly authorized promotion into dominance.
  • If one front is meant to be current-Q by default, say so as Q-Front or as Front over the declared Q components rather than leaving the relation between Q-set and DominanceSet implicit.
  • Use-Value may be one member of the Q-set only when the current Context declares it there; it is not the whole Q-set or the default Q-set by itself.
  • Metric-kind doctrine: the Q-set is the candidate/front-facing objective tuple; Novelty@context is one context-relative candidate signal; DeltaDiversity_P is one set-relative marginal diversity contribution; IlluminationSummary is one report-only archive telemetry summary unless one explicit policy promotes it.
  • Minimal mathematical lens: the current front lives in one declared comparison or outcome space, while the exploration archive may depend on one declared search, niche, or reachability space. Keep both spaces explicit when they differ.
  • Keep Novelty@context, DeltaDiversity_P, Surprise, and IlluminationSummary outside the default Q-set unless one declared PromotionPolicy says otherwise.
  • A reader should be able to tell whether one sentence is talking about a Palette, a Front, an Archive, a SteppingStoneSet, a Shortlist, a RankedShortlist, or a JointUseSet, and whether one selected set came from one declared source set, before later policy or geometry detail arrives.
  • Use portfolio only when the portfolio or set-result field is a declared retained set plus a selection/retention rule or a portfolio-publication posture. Do not use bare portfolio when Palette, Front, Archive, SteppingStoneSet, Shortlist, or RankedShortlist is already recoverable.