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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:20:20 UTC

A.6.RSIG:5.3 - Episteme-side worked recognition repair: method-description applicability

Draft cue:

“Use pairwise comparison.”

Why the cue is not enough yet:

  • the reader cannot tell whether the note applies to ranking alternatives, selecting one option, shaping a shortlist, or comparing method families;
  • the method note can be mistaken for the defining U.Episteme of selection semantics;
  • a team can prematurely choose C.11 or G.5 before identifying what the pairwise comparison is to determine.

Recognition repair:

  1. description_seen = one method-description applicability note.
  2. encountered_carrier_or_projection = one method-description note, pattern excerpt, or review comment that mentions pairwise comparison.
  3. applies_to = comparison under a declared comparator set or characteristic family.
  4. excludes = publication of a selected set, execution planning, evidence sufficiency, and one-off decision doctrine. If one of those questions is current, apply the pattern that governs it and obtain the result it requires.
  5. definitionEpistemeRef = the relevant comparison or method pattern, not the note itself.
  6. nearby_false_description_or_wrong_definition_episteme = selection/publication doctrine treated as if the method note had already settled it.
  7. first_admissible_entry_stop_or_reroute = method applicability is recognized or rejected before selection semantics begin.