U.Episteme | Claim-bearing episteme or episteme species. Use when the value is a claim-bearing episteme that can be described, viewed, grounded, revised, published, or relied on under FPF. | File, paragraph, screen, carrier, status note, process state, or generic “content”. |
| C.2.1 episteme constitution and neighboring relations | An exact episteme is identified through claim content, one exact EntityOfConcern, and one effective ReferenceScheme under EpistemeConstitutionRelation. Empirical grounding is a separate EpistemeEmpiricalGroundingRelation; describing-use viewpoint selection, E.17.0 conformance and same-individual U.View membership, C.29 representation, and publication or carrier relations are also separate. SlotKinds occur only inside the exact reusable RelationSignature that declares their participant meanings. | One universal episteme-slot tuple, card, field family, or context container. |
EntityOfConcern, EntityOfConcernRef | The EntityOfConcern participant under C.2.1 and its applicable reference for a claim-bearing episteme or episteme-lane U.View. The participant may be an entity, relation, FPF pattern, FPF publication, project episteme, project publication, a project-side entity identified by its FPF kind and reference, work or action when that work or action is itself the entity of concern, or another explicitly typed EntityOfConcern referent. Use this when the text is really about what the episteme is about. In publication-unit work, EntityOfConcernRef is used only through a claim-bearing episteme or episteme-lane U.View; it does not float as a free field on the unit. | Generic topic, local table subject, file title, reviewed publication, review packet, or review record, required project-side work, decision, action invitation, authoring work, or anything someone happens to talk about by default; the episteme’s constitution must identify the exact entity as its EntityOfConcern before this reference is used. |
wording such as describedEntity, DescribedEntityRef, primary described entity | Use the exact EntityOfConcern participant and its applicable reference under C.2.1 when a claim-bearing episteme is current. Use publicationUnitPrimaryEntityOfConcern when one bounded PublicationUnit carries or exposes a claim-bearing episteme or same-individual U.View and the primary entity of concern must be named. | A second C.2.1 slot family, a free publication-unit field, a generic topic, a second current name, or a new ontology beside EntityOfConcern. |
publicationUnitPrimaryEntityOfConcern | The primary entity of concern, non-claim-bearing kind named by value, topic, or subject that one bounded PublicationUnit is mainly about for the current use. When a claim-bearing episteme or episteme-lane U.View is current, this must be recoverable from the selected EntityOfConcernRef; otherwise name the non-claim-bearing kind named by value or keep topic and subject as plain explanatory prose. | EntityOfConcernRef created without a claim-bearing episteme or episteme-lane view, publication-unit title by default, authoring process, carrier identity, or reader interest. |
GroundingHolon, empirical-grounding relation | The exact grounding holon and obtaining C.2.1 EpistemeEmpiricalGroundingRelation that maps named empirical claims of one exact episteme to the required direct observation, intervention, measurement, or test relations. | A constituent of episteme identity, a convenient source citation, an untyped entity mention, or the declaration-local GroundingHolonSlot used as the world-side value. |
U.View, U.EpistemeView | Same-individual dependent membership of one already identified episteme when an exact E.17.0 EpistemeViewpointConformanceRelation to at least one exact viewpoint episteme obtains. A.6.3 source-to-receiving construction, describing-use viewpoint selection, publication, form, and carrier remain separate. For an episteme published through an MVPK face, this membership requires the same E.17.0 conformance; the publication form remains separate under E.17. | A UI view, reader viewpoint, screen, generic publication face, projection by default, or new claim-bearing episteme by membership alone. |
Viewpoint | One exact U.Viewpoint episteme used as the viewpoint participant of an E.17.0 conformance relation or selected for one named describing use. Selection does not prove conformance or U.View membership. If source wording says “system in role,” use E.10.ROLE and recover the exact concern, object, local system-role kind, classification judgment, participant relation, or assigned System by value. | A reader opinion, episteme-identity slot, pattern-application order, publication label, carrier label, or assignment manufactured by the viewpoint phrase. |
| publication | A publishable episteme, view, record relation, act or occurrence of publishing, or publication form, depending on sentence function. Always split by kind before use. | Generic document, any public-looking file, or proof that a claim is authorized. |
U.EpistemePublication (rejected spelling) | No durable kind. Recover the claim as the selected U.Episteme, an EpistemePublicationRelation occurrence or reference when availability matters, publication form, or U.PresentationCarrier, according to sentence function. The spelling may remain only in this rejection explanation or a negative test. | A positive object, kind, reference, field, publication identity, or carrier identity. |
| publication form | The typed form in which an episteme, view, or record is published. | The claim-bearing episteme itself, the face rendered for a reader, or the carrier holding bytes. |
| generic publication face | Reader-facing publication projection or face. Keep it distinct from the selected episteme; U.View membership of that episteme requires exact E.17.0 conformance. | U.View by default, carrier, UI face, front-end display, MVPK face under E.17 constraints, or claim-bearing episteme. |
| MVPK face under E.17 constraints | An E.17 publication form published under MVPK constraints from a source episteme or episteme-lane view, with publication viewpoint, scope, pins, and face kind. Its selected source or receiving episteme may be a U.EpistemeView when the exact E.17.0 conformance relation obtains. | Generic publication face, carrier, UI face, front-end display, or proof of evidence, work, gate, or authority by presentation. |
| carrier, front-end, rendering | Publication-side or access-side bearer or display relation. Use U.PresentationCarrier under E.17 and E.24.PUB when that exact carrier is current; otherwise name the file carrier, transport carrier, rendering, front-end relation, access-carrier relation, or another carrier relation by sentence function. | Episteme identity, publication form, U.View, proof of evidence, or authority-reference relation. |
PublicationUnit | E.17.AUD-cluster head for one bounded unit inside a publication that a person inspects as one unit: a pattern body, section, table, note, card, sheet, screen block, or another bounded publication unit whose boundary is named. A card, sheet, or screen block counts only when its boundary is inside a named publication or generic publication face and the sentence needs that bounded unit as the inspected publication unit. It is part of or bounded by the publication face that renders or locates it, whether that face is generic or published under E.17 and MVPK constraints. It may carry or expose a claim-bearing episteme, view, record, cue, or local rendered content when that carried value and relation are named, but it is not identical with the carried value. | Authoring process, review work, file, carrier, front-end, UI behavior, dashboard behavior or export behavior, whole publication architecture, U.Episteme, U.View, publication form, generic publication face, MVPK face under E.17 constraints, or “anything written”. |
| project-side FPF kind and reference named by value | Evidence record, gate record, Work record, status record, commitment record, system-role-assignment record, decision record, selected source U.Episteme, EpistemePublicationRelation occurrence reference when availability matters, status-register entry, or another project record whose FPF kind is named. | Semantic content in general, current process state, or a free-form note. |
| source document | A document named for source-use, evidence use, architecture use, or review use. Name that document use directly. | A governing source by folder proximity, the EntityOfConcern carried or exposed by that source document, or the authority-reference relation unless that relation is explicit. |
| reviewed publication, review packet, or review record | The reviewed publication named by value, review packet, review record, or bounded publication unit sent or inspected in review. | The EntityOfConcern carried or exposed by that reviewed publication, review packet, or review record, the source relation behind it, or a packet-local summary. |