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 10:45:12 UTC

C.22.2:8 - Portfolio, Archive, and Set-Return Treatment

Archive, portfolio, pool, front, shortlist, selected-set, and set-return material remain source and set cues for the current problem-side record. ProblemCard preserves sourceSetRef, source-set kind, selection or retention criterion, and the non-scalar next use when current; portfolio and archive governance stays with the named subject patterns and does not become a local problem-card kind.

Archive, portfolio, palette, front, shortlist, ranked shortlist, selected set, LivePool, and set-return material remain current source distinctions, but their current FPF subject patterns are already available:

Source wordingCurrent FPF pattern or relationRequired problem-card preservation when the corresponding claim is being made
Problem archiveC.18, C.19, A.10, G.6Preserve source set or reference, retention criterion, candidate status, and provenance relation.
Problem portfolioG.5, C.19, G.9, G.11Preserve selection or retention criterion, budget or window, review cadence, and selected-set or LivePool relation.
PaletteC.18, C.19, G.5Preserve candidate-family or option-set interpretation without turning it into evidence or approval.
FrontC.18, A.19, C.25, G.5Preserve declared characteristics and non-dominated set interpretation.
ShortlistG.5, with G.9 when comparison pins matterPreserve selected-set criterion and downstream use.
Ranked shortlistG.5 only when an order is declaredPreserve ranking criterion or narrow to selected set with tie notes.
Selected setG.5Preserve selected-set output, selection pins, and unknown handling.
LivePoolC.19Preserve pool policy, current treatment, and change trigger.
Set-returnG.5, C.18, C.16.Q, declared comparison recordsPreserve set-valued result when no total order is declared.

A singleton problem card is the degenerate case. If it came from a portfolio, front, archive, or pool, the selected problem remains traceable through sourceSetRef: the lightweight reference to the source-set kind, source reference, selection or retention criterion, budget or window, review cadence, and direct pattern when current. sourceSetRef is a reference field, not a new kind and not a downstream claim carrier.

sourceSetRef preserves the recoverable set-source relation when current: Palette, Front, Archive, ExplorationArchive, Shortlist, RankedShortlist, SelectedSet, LivePool, or another accepted source-set form. If the set-source relation is not recoverable, the card may keep a set-finding cue, but it does not claim selected-set readiness or archive-derived readiness.

When multiple plausible problem formulations remain current, C.22.2 does not bind one TaskSignature prematurely. Each optional rivalProblemFormulationRef states the rival formulation, EntityOfConcern, effective ReferenceScheme, ClaimScope, preserved concern, lost concern, reason not selected yet, and next discrimination action. It is not a CG-Frame, not the E.8 Problem Frame, and not a representation-frame kind. The next discrimination action may be to characterize, compare, retarget, reopen the source material or source relation, choose a local problem formulation, or apply the relation-bearing pattern. Reframing is triggered when EntityOfConcern, effective ReferenceScheme, ClaimScope, viewpoint qualification, or cause-theory cue changes the problem representation enough that readiness or use-boundary cannot be inherited by wording continuity.