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

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

E.8:4.2.2 - Package-form and neighboring-pattern reference discipline

FPF package-form words and neighbouring-pattern references carry stable meanings. State the actual relation used by the sentence, and use the exact subject pattern when that relation is not recoverable from ordinary wording.

For an ordinary neighbouring-pattern reference, state the concrete contribution and cite the PatternID. An identifier or locator only helps the reader find that content. Identify an exact claim-bearing episteme, ClaimGraph, edition, or relation assertion only when a named later use depends on that identity.

A local ...PatternLocator field may remain where an existing schema already uses it as a non-semantic convenience, but ordinary prose and entry cues do not require one. It never substitutes for the cited content’s concrete contribution or, when the stronger identity branch is active, for the exact claim-bearing content. Changing only a locator without changing what it resolves is a representation change; changing the defining content or exact assertion may reopen the semantic object whose receiving use depends on it.

Keep the following package and relation words distinct:

  • pattern reference = an ordinary citation to content whose concrete contribution is stated in the current sentence;
  • specialization = an exact relation in which the child carries the required parent content plus an explicit child delta and use boundary;
  • overlay = a cross-cutting reading or review projection over stated source content; it adds no authority or obtaining relation by name;
  • profile = a declarative bounded-use or review projection from stated source content, not a replacement pattern or actor;
  • family = a recurring class of cases under an explicit membership rule, not a hidden common owner;
  • bundle = a packaged set of defaults, allowances, or coordinated members whose actual relations remain explicit;
  • cluster = a navigation or reading-order grouping, with no semantic relation by grouping alone;
  • suite = a coordinated set whose suite-level membership and coordination semantics are explicitly stated;
  • pack = an editorial, source, review, or delivery grouping, not semantic authority;
  • kit = a reusable coordinated publication or boundary-description package with exact kit-level membership and use;
  • record = a case, report, assertion, representation, or review record under its own identity;
  • umbrella = a provisional review head spanning possible subfamilies before an exact membership rule and the relevant claims and relations are settled.

These words are not interchangeable and do not stand in for a missing relation. Say specialization of … with delta …, profile projecting … for use …, overlay reading …, bundle containing … under membership rule …, or another exact formulation. A source-defined position name may be reused when the cited content defines that position and the current assertion uses it in that sense; otherwise recover the meaning through E.10.ROLE and do not improvise near-synonyms for stylistic variety. The preceding receiving-use discriminator decides whether exact claim-bearing content must also be identified.

E.8:4.2.2.1 - Precision-restoration placement discipline

When a pattern or companion text is drafted from E.10 or E.10.ARCH, distinguish three authoring objects:

  • semanticArea is the Part-F semantic unit for a wording-use restoration row: one Concept-Set row, one UTS row, or an explicitly bounded row-set. It is declared with semanticAreaBaseConcept and semanticAreaSenseFamily.
  • ontologicalNeighborhood is the applicability neighborhood around that named semanticArea: nearby primary EntityOfConcern kinds, relation kinds, claim records, content that defines or constrains the current use, non-use boundaries, and remaining reader use that can carry the recovered meaning after the wording is repaired.
  • pattern nest is the publication and specialization placement of a pattern under a declared family or membership relation.

These are not synonyms. A precision-restoration pattern is placed in the pattern nest whose primary EntityOfConcern, relation record, or claim record it repairs. Its semanticArea states the Part-F semantic unit it repairs, while its ontologicalNeighborhood may name several direct relations and pattern content that defines or constrains the asserted uses. For example, quality-term repair lives in the C.16 characterization nest, even though its neighbouring relations can include relation construction, action invitation, evidence, assurance, source-use assignment, engineering quality bundles, pattern-quality evaluation, or mathematical-lens use.

Affected patterns should use a thin pointer when the first-stage wording repair belongs elsewhere. The pointer names the selected restoration pattern and the condition that triggers it; it does not copy the trigger registry, the full E.10.ARCH recovery algorithm, or a second local architecture for the same repair. The affected pattern then keeps its own subject matter: the characteristic, structure, view, episteme, relation, evidence, assurance, gate, work, decision, or adequacy question it already governs.

If a draft proposes a new precision-restoration pattern, the authoring claim must show the repeated wording failure, semanticAreaBaseConcept, semanticArea, semanticAreaSenseFamily, the recovered primary EntityOfConcern kind or relation/claim record, the intended pattern nest, the neighboring governing relations, and the admissible action left after repair. A new pattern is not justified merely because a word appears often, because a local checklist wants a bucket, or because a campaign needs a tidy grouping.