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

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 07:15:14 UTC

A.6.RSIG:5.1 - System-side worked recognition repair: boundary-presented description

Draft cue:

“The system shall reject invalid requests.”

Why the cue is not enough yet:

  • the reader cannot tell whether they are reading one law, admissibility gate, duty, work effect, or evidence statement;
  • one summary page or local paraphrase can be mistaken for the governing boundary description;
  • a reviewer can start arguing full semantics before identifying which description to inspect.

Recognition repair:

  1. description_seen = one boundary-presented admissibility description.
  2. encountered_carrier_or_projection = one clause or excerpt where the description is seen.
  3. reader_viewpoint = the perspective of a practitioner or reviewer deciding whether this is the right boundary description to inspect first.
  4. applies_to = requests presented at the boundary under the declared admissibility conditions.
  5. excludes = downstream effect claims, duty allocation, or evidence claims not actually stated by this description.
  6. definitionEpistemeRef = the governing boundary description, not one local paraphrase or summary note.
  7. nearby_false_description_or_wrong_definition_episteme = an evidence/work claim or a different routed-quadrant statement mistaken for the governing admissibility description.
  8. first_admissible_entry_stop_or_reroute = the reader can now say “this is the admissibility description to inspect first”; if the reader needs to classify the boundary claims, inspect A.6.B.