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

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:55:17 UTC

A.6.RSIG:4.1 - Recognition-cue discipline and non-goals

A.6.RSIG governs description-recognition signatures in general: the first-contact cue structure by which one reader can recover what encountered description is live, what carrier or projection exposed it, what it applies to, what excludes it, and which definitionEpistemeRef identifies its defining U.Episteme. Reject a nearby reading or wrong defining U.Episteme only when it passes F.19’s grounded-guard test: the rejected reading has an independent local ground, is plausible for the intended reader, and changes truth, understanding, selection, safety, stop, reliance, or action. Use the smallest clear correction; do not invent an alternative to fill the cue shape.

Here “description-recognition signature” is a lower-case authoring and reading discipline, not by itself a typed U.Signature or a new formal kind. A typed declaration requires the applicable neighboring pattern’s explicit conditions.

The encountered carrier or projection may help recognition; it does not become authoritative merely by being encountered.

Use definitionEpistemeRef for the defining U.Episteme. If the definition is available only through one publication, cite separately the exact E.24.PUB publication occurrence that makes it available; the publication, projection, or carrier does not become the defining episteme merely because it exposed the definition to the reader.

A.6.RSIG does not govern:

  • general information architecture or search UX;
  • documentation layout or publication-face selection;
  • pattern-entry discoverability across a pattern language;
  • the full semantics of the description itself;
  • lexical repair, alias acceptance, or naming governance as such;
  • graph ontology, workflow sequencing, or runtime route semantics.