E.11:4.5.1 - Preface, local recognition, and first-entry terminology
The Preface explains why the README entries are credible. It uses plain engineering language before FPF vocabulary and narrates the cross-cutting ideas once rather than copying the scenario set. Its coverage includes transdisciplinary use without collapsing local meaning; local closure in an open world; holons, systems, epistemes, and architecture as structure; EntityOfConcern and description/publication/view separation; thinking-through-writing; epiplexity; first-principles-to-work; mathematical lenses and FormalSubstrate distinctions; ontology-first wording repair; evidence/assurance/gate/decision/work separation; characteristic spaces, quality, NQD/OEE, and improvement; novelty, diversity, and SoTA; and didactic primacy. A strict FPF term that carries the explanation receives an immediate plain gloss. Pattern IDs are addresses for stricter treatment, not the main explanatory language.
A pattern’s own Problem frame is the local high-precision recognition section. It makes recoverable the primary EntityOfConcern, working problem, failure if missed, first admissible action, practical result, and ordinary non-use boundary. Add candidate-pattern comparison only when a real discoverability ambiguity exists; otherwise keep cross-pattern comparison in README, ToC, Relations, or an expanded case.
Keep these terms stable:
| Term | Use |
|---|---|
first entry | General entry from a working project or FPF artifact into the corpus. |
first practical entry | Public form selected by a real working question. |
first-entry scenario | README prose that starts from a recognizable question and names a first useful result and direct pattern family. |
first-entry cue | A phrase, query row, heading, compact locator, or local recognition passage that helps recover a direct pattern. |
first-entry pattern-comparison set | A small case-relative set used only when the first choice is genuinely ambiguous; it is not a standing index. |
expanded entry-disambiguation case | A longer case used only when README, ToC, and local recognition are insufficient. |
ToC and lexical-query phrases remain finding aids, not alternate names, semantic equivalences, or authority relations. A projection that needs to answer a substantive claim must return to the direct pattern or the pattern for that claim; do not strengthen the projection.