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

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

E.10.ARCH:2.1 - EntityOfConcern and recurring hidden-field distribution

For wording such as EntityOfInterest, EoI, EoIClass, describedEntity, DescribedEntityRef, and primary described entity, or for selected EntityOfConcern-family heads such as EntityOfConcern, entityOfConcernRef, EntityOfConcernRef, EntityOfConcernClass, and publicationUnitPrimaryEntityOfConcern, the repair is distributed by the current FPF-governed use:

EntityOfInterest, EoI, EoIClass, describedEntity, DescribedEntityRef, and primary described entity are active repair triggers. FPF-governed wording must recover the EntityOfConcern-family use named by value, publication-unit primary-EoC or ordinary primary-subject use, or local FPF kind, then rewrite to EntityOfConcern, entityOfConcernRef, EntityOfConcernRef, EntityOfConcernClass, publicationUnitPrimaryEntityOfConcern, publicationUnitPrimarySubject for the E.17.AUD.OOTD primary-subject use, or the local FPF kind named by value. For the non-claim-bearing case, use the kind named by value or plain topic or subject without inventing an EntityOfConcernRef. If no use is recoverable by value, the wording remains quoted source or trigger wording and cannot be used for reliance.

  • C.2.1 defines episteme identity and the identified EntityOfConcern participant of EpistemeConstitutionRelation; A.6.5 defines EntityOfConcernSlot only inside a reusable constitution RelationSignature; direct reference rules define or constrain entityOfConcernRef, EntityOfConcernRef, and related reference use.
  • C.2.P carries episteme, publication, source-wording, and source-relation precision restoration when the sentence still hides source wording, claim-bearing episteme, publication construction, publication-form construction, project-side reliance, pattern-application wording, or use or non-use disposition.
  • F.18 carries durable naming, selected head settlement, and source-string and durable-name discipline after the kind under repair and use are recovered.
  • C.2.P defines and E.17.AUD uses the union field publicationUnitPrimaryEntityOfConcern: the carried EntityOfConcern or the non-claim-bearing kind, topic, or subject value. E.17.AUD.OOTD governs its separate local publicationUnitPrimarySubject for one bounded publication unit with one carried move and one outside-work boundary. Only when the unit carries one identified episteme E and the subject is the exact entity that its claims concern may publicationUnitPrimarySubject = EntityOfConcern(E) be stated. Neither field adds a participant to EpistemeConstitutionRelation, and the fields are not aliases.
  • A.6.3, its retained entityOfConcernRef-preserving specializations, and A.6.4 carry preservation or retargeting of the EntityOfConcern across episteme morphisms.
  • When an evidence, assurance, gate, work, decision, architecture, characteristic, mathematical-lens, or project-side claim is already recoverable, use the rule that defines or constrains that exact claim or its admissible-use boundary.

This selected-family case is the standing example for recurring hidden-field architecture. When a new hidden-field family recurs, do not add local warning prose to every pattern. Use an existing defining or testing rule when one fits, add one applicability row when shared recovery is needed, and justify a new realization pattern only when the hidden field set, recovery apparatus, and remaining reader use recur across FPF-governed texts.