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 still 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.

1. Say what the sentence is doing: defining, claiming, instructing, comparing, locating a source, describing a publication, or supporting a project use.
2. Recover the one unresolved episteme, publication, source-to-use, carrier, or use-disposition distinction.
3. Rewrite the sentence, or hand the remaining claim to the exact pattern that defines, constrains, or tests it. Then stop.

Not this pattern when. If the exact receiving pattern and its current field 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 plus one plain reason or non-use boundary. 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.
• Non-use result: 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 live 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 is especially dangerous because it 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 not only ugly terminology. 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. Overread removal is only half of the repair; the other half is remaining action guidance under the Pillars.

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.

Anti-overread payoff question. A repair is useful only if the text can say in ordinary prose what false downstream interpretation is blocked, what useful action remains, and when the reader must apply another named FPF pattern because evidence, gate, decision, work, assurance, bridge, release, or reliance is current. If the repair blocks an overclaim but leaves no useful action, it is probably becoming ceremony rather than guidance.

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:

1. 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;
2. 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;
3. slash lists and heterogeneous rows become false group kinds;
4. unclear source meaning is guessed into FPF-governed wording rather than blocked or assigned to an accepted FPF extension;
5. authors copy the same loose wording into DRRs, patterns, source-relation notes, source-ref target notes, or project texts.

C.2.P:3 - Forces

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:

1. the head kind and sentence function are recoverable under E.10;
2. a stable reusable name has an F.18 naming result;
3. a relation, comparison, dependency, support, sameness, grounding, mapping, or endpoint claim has A.6.P relation precision, with use-boundary and project-side reliance questions split into their own fields;
4. a claim-bearing episteme, episteme species named by value, episteme-lane view, or project-side FPF kind and reference named by value has the needed C.2.1 typing or named FPF claim or declared-use boundary named by value;
5. publication, view, face, and carrier distinctions satisfy the applicable E.17.0 view-conformance, E.17/MVPK publication-face, and E.24.PUB publication-occurrence, form, and carrier rules;
6. the repaired text satisfies E.2 Pillars, especially P-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 being made; 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;
7. the final phrase preserves the distinction without adding another claim;
8. 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 and one plain reason or non-use boundary. It creates no record.

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 exact 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. A full check records the original sentence, the competing interpretations, the selected kinds and relations, the exact neighboring-pattern contributions, rejected overreads, selected wording, remaining reader use, and reopen condition. It does not repeat empty trigger flags or every possible downstream field.

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.

1. Name the sentence function. State what the sentence would let a reader claim or do.
2. Recover one blocking distinction. Separate source expression, episteme, publication, bounded publication unit, carrier relation, source-to-use relation, or project-side use. Use A.6.P as a separate step only when the remaining problem is relation precision.
3. 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: a standard name, source name, discipline abbreviation, established compound name, formula, ratio, fraction, unit, path-like quoted source token, title, product name, file path, URL, or quoted source wording where the slash is part of the accepted designation or carrier syntax; keep ISO/IEC, ISO/IEC/IEEE, 1/2, URLs, conventional abbreviations, and similar forms when the sentence uses them as notation;
• a plain-language synonym pair with no ontology, authority, evidence, or use-boundary claim;
• a lazy and/or-style join that must be split or recovered before FPF-governed use;
• a composite-kind candidate that needs F.18 and A.6.P recovery;
• a relation claim that needs a RelationKind, a QualifiedRelationRecord, or a multi-term relation phrase with typed endpoints, slots, qualifiers, scope, time, and viewpoint;
• a tuple-like record that needs a named record kind and named slot semantics;
• 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 FPF kinds, or current FPF episteme and publication ontology;
• the claim is understandable, but current FPF does 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 only when the problem situation, tempting overread, rejected current uses, current FPF gap, and the first user action that would improve are stated by value.

Classify the case explicitly:

• recovered by value: the text now names the current U.Episteme, selected EntityOfConcern, U.View, publication form, generic publication face, MVPK face under E.17 constraints, PublicationUnit, carrier relation, relation record, relation phrase, tuple-like record, FPF pattern, document named for source, evidence, architecture, or review use, reviewed publication, review packet, review record, or review state, project-side FPF kind and reference named by value when projectSideFPFRef is current. The selected value is one current value, not the list: C.11 ChoiceResult; C.11 decision record; A.6.A action invitation; A.15 U.WorkPlan; A.15.1 dated U.Work occurrence; U.Method; U.MethodDescription; A.20 constraint or adjudication decision record; A.21 GateDecision; A.21 DecisionLogRef; A.10 evidence path; typed evidence record; B.3 AssuranceResult; an engineering-justification result under its direct pattern; typed status record whose FPF status pattern is named; carrier relation; front-end relation; or not-triggered alternative;
• 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 DRR content decision, or campaign-scoped content question, but it does not carry current authority, evidence, or use-boundary claim until an accepted architecture decision, accepted DRR, 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. C.2.P may identify that A.10, A.15, A.15.4, A.20, A.21, B.3, C.11, F.9, E.17.EFP, E.17.ID.CR, or another FPF pattern applies. 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 actually 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 actual 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.P for relation precision;
• F.18 for a reusable name;
• C.30.P for a hidden architecture or structure distinction;
• C.16.P or C.16.Q for a hidden characteristic, scale, or evaluative-quality distinction;
• the applicable episteme or publication pattern for an already identified episteme or publication question.

These are alternatives, not a mandatory sequence. 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.

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. Each field closes only by naming the FPF kind named by value, relation record, relation phrase, project-side FPF kind and reference named by value, or explicit non-use disposition that is current 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.

C.2.P:4.2.1 - Episteme, Publication, and Carrier Distinctions

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 exact pattern and current field 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 intended entity is a bounded, human-inspected unit inside a publication. 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. When the use is E.17.AUD.OOTD’s primary-subject question, recover its local publicationUnitPrimarySubject; apply the EntityOfConcern projection only when that pattern’s equality condition holds.

Use ordinary topic, subject, or local referent only in non-normative explanatory prose where no episteme constitution or neighboring direct relation, publication construction, or authority relation is being asserted.

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 person 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 exact 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 and state one plain reason or non-use boundary. No row or note is required.

Example result: “The note helps the reader find section 4.2.” Reason: this is navigation, not evidence or assurance. 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, competing readings, selected kinds and relations, direct pattern contributions, rejected overreads, final wording, remaining reader use, and reopen condition. It is not required because the text is an FPF pattern or because a source is cited.

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: it adds no fourth execution mode, no extra required field, and no durable FPF record kind.

C.2.P:4.6 - Completion and reopen boundary

The application is complete when the smallest selected product:

1. preserves any E.10 cue or routing result rather than restarting from word taste;
2. names the recovered kind, relation, or non-use disposition;
3. hands any remaining relation, naming, publication, evidence, work, decision, or assurance claim to its exact pattern;
4. 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 decision exists: “The dashboard shows GateDecision 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 exact decision exists.

C.2.P:5.1 - Boundary and Anti-Cases

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

C.2.P:7 - Conformance Checklist

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. When the relation-bearing slice is current, A.6.P remains a separate required precision-restoration pattern.

C.2.P:8 - Common Anti-Patterns and How to Avoid Them