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 07:40:10 UTC

E.10:0.0a - One-screen cue and route

  1. Read one complete sentence, row, paragraph, list, or small coherent section rather than classifying a word in isolation.
  2. Apply the connected F.19 reading. If ordinary meaning settles the issue, write the repaired text and reread the changed sentence with only its meaning-dependent neighbors.
  3. If an FPF wording question remains, name that one question: head or kind, register, morphology, durable name, direct relation and participant, reusable declaration, claim or report, representation, source or publication use, or another exact governed object.
  4. Use the applicable subject pattern directly when the object and claim are already recoverable. Use the detailed E.10 rows only for the selected lexical question. Open E.10.ARCH when the distinction among a world-side fact, reusable declaration, claim or report, and representation is itself unresolved.
  5. Check the replacement for another umbrella head, an unintended kind or scope change, and a newly introduced relation. If one remains unresolved, state the blocker instead of filling the sentence with possible interpretations.

A complete reading can preserve clear conversational wording or an exact locally defined meaning. Where something remains unresolved, distinguish a sentence repair under an existing rule, a needed distinction or relation for which the defining rule is absent, and facts still missing to decide the meaning or claim. Unavailable facts do not establish an ontology gap. An applicable pattern supplies its stated rule; its presence does not prove that every encountered case is covered.

The ordinary result is retained or repaired text, or a specific blocker. E.10 requires no per-correction card, field set, concordance row, or classification receipt. A using environment may manage attention over a large text, but that mechanism is outside this language pattern.

Common prose can often remain ordinary after the relation is stated: Test T is evidence for claim C; Index I helps readers find section S; Column C bears roof R's load. These sentences reach different subject patterns and do not need a common SupportRelation.

Local patterns may cite a useful recognition row. They do not copy the trigger inventory or create a local lexical registry unless a stable local vocabulary is itself the governed product. Self-application remains bounded: use E.21 for pattern-quality evaluation and the exact subject pattern for any non-lexical claim.