C.2.P - Clarify Episteme, Publication, and Source Wording (Epistemic Precision Restoration)
Type: C.2 precision-restoration pattern for episteme, publication, source wording, and source-relation wording Status: Stable Normativity: Normative unless a section is explicitly informative
C.2.P:0 - Use this when
Use C.2.P only when one unresolved distinction prevents the reader from selecting or safely using the direct pattern. The unresolved point must concern a source expression, claim-bearing episteme, publication, publication unit, view, carrier relation, source-to-use relation, or use disposition.
Recognizable situation. A sentence is readable, but it leaves the reader unable to tell whether it refers to claim content, a publication or bounded unit, a carrier or display, a source-bearing relation, or a project-side use of one of those objects.
First useful move.
- Say what the sentence is doing: defining, claiming, instructing, comparing, locating a source, describing a publication, or supporting a project use.
- Recover the one unresolved episteme, publication, source-to-use, carrier, or use-disposition distinction.
- Rewrite the sentence, or hand the remaining claim to the pattern that defines, constrains, or tests it. Then stop.
Not this pattern when. If the receiving pattern and its field at issue are already recoverable, apply that pattern directly. A clear ordinary phrase needs no C.2.P record. Use A.6.P for a relation problem whose publication or source-expression side is already clear, F.18 for a stable reusable name, A.7 for EntityOfConcern-description-carrier separation, E.17 for reader-facing publication of an accepted account, and E.24.PUB for publication-occurrence, form, or carrier distinctions.
Smallest outputs.
- Direct repair: the repaired sentence. Add a reason or non-use boundary only when it changes interpretation or action. No record.
- Compact row: the exact sentence, its function, one recovered kind or relation, the selected wording or disposition, and the reader’s remaining use.
- Full check: only when several recovery fields interact, a source-to-FPF use is contested, or a reusable ontological or naming decision is being made.
- Other outcomes: reduced-use cue, blocked use, incomplete rewrite, or not triggered.
Changing an FPF pattern is not by itself a reason to use the full check. Use the cheapest product that preserves the needed distinction.
Source-expression boundary. External or ordinary prose may be clarified without forcing all of its vocabulary into FPF. If no FPF-governed use is recoverable, keep the phrase as source-local wording, a source-finding cue, or a blocked claim-bearing use.
Source-to-use continuity. Do not close a repair merely by replacing the word source. Name the source expression or selected source episteme, the publication occurrence only when availability matters, the relation or path that carries it into the current use, the permitted use, and the condition that requires return to the source. Keep physical raw material with its constituent, resource-use, supply, transfer, or transformation relation.
Ordinary-language survival. Words such as source, view, support, route, and display may stay ordinary when they make no FPF kind, relation, authority, evidence, gate, work, decision, or reliance claim. Repair by sentence function and consequence, not by trigger word.
What this buys. The practitioner recovers the one distinction that matters without building a second ontology or a second review procedure. The final wording still tells a cold reader what to do and where to stop.
C.2.P:0.1 - What goes wrong if missed
Episteme-publication-heavy text starts to build a parallel ontology. A generic publication face becomes a U.View, a file becomes an episteme, a dashboard tile becomes evidence, a pattern name becomes a procedure, or a slash list becomes a group kind. A broad word such as source can hide several different recovery fields: an FPF pattern or DRR; a publication field; a document named for source, evidence, architecture, or review use; a reviewed publication, review packet, review record, or review state; a project-side FPF kind and reference named by value; or a relation.
The immediate cost is that engineers and FPF authors start making action, evidence, gate, decision, or engineering-justification claims from the wrong entity, publication, record, relation, or carrier.
C.2.P:0.2 - What this buys
C.2.P gives one small epistemic precision-restoration move: recover the FPF kind and relation set first, then write wording that preserves the needed distinction without adding another claim. It prevents string-replacement cleanup, keeps FPF-side and project-side episteme and publication work separate, and blocks unclear wording from having FPF-governed use by guesswork.
Successful repair condition. Type-correct wording is not enough. A repair must satisfy the E.2 Pillars, especially P-2 Didactic Primacy, together with E.12 and the register rule in E.10:6.2. It closes only when the text preserves or restores a usable action, a recognition reason that tells the working reader why the distinction matters, or a named FPF pattern application that carries the claim.
When Tech and Plain registers are both current, the Tech interpretation remains recoverable and the Plain or didactic line maps back to it. An ordinary or metaphorical Plain line may stay light when it carries no FPF-governed use; if it carries an ontological, evidence, causal, assurance, bridge, gate, work, decision, or use-boundary claim, that claim must be recoverable through the Tech fields, named FPF kind, recovered relation, project-side reference, or disposition.
A repair to a Problem frame, recognition text, example, or worked slice is incomplete if it improves typing but hides the working situation, why it matters, or the first useful action; name the applicable FPF pattern when that pattern carries the claim. Preserve the remaining action guidance as well as the recovered meaning.
Recovery focus in plain terms. The use being made is one episteme-publication-heavy wording use inside conformant text: the word or phrase, the sentence function it carries, the FPF kind or relation it must recover, and the remaining declared use boundary after recovery.
Primary working user. The first user is a practitioner maintaining conformant FPF-style or project text: an author, reviewer, or engineer-manager who must repair wording without losing ontology. The downstream user is the practitioner who will rely on the repaired pattern or project text in a working situation.
Practical payoff. State what the repair lets the reader distinguish or do, and any remaining question that requires another named FPF pattern. Explain a rejected reading only when F.19 establishes an independent ground, a plausible intended-reader interpretation, and a consequence for truth or use. If the repair blocks a false claim, retain the useful remaining statement or state the blocked use.
C.2.P:1 - Problem frame
FPF already has episteme, publication, view, carrier, presentation, relation, naming, and pattern-application concepts. FPF-governed project, review, draft, pattern, and architecture prose, plus source prose being unpacked for possible FPF use, can still introduce convenient intermediate words that survive into final guidance without their kind and relation set recovered.
The recurring situation is simple: a sentence is understandable enough to feel worth keeping, but its head kind is not recovered. If it is repaired by replacing one broad word with another broad word, the ontology gets worse while the text looks cleaner.
C.2.P:1.1 - Purpose and Scope
This pattern gives the current glossary and rewrite rules for terms around epistemes, publications, views, publication forms, generic publication faces, MVPK faces under E.17 constraints, carriers, records, and bounded publication units.
It exists because episteme-publication-heavy texts can use locally convenient heads that collapse EntityOfConcern, publication unit, publication face, carrier, record, source relation, and project-side FPF kind and reference. Those words may be useful recognition handles, but they are not safe FPF heads when they carry ontology, authority, or authority-changing meaning.
The rewrite discipline here is ontological and use-facing, not lexical; in this pattern the repair is bounded to episteme, publication, source wording, and source-relation precision:
- do not replace one broad token with one new broad token by string substitution;
- first recover the FPF kind and relation set, whether the wording carries a claim, the publication, view, carrier, or relation construction, and any work, action, or authority crossing;
- then choose the smallest wording that preserves the FPF-governed distinction without creating a second ontology.
For FPF-governed wording, use the E.10 cues and routes within the connected F.19 reading. C.2.P works in the C.2.1, E.17, and E.24.PUB epistemic-publication ontology rather than in a lexical registry.
C.2.P:2 - Problem
Without an epistemic precision-restoration discipline for episteme-publication-heavy wording:
- broad publication words hide which field family is current: episteme or view, publication form or face, bounded publication unit, carrier relation, named document use, review-state use, or project-side FPF reference;
- FPF pattern-application claims and project-side fields for work occurrence, work plan, decision, action invitation, method, record, carrier relation, or front-end relation get mixed in one sentence;
- slash lists and heterogeneous rows become false group kinds;
- unclear source meaning is guessed into FPF-governed wording rather than blocked or assigned to an accepted FPF extension;
- authors copy the same loose wording into
DRRs, patterns, source-relation notes, source-ref target notes, or project texts.
C.2.P:3 - Forces
| Force | Tension |
|---|---|
| Precision vs readability | FPF-governed wording needs kinds named by value, but a sentence overloaded with every possible kind becomes unreadable. |
| Preservation vs cleanup | Accepted source text or accepted governing text must not be paraphrased away, but source-companion statement cannot be mistaken for pattern authority. |
| Local repair vs new ontology | Many phrases need only an ordinary sentence or one direct subject pattern; a real missing kind or relation may require separate development. |
| FPF-side vs project-side work | The same word can describe FPF pattern authorship or a user’s project publication, record, work, or action. |
| Guidance vs audit | The pattern must tell authors what to do, while check rows only verify that the rewrite was carried out. |
C.2.P:4 - Solution
Repair episteme-publication-heavy wording by epistemic precision restoration, not by dictionary replacement.
A successful rewrite satisfies these field-validity constraints:
-
the head kind and sentence function are recoverable under
E.10; -
a stable reusable name has an
F.18naming result; -
a relation, comparison, dependency, support, sameness, grounding, mapping, or endpoint claim has
A.6.Prelation precision, with use-boundary and project-side reliance questions split into their own fields; -
a claim-bearing episteme has a recoverable
C.2.1identity; dependent-kind membership, such asU.View, uses its defining pattern. A project-side object or relation keeps its own kind, applicable reference, and declared use; -
publication, view, face, and carrier distinctions satisfy the applicable
E.17.0view-conformance,E.17/MVPK publication-face, andE.24.PUBpublication-occurrence, form, and carrier rules; -
the repaired text satisfies
E.2Pillars, especiallyP-2 Didactic Primacy, by preserving or restoring one remaining reader use: a usable action, a recognition reason that tells the working reader why the distinction matters, or a named FPF pattern application that carries the claim.When both Tech and Plain registers are current, the Plain or didactic line maps back to the recovered Tech kind, relation, or FPF pattern application under
E.10:6.2.Ordinary Plain wording and intentional didactic metaphor stay light when they carry no FPF-governed use, but ontological, evidence, causal, assurance, bridge, gate, work, decision, or use-boundary claim in a more expressive Plain line must be recoverable through the repaired Tech fields.
FPF-governed Problem frames, Problem sections, recognition texts, examples, and worked slices must still show the broad working situation and first useful move, or the rewrite is incomplete.
-
the final phrase preserves the distinction without adding another claim;
-
unrecoverable meaning, kind, register mapping, or remaining reader use fails closed.
C.2.P:4.0a - Progressive recovery products
An ordinary application ends with the repaired sentence. Add a reason or non-use boundary only when it changes interpretation or action; no record is required.
Use a compact row only when another reader must later inspect the recovery:
Compact epistemic precision-restoration row:
exactSpanOrSentence:
sentenceFunction:
recoveredKindOrRelation:
selectedWordingOrDisposition:
remainingReaderUse:
Add a source identity, publication occurrence, carrier relation, declared-use boundary, project-side reference, naming decision, evidence relation, or assurance reference only when that claim is live. Optional fields do not become a common schema.
Use a full check only when several unresolved fields interact, the source-to-FPF use is contested, or a reusable ontological or naming decision is being made. Record the original sentence, its function, the selected kinds and relations, the neighboring-pattern contributions, selected wording, remaining reader use, and reopen condition. Record competing interpretations or rejected overreads only when they are independently grounded, plausible for the intended reader, and consequential under F.19. Omit unused fields.
When the wording exposes a field defined elsewhere, name the contributingPattern and the concrete definition, constraint, or test it supplies.
Carrier-specific recovery. Words such as carrier, file, dashboard, screen, front-end, and rendering are recognition cues. First say what the carrier is being used for. If the next pattern is not already clear, use the compact category-to-contribution route in §4.1.3 for publication, evidence or currentness, generated results, framework packages, Work or reliance, architecture or structure, and base or support questions. Do not close on the word carrier alone.
C.2.P:4.1 - General Recovery Check
Run this check only while one C.2.P distinction remains unresolved.
- Name the sentence function. State what the sentence would let a reader claim or do.
- Recover the blocking distinction. Read the expression using its governing conventions. In a filled table, use the headings, units and applicable key to recover what one row asserts. A missing convention matters if two readings would classify the item differently or change the action. Obtain that convention or the deciding fact, or retain both readings. A.6.P can resolve a remaining question about the relation. Stop here if the recovered assertion answers the reader’s question. Use C.2.P.DR when someone infers a further classification, operation or result from how the expression looks.
- Select the next result. Rewrite directly, write the compact row, perform the full check under its material conditions, or return a non-use result. If another pattern now supplies the needed definition, constraint, or test, name that contribution and stop C.2.P.
Fail closed when the kind, relation, use, or remaining reader action cannot be recovered. A type-correct sentence that no longer shows the working situation or useful action is an incomplete rewrite.
C.2.P:4.1.1 - Slash Discipline
In conventional abbreviations, source titles, mathematical notations, standards, URLs, file paths, and ordinary notations, a slash can be part of an accepted designation rather than a hidden FPF kind. In FPF-facing episteme and publication ontology, a slash is still a recovery trigger before it is a synonym marker unless the mark is part of such accepted notation, carrier syntax, or conventional designation.
Before leaving a slash expression in current prose, classify the expression as one of these cases:
- accepted notation or conventional designation: keep established names, mathematical and unit notation, file paths, URLs, and quoted source tokens whose slash belongs to the designation or carrier syntax. Examples include
ISO/IEC,ISO/IEC/IEEE, and1/2; - a plain-language synonym pair with no ontology, authority, evidence, or use-boundary claim;
- an unresolved
and/or-style join that must be split or recovered before FPF-governed use; - a proposed composite kind: establish its meaning under the kind’s subject pattern; use
F.18only for a durable reusable name andA.6.Pfor an unresolved relation; - a relation claim: recover the direct predicate, its participants, and its defining pattern; use
A.6.Ponly while one of these remains unclear, then use the direct subject pattern. Add declaration, occurrence-identity, qualification, or representation detail only when the receiving use needs it; - a tuple-like record: state the record’s purpose and component meanings; use
A.6.5SlotSpecs only for a reusable typed declaration that needs them; - a failed ontology signal where the sentence lists unlike values because the FPF kind under repair, relation record, relation phrase, tuple-like record, alternative-case disposition, or not-triggered disposition has not yet been recovered.
If the expression is not one of the safe notation, conventional-designation, carrier-syntax, quoted-source, or plain-language cases, do not keep the slash as final wording. Do not repair it by replacing the slash with one equally vague grouped word. Write the recovered FPF kind, relation record, relation phrase, tuple-like record, alternative-case disposition, or not-triggered disposition by value.
C.2.P:4.1.2 - Unclear Source Meaning and FPF Extension Candidates
Sometimes the problem is not a bad word but one of two different cases:
- the intended claim cannot be determined from the surrounding source, current
FPFkinds, or current FPF episteme and publication ontology; - the claim is understandable, but current
FPFdoes not yet contain the kind, pattern, relation record, or method guidance needed to carry it.
Do not merge those cases.
An unclear claim is not current architecture truth merely because deleting it feels risky, and it must not be rewritten by guessing a likely author intention.
An understandable uncovered claim may be retained as a candidate FPF extension when the problem situation, current FPF gap, and first user action that would improve are stated. State an overread or rejected use only when it has the independent ground and practical consequence required by F.19.
Classify the case explicitly:
- recovered by value: the sentence names the object or relation, its defining or constraining pattern, and the declared use. When it uses
projectSideFPFRef, recover the exact project-side kind and reference described in :4.2.1. Stop at the selected value and the relation needed for that use; - understandable FPF extension candidate: the thought is clear enough to state as a candidate new or amended FPF kind, pattern, relation record, method guidance, accepted
DRRcontent decision, or campaign-scoped content question, but it does not carry current authority, evidence, or use-boundary claim until an accepted architecture decision, acceptedDRR, or accepted FPF pattern supplies that authority; - source wording without FPF-governed use: the phrase has no current authority, evidence, or use-boundary claim;
- reduced-use cue: the phrase is kept only as a recognition cue or anti-case, not as a claim-bearing architecture decision;
- blocked use: the phrase is blocked for claim-bearing architecture, pattern, or project text while the needed meaning, kind, or relation is missing.
- rewrite incomplete: the repaired wording may be kind-correct, but it does not yet state a remaining reader use, recognition reason, Tech-to-Plain mapping when both registers are current, or FPF pattern application, or a Plain or didactic line carries ontological, evidence, causal, assurance, bridge, gate, work, decision, or use-boundary claim that cannot be recovered from the Tech interpretation; continue repair or demote to a non-use disposition before the text has FPF-governed use.
These dispositions are recovery results, not a meta-governance authority over all of FPF.
When recovery names another FPF kind, use the pattern that defines or constrains that kind, its declared use boundary, and its conformance checks.
After that identification, C.2.P no longer defines or constrains the recovered kind.
C.2.P only makes the kind under repair, relation, and use boundary explicit enough to apply the appropriate pattern.
No other disposition is closed. In particular, “seems to mean”, “probably about”, a cleaner paraphrase, or a broad umbrella replacement is not a successful recovery.
C.2.P:4.1.3 - Keep source, return, work, and next-pattern questions separate
When source data or source material is epistemic, identify the source expression and selected source episteme. Add a publication occurrence only when availability matters. Then name the relation or path that carries the source into the current use.
Treat source-use as a cue, not as a relation name. Do not call an endpoint value unless the direct pattern declares a value slot.
If the wording also makes a claim about a Method, Work, transformation, evaluation, transfer, or receiving use, use its direct pattern. Use A.6.P.WMR only while the work-side relation or what is being claimed about it remains hidden. Physical raw material stays with its constituent, resource-use, supply, transfer, or transformation relation.
Use source-return only for a reverse or escalation move from a derivative, coarsened, extracted, compressed, rendered, or reused object to a named source. Such a move is current when a stronger use, dispute, freshness change, hidden loss, or missing distinction requires the source again. For ordinary movement from a source into current use, say source-to-use path or name the relation. Name a rule-bearing ClaimGraph only when later comparison or reuse depends on the identity of that rule.
C.2.P does not decide whether Work may proceed. Use A.15.4 only after the wording repair shows that a publication, display, or other appearance is being relied on as a reason for intended Work and the exact project-side object or relation is still unresolved. If the direct pattern is already known, use it without an intermediate reliance-repair branch.
Once the remaining question is clear, stop C.2.P and choose the direct branch:
A.6.Pfor relation precision;F.18for a reusable name;C.30.Pfor a hidden architecture or structure distinction;C.16.PorC.16.Qfor a hidden characteristic, scale, or evaluative-quality distinction;- the applicable episteme or publication pattern for an already identified episteme or publication question.
These branches are alternatives. C.2.P may expose a naming or authority question, but it neither renames an accepted FPF pattern nor admits a reusable head; use F.18 and the applicable accepted decision source for that change.
Carrier-like words are only recognition cues. Once the category is clear, use one row below and stop C.2.P as soon as that contribution closes the question.
| Recovered category | Use the contribution that answers the remaining question |
|---|---|
| Publication occurrence, form, face, presentation carrier, rendering, or availability | Use E.17 to select a source-backed face of an already accepted account for a named reader and use; use E.24.PUB when publication-occurrence identity, form, carrier, audience, bounded use, or availability matters. If the claim is that access actually occurred, use the pattern for that access relation; availability alone does not establish access. |
| Evidence, provenance, or currentness | Use A.10 for one claim-bound evidence-provenance path and bounded reliance. Use G.6 only when later citation or replay needs an addressable path through several already established objects and relations. Use G.11 when staleness or refresh of a source, edition, evidence set, dashboard, or carrier is the live question. |
| Generated or discovered result reached through a carrier | Use C.35 to decide whether the exact result may seed architecture work. Use E.24.PUB for its publication occurrence and carrier, and E.17 when publishing reader-facing forms of the accepted account. C.35 admits or rejects the result, not a generic “generated carrier”. |
| FPF, DPF, or LPF edition, package carrier, or access carrier | Use E.4.FPF for FPF form and publication- or access-carrier assembly and E.4.DPF for DPF or LPF authoring and publication- or access-carrier assembly. Use E.4.PFIP only for accepted-source integration or predecessor-publication preservation, E.4.PFR only for a relation or edition maintenance claim, and E.4.DPF.DA only for whole-package adequacy. |
| Work or reliance prompted by a carrier or display | Use A.15.2 for an identified WorkPlan and A.15.1 for performed Work. Use A.15 only while the system-role kind or assignment, Method, WorkPlan, and performed Work remain entangled. Use A.15.4 only while the appearance hides the direct prerequisite for the intended Work or reliance use; once that prerequisite is known, use its direct evidence, gate, decision, permission, or assurance pattern. |
| Architecture or structure use | Use C.30.P while the architecture or structure claim is still hidden, C.33 to test what selected structure a carrier or observation actually captures and what must return from source, and C.34 only for a claimed correspondence or preservation between two exact structures. |
| Base or support wording | Use A.6.6 only when the wording hides an actual basedness relation. Name the dependent, base, and direct predicate first and stop when that ordinary assertion answers the use. If the wording instead concerns evidence, assurance, or work enablement, use the pattern for that claim; leave navigation or ordinary help in ordinary language. |
C.2.P:4.2 - Core Glossary
C.2.P:4.2.0 - Cross-Side Fields That Must Stay Split
These fields are current episteme-publication precision vocabulary for DRR, architecture, and pattern-drafting work.
They exist to prevent one sentence from mixing FPF-side use-boundary, project-side records, actual work or action, method selection, carrier access, and authority records.
They are local recovery aids, not FPF kinds, not record kinds, and not a universal record ontology.
Close each field only by naming the FPF kind by value, relation record, relation phrase, project-side FPF kind and reference by value, or explicit non-use disposition at issue in the sentence.
The same local-aid rule applies to neighboring field names such as sourceRelationClass, explanationSourceRelationClass, comparativeRelationClass, representationValidityUseBoundaryValue, allowedUse, misuseRisk, and worldContactPolicy: they help record a local recovery or reader-use boundary, but they do not become kinds. These local fields do not instantiate evidence, gate, assurance, work, commitment, speech act, decision, release, authority, representation kind, world-contact kind, or policy kind. Read allowedUse as a local reader-fit field under declaredUseBoundary, not as permission, evidence relation, or authority.
| Term | Current interpretation | Must not mean |
|---|---|---|
FPF as episteme | The whole FPF is a claim-bearing episteme with publications, parts, patterns, pattern sections, DRRs, and companion publications and documents named for source, evidence, architecture, or review use. | A file, repository, taxonomy, pattern-language metaphor, or packet-local summary by default. |
| FPF pattern | A named pattern episteme that gives reusable action guidance for a problem situation. A practitioner applies its content in that situation. | A recurring arrangement, performed procedure, method call, cluster label, or document treated as a pattern merely from its name or appearance. |
| pattern section | Either a part of the pattern episteme or a bounded PublicationUnit of that pattern publication, depending on sentence function. State which one matters when the distinction carries a claim. | Independent pattern, file location, generic locus, or record with named authority-reference relation. |
accepted campaign DRR | A campaign decision source that states accepted content decisions for one campaign. | A pattern, current-authority summary, open-ended plan, review log, or replacement for pattern text. |
relationClaimSlice | An optional local note for a sentence whose direct predicate or participants still need A.6.P recovery. Name that problem, then recover the predicate, participants, and defining pattern. Add declaration, occurrence identity, qualifications, or representation detail only when the receiving use needs it. | A generic record-shaped relation, an invented umbrella kind, or a token or list used instead of the predicate and participants. |
declaredUseBoundary | The use for which the statement or result is offered, with any excluded or unsupported use whose distinction changes interpretation or action. State a blocked use only when its governing rule blocks it. Use A.6.B when the boundary claim needs L-, A-, D-, and E-claim separation. | Permission inferred from the declaration, a display, or readability alone. |
projectSideFPFRef | The project-side FPF kind and reference named by value when a publication, display, cue, or explanation is treated as a project-side source for work, evidence, gate, constraint, adjudication, decision, commitment, method, action invitation, assurance, or engineering justification. The field points to that kind and reference; use the relevant FPF pattern for the relation and its checks. | One slot accepting records, actions, methods, carriers, evidence, gates, decisions, assurance, and engineering justification interchangeably. |
rejectedOverread | An optional local note naming an independently grounded reading that a plausible intended reader could take and that changes truth, selection, reliance, or action. State the recovered relation or subject-specific source, scheme, scope, practice, or use that rules it out; apply F.19’s contribution test. | A mandatory invented foil, risk slogan, review-finding kind, moralized defect class, or reusable FPF kind. |
useBoundaryTargetKind, useBoundaryTargetRef | Source-local helper fields. Prefer declaredUseBoundary; if these fields appear in material being repaired, they name the kind and reference inside declaredUseBoundary, not an A.6.P relation slot. | A generic supported use, document capability, “claim outside the declared boundary”, review permission, or untyped pattern assignment. |
C.2.P:4.2.1 - Episteme, Publication, and Carrier Distinctions
| Term | Current interpretation | Must not mean |
|---|---|---|
U.Episteme | A claim-bearing holon identified under C.2.1. A dependent episteme kind has its own membership condition for that same individual. Use this head when the selected object is the knowledge that can be described, viewed, grounded, revised, published, or relied on. | A file, display, or process state treated as knowledge merely from appearance. For a paragraph or status note, identify the claim-bearing whole it carries. |
| 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, representation and its explicit correspondence under the applicable pattern, with C.29 governing mathematical-lens use, 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 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 the unit carries the claims of one identified episteme or episteme-lane U.View and the unit’s primary subject is that episteme’s EntityOfConcern, use the episteme’s EntityOfConcernRef. Otherwise identify the kind, topic or subject that the unit actually addresses. Citing an episteme does not by itself give the unit that episteme’s subject. | 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 | 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 | Depending on sentence function, recover the selected episteme, publication occurrence, particular expression, reusable publication form, publishing Work, or carrier under the direct pattern. | A public-looking file treated as proof that the 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, particular expression, reusable publication form, or independently identified physical or digital carrier in an actual expression-bearing relation, 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 expression | An independently identified sign construction under its expression domain’s formation and equality rules. PublicationExpressionRelation(E,X,U) establishes which selected edition it expresses sufficiently for the bounded use; actual carrier bearing and form conformance remain separate. | The episteme, reusable formation rules, carrier, or publication occurrence. |
| publication form | An independently identified collection of reusable formation or arrangement rules, their application domains and imported dependencies. A particular expression conforms to it under PublicationFormConformanceRelation; form-mediated expression and bearing claims have actual conforming expression witnesses under E.24.PUB. An E.17 MVPK face names such reusable rules. | The particular expression, selected claim-bearing episteme, actual publishing Work, or physical or digital carrier. |
| 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 | The reusable publication-form rules selected under E.17, with publication viewpoint, scope, pins and face kind when required. A constructed face expression follows those rules and expresses the selected source or receiving episteme; that episteme is a U.View only when exact E.17.0 conformance obtains. | Generic publication face, carrier, UI face, front-end display, filled expression by form identity alone, or proof of evidence, work, gate, or authority by presentation. |
| carrier, front-end, rendering | Recover the exact bearer or display relation. For publication under E.17 and E.24.PUB, identify the physical or digital carrier under its own domain identity rule and establish that its actual state or realization yields the selected expression. Otherwise name the file, transport, rendering, front-end, access or other carrier relation by sentence function. | Episteme identity, particular expression, reusable 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 reader 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 | The independently identified project object or relation, named by its FPF kind and an applicable reference: for example, a U.Work, U.WorkPlan, GateDecisionResult, A.10 evidence path, source U.Episteme, or the typed record actually referenced. Use an EpistemePublicationRelation occurrence reference only when availability matters. | An untyped label, carrier, or note used in place of the exact object and its reference. |
| 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. |
C.2.P:4.2.2 - Trigger Boundary
For FPF-governed wording, use E.10:0.2, E.10:0.2a, E.10:0.2b, E.10:0.2c, and E.10:0.2d for lexical cues within the connected F.19 reading and for selection of an already known applicable pattern.
This pattern is applicable only when one C.2.P-specific source-expression, episteme, publication, carrier, source-to-use, or use-disposition distinction is still needed to select or safely use the direct receiving pattern. When the pattern and field at issue are already recoverable, apply it directly.
When this pattern is applicable, do not restart from word taste. Keep any E.10 cue or routing result as input and recover source-expression clarification, FPF-governed use, current episteme-publication relation set, use disposition, and remaining reader use.
C.2.P:4.3 - Current Preferred Vocabulary
Use PublicationUnit when the reader inspects a bounded unit inside a publication. A person or an AI agent can perform that inspection.
Do not use it for UI behavior, carrier behavior, front-end behavior, file identity, dashboard behavior, or export behavior; use A.7, specific carrier or front-end wording, or the applicable named FPF pattern instead.
Use the current cluster names directly: PublicationUnit Stability Discipline, Local Head Restoration, and PublicationUnit Primary-Subject Discipline.
When the current entity is a bounded unit inside a publication, use PublicationUnit; when the current entity is authoring or editing work, name that work directly.
Use EntityOfConcern and its applicable EntityOfConcernRef when local wording names the participant of a claim-bearing episteme or episteme-lane view. publicationUnitPrimaryEntityOfConcern has the union meaning defined in C.2.P:4.2.1 and used by E.17.AUD: the carried EntityOfConcern or the non-claim-bearing kind, topic, or subject value. For E.17.AUD.OOTD’s separate primary-subject question, use its local publicationUnitPrimarySubject; the two fields are not aliases.
For describedEntity, DescribedEntityRef, primary described entity, EntityOfInterest, or EoIClass, use the exact EntityOfConcern participant, its applicable entityOfConcernRef or EntityOfConcernRef, EntityOfConcernChangeMode, EntityOfConcernClass, publicationUnitPrimaryEntityOfConcern, or the local FPF kind named by value.
Use EntityOfConcernSlot only while inspecting the exact reusable C.2.1 constitution RelationSignature; it is not an episteme field. If no claim-bearing episteme or same-individual U.View is current, use a non-claim-bearing kind named by value or plain topic or subject instead of inventing an EntityOfConcernRef.
For a publication unit’s primary subject, use publicationUnitPrimarySubject under E.17.AUD.OOTD. A section about scheduling maintenance may quote a report about a pump’s pressure. The section concerns the schedule, and the cited report concerns the pump. For this technical identification, establish that the unit carries the claims of the identified report and that the unit’s primary subject is the report’s EntityOfConcern. An index can point to the report under the pump’s name without carrying its claims.
Use ordinary topic, subject, or local referent when those words preserve the distinction needed by the receiving use; use the defined technical designation when episteme constitution or another direct subject rule depends on it. Preserve the applicable register requirements of E.10.
Do not mint any other reusable FPF name from this pattern alone. The E.17.AUD cluster PublicationUnit Stability Discipline defines and constrains PublicationUnit; this pattern only recovers bounded-publication-unit wording into that head and points to the cluster for its tests. FPF-governed uses keep the nearby definition or explicit publication relation set.
C.2.P:4.3.1 - PublicationUnit use and non-use boundary
PublicationUnit means one named, bounded unit inside a publication that a reader inspects as one unit: for example, one pattern body, section, table, note, card, sheet, or screen block inside that publication.
Use it when the unit boundary matters to authoring, review, navigation, or a claim about what that bounded unit exposes. Do not use it for the underlying episteme, a view, publication form, whole publication, carrier, file, interface behavior, dashboard behavior, authoring Work, or review process. Name those objects and relations directly.
The bounded unit may carry or expose claim-bearing content, but it is not identical with that content. PublicationUnit keeps the inspected publication-side boundary visible without mixing the unit with authoring action or reader action.
C.2.P:4.4 - Epistemic Precision Restoration After E.10
Keep any E.10 cue or routing result as input. Apply C.2.P only while a source-expression, episteme, publication, carrier, or use-disposition distinction is still needed to select or safely use the direct receiving pattern. If the pattern and field are already known, apply them directly.
C.2.P:4.5 - Rewrite execution modes
C.2.P:4.5.1 - Direct repair
Use this mode for the ordinary case. Rewrite the sentence; add a reason or non-use boundary only when it changes interpretation or action. No row or note is required.
When the intended function is navigation, “The note helps the reader find section 4.2” is a sufficient result. Stop.
C.2.P:4.5.2 - Compact row
Use the five-field row in 4.0a when the recovered distinction must remain inspectable. Add only the optional fact that changes the current claim.
C.2.P:4.5.3 - Full check
Use a full check only when:
- several unresolved fields interact;
- the source-to-FPF use is contested; or
- a reusable ontological or naming decision is being made.
The full check records the exact span and function, selected kinds and relations, direct pattern contributions, final wording, remaining reader use, and reopen condition. Add competing readings or rejected overreads only when they pass F.19’s independent-ground, plausible-reader, and contribution tests. Pattern authorship or a source citation alone does not require this mode.
C.2.P:4.5.4 - Publishing the compact row as a local note
When the five-field compact row must remain beside the repaired text, publish that same row as a local note. This changes only its presentation.
C.2.P:4.6 - Completion and reopen boundary
The application is complete when the smallest selected product:
- preserves any E.10 cue or routing result rather than restarting from word taste;
- names the recovered kind, relation, or non-use disposition;
- hands any remaining relation, naming, publication, evidence, work, decision, or assurance claim to the applicable pattern;
- leaves the reader a clear action or stop condition.
Reopen when a replacement head hides another umbrella, a later use adds a material field, the direct receiving pattern changes, or the repair becomes technically exact but hard to use.
Also reopen when an entry cue, summary, dashboard, retrieval snippet, or source note still carries the pre-repair reading. Do not reopen merely because a larger form could be filled.
C.2.P:5 - Archetypal Grounding
C.2.P:5.0.1 - Cheap case: ordinary reader help
Starting sentence: “The note supports the reader.”
Questions: What does the note let the reader do? Does the sentence claim evidence, authority, gate passage, work permission, or assurance?
Result: It only helps navigation. Rewrite: “The note helps the reader find section 4.2.” The recovered function is ordinary reader help. No FPF kind, relation, compact row, or full check is needed. Stop after the sentence.
C.2.P:5.0.2 - Mixed case: display and decision
Starting sentence: “The dashboard approves launch.”
Questions: Is the dashboard the decision, or does it display one? Which exact project object carries the approval claim?
Result when a passing gate decision is established: “The dashboard shows GateDecisionResult GD-17 for release candidate R; the decision, not the display, records that the gate passed.” E.24.PUB separates publication form, carrier, and occurrence; use E.17 when publishing a reader-facing account of the accepted decision. A.21 supplies the gate-decision meaning. The reader may find and cite GD-17, but must use the direct release or permission rule for launch. Stop.
Result when no decision resolves: “The dashboard is only a cue; launch approval is unresolved.” Block approval-bearing use until the required decision is recoverable under the direct approval rule.
C.2.P:5.1 - Boundary and Anti-Cases
| Boundary case | C.2.P result | Why this protects use |
|---|---|---|
| Ordinary reader help | The sentence says a note helps a reader find another section, with no evidence, authority, use-boundary, work, gate, decision, or project reliance claim. Leave ordinary wording ordinary or make one local wording repair. | Keeps ordinary prose affordable; support as ordinary help is not forced into a record. |
| Relation-only support wording | The source-use and publication-construction distinctions are already clear. If the relation to the receiving claim or any of its participants remains unclear, apply A.6.P; otherwise use the direct subject pattern. No C.2.P recovery is needed. | Prevents this pattern from absorbing relation precision restoration. |
| Known FPF kind named by value | The sentence already names the project-side FPF kind and reference, such as an evidence path, gate decision, decision record, Work occurrence, B.3 AssuranceResult, or architecture pattern application. Apply the named pattern without an intermediate C.2.P step. | Avoids a needless logical hop and keeps the relevant neighboring-pattern application intact. |
| Source phrase without recovered FPF-governed use | Source wording is interesting but its FPF kind, relation, or use disposition cannot be recovered. Keep it as reduced-use cue or block its FPF use. | Preserves source meaning without guessing FPF meaning. |
| Replacement head is another umbrella | A proposed repair changes support to basis, display to face, or route to path while the kind and relation are still hidden. Mark repair incomplete. | Blocks lexical churn and forces the kind named by value, relation, and declared use boundary to be recovered. |
| Apparatus too heavy | A one-sentence local repair is replaced by a full record, checklist, and source note with no additional declared use boundary. Use the local sentence or compact row instead. | Keeps first-use cost and maintenance cost inside the quality claim. |
C.2.P:5.2 - Transfer Coverage
C.2.P is intentionally narrow but must transfer across three recurrent publication situations:
- FPF-side drafting: pattern text, DRR text, source-relation notes, review-use notes, and pattern draft prose;
- project-side publication: dashboards, explanations, cards, documents, front-ends, rendered files, and generated summaries used around evidence, work, gates, decisions, assurance, or methods;
- external source-expression clarification: seminar fragments, papers, reviews, standards, and tool outputs being clarified before possible FPF use.
In all three situations the same invariant holds: before accepting the wording as current FPF text, recover the distinction between source wording and current FPF wording, claim-bearing episteme, publication construction, carrier-relation construction, relation-like slice, the applicable neighboring pattern for any non-C.2.P field, and remaining reader use.
C.2.P:6 - Bias-Annotation
| Lens | Risk | Mitigation |
|---|---|---|
| Ontology | Precise-looking words become a new parallel ontology. | Require recovery to current FPF kinds and relations before reuse. |
| Usability | The rule becomes too heavy for ordinary edits. | Use the smallest sufficient rewrite mode. Reserve the full check for several interacting unresolved fields, contested source-to-FPF use, or a reusable ontological or naming decision. |
| Preservation | Source-relation or source-ref target text is mistaken for direct pattern authority. | Keep source-related statements separate from the ordinary pattern guidance. |
| Checklist ritual | The rule becomes a form to satisfy rather than a wording action to perform. | Put the action in Solution; use row evidence only when wording has FPF-governed use. |
C.2.P:7 - Conformance Checklist
| Item | Check |
|---|---|
CC-C2P-1 | C.2.P opens only while one source-expression, episteme, publication, carrier, source-to-use, or use-disposition distinction remains unresolved. |
CC-C2P-2 | If the receiving pattern and field are already recoverable, the practitioner uses them directly. |
CC-C2P-3 | The selected product is direct repair, the five-field compact row, a materially justified full check, or an explicit non-use result. |
CC-C2P-4 | A direct repair needs no record; optional fields appear only when changing them could change the claim or use. |
CC-C2P-5 | A full check is used only for several interacting unresolved fields, contested source-to-FPF use, or a reusable ontological or naming decision. Pattern editing alone is not a trigger. |
CC-C2P-6 | Claim content, episteme, publication occurrence, form, bounded PublicationUnit, view, carrier, rendering, and project-side use remain distinct when current. |
CC-C2P-7 | Relation precision goes to A.6.P, stable naming to F.18, episteme identity to C.2.1, view conformance to E.17.0, reader-facing publication of an accepted account to E.17, and publication-occurrence, form, or carrier claims to E.24.PUB once that direct branch is known. |
CC-C2P-8 | The wording names a contributingPattern only for the concrete definition, constraint, or test it supplies. |
CC-C2P-9 | Slash compounds and lists do not hide an unnamed kind or relation. Examples are marked as examples rather than treated as a complete extension. |
CC-C2P-10 | The final wording remains precise plain language: a cold reader can recognize the situation, take the next action, and see the stop or non-use boundary. |
CC-C2P-11 | Source wording is not forced into FPF vocabulary when no FPF-governed use is recoverable. |
CC-C2P-12 | Source expression, source episteme, publication availability, source-to-use relation, any reverse source-return edge, work-side relation, and physical raw material remain separate. A.6.P.WMR or A.15.4 opens only while its relation or reliance question remains unresolved. |
C.2.P:7.1 - Current Scan Boundary
For FPF-governed wording, use E.10:0.2, E.10:0.2a, E.10:0.2b, E.10:0.2c, and E.10:0.2d for lexical cues within the connected F.19 reading.
C.2.P conformance begins only when one C.2.P distinction remains unresolved under §0’s entry condition. This same condition covers non-FPF source text being unpacked before possible FPF transfer; source status creates no separate entry branch.
Do not copy the E.10 trigger list into this pattern as a second registry. Keep any E.10 cue or routing result as input and recover source-expression unpacking mode, FPF-governed use mode, current episteme-publication relation set, use disposition, and remaining reader use. Use A.6.P only while the remaining direct predicate or participant question is unresolved.
C.2.P:8 - Common Anti-Patterns and How to Avoid Them
| Anti-pattern | Failure | Avoidance |
|---|---|---|
| Token swap | Replace display with face or host with file without recovering kind and sentence function. | Apply head-kind and relation recovery before rewriting. |
| Group-kind list | Leave a list such as pattern, record, relation, or action as if the list names one kind. | Decide whether the sentence needs one kind, a relation record, a tuple-like record, alternative cases, or a blocked ontology. |
| Type-correct but inert rewrite | All overread is removed, all heads are typed, and no practical guidance remains: the reader can see that local checks passed but cannot tell why the distinction matters, what to do, or which FPF pattern application or project-side FPF kind carries the claim. | Recover the didactic or recognition function in wording whose claim is recovered through the named FPF pattern, keep any Plain line mapped to the recovered Tech interpretation when both registers are current, state the remaining reader use, or demote the phrase to reduced-use cue, blocked use, or rewrite incomplete instead of treating the repair as complete. |
| Expressive overread rebound | A repair restores practical guidance with a memorable Plain or didactic line, but that line carries a claim not recoverable from the Tech fields, named FPF kind, recovered relation, project-side reference, disposition, or pattern application. | Map the line to the recovered Tech interpretation under E.10:6.2; use the FPF pattern that defines, constrains, or tests the claim; or demote the phrase to reduced-use cue, blocked use, or rewrite incomplete. |
| Pillar-blind precision pass | A broad cleanup proves trigger removal and kind recovery, but never checks whether E.2 P-2, E.6, E.8, or E.12 still let the intended reader see the working situation, why it matters, and what first useful move remains. | For FPF-governed Problem frames, Problem sections, recognition texts, examples, and worked slices, state the remaining reader use or FPF pattern application. Preserve intentional didactic metaphors when they are ordinary recognition aids or when their claim maps back to Tech. If the didactic function was harmed, repair the Plain wording so it maps back to the recovered Tech interpretation, or mark the rewrite incomplete instead of accepting type-correct but inert wording. |
| Source-companion header leakage | Carry a source-companion header into a pattern and let Authority: none or Current use define the new pattern. | Replace the copied metadata with the pattern’s own subject, use, and applicable normative status. |
| Pattern as procedure | Treat a pattern episteme as executable code or performed Work merely because an instruction says to call, route to, or invoke it. | Keep ordinary instrumental wording when it clearly means that a practitioner uses the pattern. For an asserted dated Work occurrence, use A.13 and independent A.15.1 admission; add F.6 only for precise assignment-bound attribution. Use A.3.2 when a claimed U.MethodDescription membership needs checking. |
| Strength metaphor | Say a claim is strong or weak without a recoverable comparison basis, such as a characteristic, threshold, evidence class, scope, gate condition, or use-boundary relation. | Name that basis, or replace the metaphor with the recovered use-boundary claim when that is what the sentence means. |
C.2.P:9 - Consequences
| Benefit | Trade-off and mitigation |
|---|---|
| Prevents parallel episteme and publication ontology from entering FPF-governed wording. | Adds a small recovery step before apparently simple rewrites; mitigate by using the smallest sufficient mode. |
| Preserves accepted glossary and rules without turning source-related statements into accidental pattern authority. | Requires a clear separation between pattern guidance and source-related statements. |
| Makes unclear meaning fail closed. | Some attractive phrases will not be accepted until their kind or relation is recovered. |
| Improves DRR and pattern drafting discipline. | Authors must resist convenient lists and umbrellas when one kind named by value or relation is needed. |
C.2.P:9.1 - Operating consequence
For each repair:
- start from the sentence’s function and practical consequence, not from a word list;
- preserve any E.10 cue or routing result and recover only the one still-hidden episteme, publication, carrier, source-to-use, or use-disposition distinction;
- use the direct pattern as soon as it is known;
- choose direct repair before a compact row, and a compact row before a full check;
- keep the final sentence readable to a cold practitioner and state what action or non-use remains;
- reopen only when a material field or use changes.
Do not perform global lexical replacement. Do not treat every FPF pattern edit as a full epistemic-restoration case. Do not retain a compatibility field whose only function is to remember a previous internal schema.
C.2.P:10 - Rationale
FPF already contains the relevant ontology. The recurring defect was not lack of concepts but ad hoc wording that bypassed them: source, target, display, object, host, route, supported use, and similar trigger terms packed several FPF kinds and relations into one convenient phrase; they are examples of wording to unpack, not current replacement vocabulary.
For FPF-governed wording, use F.19 with the E.10 cues, then use only the pattern whose field remains unresolved: F.18 for a reusable name, A.6.P for relation precision, and A.7, C.2.1, E.17.0, E.17, MVPK, or E.24.PUB for the relevant EntityOfConcern, episteme, view, publication, or carrier distinction. C.2.P stops as soon as the direct pattern and field are known.
Because every normative FPF pattern must satisfy E.2, epistemic precision is not a value apart from P-2 Didactic Primacy. A stricter repair is incomplete if it turns reader-facing problem text into a kind inventory with no working situation or first useful move. The remedy is recognition wording whose claim remains recoverable through the Tech interpretation or a named FPF pattern application, with a declared-use boundary when that boundary matters.
C.2.P:11 - SoTA-Echoing
The question is when ordinary contextual interpretation is sufficient to repair an episteme-publication claim, and when its intended use requires further recovery of the actual participants, relation or governing condition. Sections :4.0a–:4.1.3 select progressive recovery: understand the sentence in its context, recover only the unresolved distinction needed for the receiving use, and stop when that use is clear under its direct pattern. This is an FPF synthesis whose benefit and cost depend on what remains unresolved.
An alternative is a competent reader’s contextual explanation. It can recover the whole intended claim with less effort than an explicit record. In :5.0.1, understanding “supports” as helping the reader find a section is enough to write the direct sentence and finish. In :5.0.2, the meaning of “approves” can be understood while the particular decision and its scope still need to be recovered. The useful extra work is locating that decision under A.21; repeating a definition of approval would leave the receiving launch decision unsupported. These cases support the conditional choice in :4.1.2, not a claim that contextual readers generally fail.
The comparisons below retain designation, contextual explanation and explicit-constraint contributions for these different questions. They do not supply the local FPF relations themselves.
| Source contribution | Selected use in FPF | Limit or rejected transfer | Solution locus |
|---|---|---|---|
| ISO 704:2022 and ISO 1087:2019 terminology work distinguishes the entity under discussion, the concept used in a terminology system, the definition, the designation, and term-formation practice. | Recover the FPF kind, relation, and sentence function before accepting a rewritten phrase. Use external terminology work only as external corroboration for careful designation and definition practice. | Do not replace FPF episteme and publication ontology with an ISO concept system, a dictionary substitution, or a global class row. | C.2.P:4.1, C.2.P:4.4, and C.2.P:10 |
| SHACL validation checks a data graph against constraints in a shapes graph and reports conformance and validation results. | Use the explicit-constraint analogy: if the required FPF kind, relation, or declared use boundary cannot be recovered, keep that use unresolved or blocked under its direct rule. | The validation report supplies no FPF ontology or authority. Here, fail-closed means withholding the unrecovered FPF-governed wording use; the direct subject rule governs further action. | C.2.P:4.0a, C.2.P:4.2, and C.2.P:8 |
| Meconi et al., Do Large Language Models Understand Word Senses? (2025, §§3–4, 6) compares sense selection with contextual generation. Its free-form explanation results make contextual interpretation an alternative to requiring a predefined sense label. | Adopt contextual explanation as a sufficient starting point when it recovers the intended claim. The direct sentence in :5.0.1 needs no additional repair record. Adapt the question from word sense to whatever claim remains unresolved for the receiving FPF use. | The English tasks and tested models do not establish recovery of a particular FPF relation, actual participant or permission. Reject transfer of their scores to that broader conclusion. | C.2.P:4.1.2, C.2.P:4.4, C.2.P:5.0.1 |
| Suri et al., Structured Uncertainty guided Clarification for LLM Agents (2026, §4, §10) selects clarification using unresolved tool parameters and their domains, balancing a question’s disambiguation value against its cost. | Adapt the question-selection idea: identify the missing participant, relation or condition and ask only what can change the receiving use. This supports :4.1.2’s progression to explicit recovery when context alone leaves a consequential gap. | Its known tool schemas and simulated benchmark do not supply an open FPF ontology or validate this Method. Reject a universal parameter form, its formal cost model, or benchmark gains as requirements or guarantees for human and AI readers. | C.2.P:4.1.2, C.2.P:5.0.2 |
The selected line accepts the cost of consulting a direct pattern or recovering a source fact when that contribution is needed to settle the receiving claim. The ISO row constrains designation work; the SHACL row makes the explicit-constraint analogy and its limit inspectable; the two contextual-recovery comparisons explain why a full record is conditional. This is a reasoned choice for the cases and conditions above, not a measured advantage over every capable reader. Reopen the comparison when a cheaper explanation preserves the same receiving use, an actual repair loses a necessary distinction, or the governing claim or source changes.
C.2.P:11.1 - Relevant FPF Patterns
The current FPF corpus already has patterns that contribute to this discipline:
E.10supplies word/head, morphology, register, and naming cues and routes within the connectedF.19reading.E.10.D2gives the “thing vs words vs rules” discipline and the carrier humility rule.F.18gives the local-first naming protocol: governed value and kind; the pattern and contribution that define or constrain them; by-value scheme; local-sense claim; intended use; candidate comparison; and any separately obtaining relation.A.6.Prestores an ordinary sentence with the direct predicate, participants, and defining pattern. It adds a candidate note, reusable declaration, occurrence identity, or representation only when unresolved meaning or the receiving use needs that detail.C.2.1gives episteme identity through exact claim content, EntityOfConcern, and effective ReferenceScheme and keeps empirical grounding and edition continuity as distinct direct relations.A.7keeps EntityOfConcern, Description episteme, and publication carrier distinct.E.17.0tests view conformance to a viewpoint;E.17governs reader-facing publication forms for an accepted account;E.24.PUBdistinguishes publication occurrence, form, and carrier.A.15.4shows how to keep an encountered publication, display, or low-articulation cue distinct from the project-side FPF kind and reference used for work or reliance.A.16coordinates language-state moves;A.16.0supplies an optional trajectory account when their history matters;A.19defines the CharacteristicSpace and its reusable predicates;B.2.5governs supervisor-subholon feedback;C.27distinguishes state or rate readings from intervention-sensitive temporal claims;A.3.3defines the reusable state-space and transition-law episteme.E.19compares a materially revised pattern edition with its earlier supported uses and tests the changed wording.A.6.Acarries action-invitation discipline when a publication, representation, or cue invites an action without itself becoming authority, evidence, gate passage, or work completion.C.11carries decision-making and decision-record discipline when the question under repair is a decision rather than generic action.A.15andA.15.4split system-role kind and assignment, Method, WorkPlan, and actual-Work alignment from appearance-based reliance repair; do not useA.15as a universal repair for episteme-publication wording.E.9is the campaignDRRpattern for campaign-level content decisions;E.11is only for entry-discoverability situations and must not organize an episteme and publication repair by default.
These internal FPF patterns remain primary:
| Claim need | Relevant FPF pattern(s) | Alignment with C.2.P | Adoption result |
|---|---|---|---|
| Head-kind discipline | E.10 | Use head-kind recovery before accepting a phrase. | Adopt. |
| Stable naming | F.18 | Run a name card when a reusable head is being minted. | Adopt. |
| Relation precision | A.6.P | Recover the predicate, participants, and defining pattern. Add typed declaration, occurrence identity, qualifications, or representation only when the receiving use needs them. | Adopt. |
| Carrier and EntityOfConcern-description humility | A.7 | Keep EntityOfConcern, Description episteme, and carrier apart before treating a publication as evidence, work, gate, or authority. | Adopt. |
| Episteme and publication ontology | C.2.1, E.17.0, E.17, MVPK, E.24.PUB | Separate episteme, publication, view, generic publication face, MVPK face under E.17 constraints, publication unit, carrier, and rendering. | Adopt. |
| Project-side downstream use | A.6.A, A.10, A.15, A.15.4, B.3, A.20, A.21, C.11 | When a publication, display, cue, or explanation is treated as evidence, gate, decision, work permission, method, assurance, or engineering justification, name the applicable FPF pattern and the project-side FPF kind and reference. | Adopt. |
Use the internal patterns above for the particular claim left unresolved. Under :4.6, a repair closes when the intended kind, relation and relevant use condition are recoverable; an ordinary sentence can supply that result. A remaining unrecovered distinction keeps the affected use unresolved under its direct rule, while an understood claim outside the existing FPF account can require a separate framework decision.
C.2.P:11.2 - E.19 Review Profile Carry-Through
Use this section for an E.19 judgment of a pattern edition. Select only the profiles whose triggers hold for that edition and use. For an ordinary sentence repair, :4.6 supplies the completion test.
Run PCP-TERM when the repair changes episteme-publication-heavy naming, umbrella words, slash compounds, trigger-word replacements, or relation wording.
Run PCP-BRIDGE when the repair imports claims, terms, or norms across contexts, disciplines, or reference planes under E.19.
Run PCP-ENTRY only when the repair changes which FPF pattern a working reader should apply in a problem situation. Do not use PCP-ENTRY as a substitute for the epistemic precision restoration itself.
Run PCP-PRAG when the repair changes reader action, practical payoff, or what the working reader can safely do next. A type-correct but inert repair fails this line even when every recovered kind is technically right.
When the repair changes evidence, proof, witness, grounding, explanation, gate, release, or engineering-justification claims, apply the relevant FPF pattern (A.10, E.17.EFP, A.20, A.21, B.3, or another applicable pattern) and select the current E.19 profile by the changed claim. Do not mint a local evidence-review profile inside C.2.P.
C.2.P:12 - Relations
- Builds on:
E.2Pillars, especiallyP-2 Didactic Primacy;F.19,E.10,E.10.ARCH,A.7,F.18,A.6.P,C.2.1,E.17.0,E.17, MVPK,E.24.PUB, andA.6.A. - Coordinates with:
E.6,E.7,E.8,E.9,E.12,E.19,A.10,A.15,A.15.4,B.3,A.20,A.21,A.6.F,A.6.P.WMR,A.6.3.CSC,A.6.3.CR,A.6.3.RT,C.30.P,C.16.P,C.16.Q,E.17.EFP, andE.17.ID.CR. - Does not replace:
E.10general lexical rules,F.18naming protocol,A.6.Prelation precision, or local episteme and publication patterns. It says when those patterns must be applied to episteme-publication-heavy wording.