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

A.16.1:16 - Cue-Pack Package Discipline

A cue pack is useful only if it preserves enough structure to support later route publication or prompt formation without pretending that an endpoint claim has passed its test, a later publication is available, or an actual authority relation exists.

A.16.1:16.1 - Minimal preservation package

A robust cue pack should make visible:

  • the cue nucleus being preserved,
  • the preservation rationale,
  • the primary witness or primary anchor when one is load-bearing,
  • the candidate anchors / contrasts / exemplars that keep the nucleus non-arbitrary,
  • the secondary witnesses or carriers that corroborate or enrich it,
  • and the lane candidates or route-candidate hints, if such directional hints are already visible.

This is what turns early cues into an admissible preservation form.

A.16.1:16.2 - Route-candidate hints are optional, not forbidden

A cue pack is not an archive of low-articulation cues, but it also need not wait until route-candidate hints are fully articulate. If route-candidate hints are already visible, publish them. If they are not yet visible, publication may still be admissible when the cue nucleus, grounding, and preservation rationale make clear why the cue should not be lost.

A.16.1:16.3 - Valence is not endpoint semantics

Valence, urgency, discomfort, promise, or attraction may explain why a cue is preserved. They do not by themselves establish an A.6.A invitation, evaluation, abductive prompt, selected route, or route-selection status.