#Ontology-First Plain Technical Rewriting

F.19 · Stable · Plain-technical precision-restoration pattern · Normative for FPF-governed technical prose unless explicitly marked informative; informative for external source prose until it is rewritten for FPF use · Part F - The Unification Suite (U-Suite): Concept Sets, SenseCells, and System-Role Kinds and Assignments

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Type: Plain-technical precision-restoration pattern Status: Stable Normativity: Normative for FPF-governed technical prose unless explicitly marked informative; informative for external source prose until it is rewritten for FPF use

Plain-name. Ontology-first plain rewriting.

Intent. Repair technical prose that is grammatically plausible or locally true yet makes the reader supply an unsupported relation, participant, alternative, list meaning, or rhetorical branch. First recover the governing object, claim, action, required operands, referents, and kinds; then remove apparatus and other structure that contributes nothing to the intended use. The normal result is repaired text, not an audit form. Preserve every technical distinction and operational detail that changes truth or action, and route only genuinely unresolved FPF wording to E.10, E.10.ARCH, E.10.ROLE, A.6.F, F.18, or the subject pattern that defines it.

Builds on. E.8, E.10, E.10.ARCH, F.18, A.6.P, A.7, E.18, E.21, and source-use, evidence, assurance, gate, work, decision, publication, architecture, characteristic, state-family, and relation patterns when those objects carry the repaired span's claim.

Coordinates with. E.19, E.22, E.23, A.19.SPR, C.2.P, C.16.P, C.30.P, E.11, I.2, pattern-quality records, review records, DRRs, projection loci, and source-side notes.

Use F.19 when a bounded piece of technical prose is harder to understand or use than its intended claim requires. The sentence may be grammatical and every isolated statement may be true, yet the reader still has to invent a missing operand, accept an implausible relation, guess what a pronoun or relational noun refers to, interpret a list with no stated purpose, or wait through caveats and ornament before reaching the governing message.

#Relations

#Content

#Use this when

Use F.19 when a bounded piece of technical prose is harder to understand or use than its intended claim requires. The sentence may be grammatical and every isolated statement may be true, yet the reader still has to invent a missing operand, accept an implausible relation, guess what a pronoun or relational noun refers to, interpret a list with no stated purpose, or wait through caveats and ornament before reaching the governing message.

Common signs are:

• a verb or relational noun whose needed participant is not cheaply recoverable;
• a grammatical subject that cannot bear the asserted predicate, even when that predicate appears inside a denial;
• a contrast, warning, or guard against a reading that no plausible intended reader has reason to make;
• one head or predicate imposed on unlike members;
• examples presented as a classification, or a catalogue presented instead of a proposition; and
• coordination repeated inside phrases and across clauses, or stacked modifiers, when one governing statement would do.

Item count is only a cue. Two coordinated members can already be needless, while a long inventory can be exact and useful when its kind, membership rule, and closure matter. Matching kinds and individually relevant members do not by themselves justify a series: the reader must need to distinguish or retain the members together for the intended use.

Apply the same method to FPF pattern prose and to other technical prose whose accepted domain terms, relations, claim boundaries, or use conditions must survive simplification.

What goes wrong if missed. The prose looks careful while introducing relations, alternatives, or branches that the work does not need. A later author or generator may then copy that shape as an acceptable technical style.

What this buys. The reader reaches the supported object, claim, and action sooner. Required technical distinctions remain; invented foils, false agency, reference puzzles, and catalogue rhetoric do not.

First useful move. State in one plain sentence what the intended reader must recognize, understand, decide, or do. Then read the whole natural span against that sentence before changing individual words.

Not this pattern when.

• If only one already-visible FPF word or head has an unresolved technical use, take the exact E.10 route for it.
• If the question is a durable reusable name, use F.18.
• If clear advice still demands work whose contribution, feasibility or requirement merits are unresolved, use C.11.DUA to repair that advice. Return here for any wording repair it needs.
• If source prose is only being observed and not admitted into governed technical prose, keep the observation source-side.
• If evocation, rhythm, ambiguity, or parallelism is the declared work of a poem, quotation, ceremonial passage, or other expressive genre, do not flatten it into technical instruction. Apply F.19 only to the technical claim or action that must remain recoverable.
• If a language-specific grammar or idiom remains after the common semantic repair, use the applicable language profile.

Primary EntityOfConcern in plain terms. One sentence, row, paragraph, list, or small coherent section being repaired into precise plain technical prose.

#Problem frame

Local truth is necessary but not sufficient for useful technical prose. “A mouse is not the Eiffel Tower” is true, but it introduces an Eiffel-Tower reading that the reader had no reason to construct. “The evidence does not notice the error” is also locally true, yet the denial makes evidence the subject of an impossible noticing relation. “The result is not a final scheme of the world” invents a grand alternative before the sentence reaches its actual result.

The same failure appears without negation. “Then pour” can omit the thing or destination that determines the operation. “Bearer” can leave the reader asking bearer of what. A grammatical series can give examples, methods, activities, and outcomes one false common head. Several individually valid pairs can create catalogue rhythm while never stating the proposition they are meant to support. Scenic or defensive detail can delay an urgent event or requested action.

One connected repair therefore answers two questions:

1. Semantic completeness: can the reader recover the predicate, its required participants or operands, local referents, member kinds, and the relation actually asserted?
2. Pragmatic contribution: does each explicit alternative, modifier, guard, list member, and extra proposition change what the plausible intended reader can recognize, understand, decide, or do?

The defect is not a word class or a forbidden syntax. Negative polarity can be the claim. A documented anti-pattern can quote the real error. A visible diagram feature can make one overreading plausible. Ordinary metonymy and ellipsis can be clearer than formal expansion. Judge the supported relation and the receiving use, not the presence of not, a comma, or a particular verb.

#Problem

How can a practitioner repair technically plausible prose that asserts unsupported relations or makes the reader invent missing structure, while preserving the kinds, claim boundaries, operational detail, and established terms that the intended use actually needs—without building a controlled language, a universal ontology of speech, a prohibited-word list, or a form for every correction?

#Forces

#Solution

Use OntologyFirstPlainRewrite as one connected reading and repair over a natural sentence, row, paragraph, list, or small coherent section. Take the intended reader and use from the surrounding work; do not invent an adversarial reader or a persona form.

#One connected reading and repair

1. State the governing message. Say what object, claim, action, event, or distinction the span needs to convey. Mark process traces, status language, reference boilerplate, quality proof, defensive caveats, ornamental detail, and other apparatus that may be displacing it. Apparatus receives no protection merely because it is true or polished.
2. Recover the predicate and its participants. Identify the operation and every participant that changes it. This may be an actor, object, source, target, result, or another required operand. Apply the same question to verbal and relational nouns: recover of what, for what, between what, or another required participant. Leave an argument implicit only when one intended value is cheaply and uniquely recoverable from the local span.
3. Check predicate compatibility. Recover what the complete claim asserts under its negation, modality, or conditions, and test the subject and participants under the intended literal or metonymic reading. A positive assertion must assign its predicate to a compatible kind. A denial may correct an evidenced type mistake under the plausible-reader test below; without that ground, “evidence does not notice the error” introduces an idle alternative. Keep ordinary metonymy when the relation is established and the capable participant or work remains recoverable: a diagram may show, a framework may help, a reminder may cue, and a constraint may limit.
4. Resolve referents and kinds. Pronouns, demonstratives, omitted heads, and repeated labels must select one locally appropriate referent. Preserve the object kind, claim or relation kind, slot or relation position, use and publication boundary, and flow distinction whenever one changes the claim. A shared grammatical position does not make different FPF kinds interchangeable.
5. Test contribution. Try deleting every optional contrast, guard, modifier, example, coordinated member, and extra proposition. Remove it when the plausible intended reader can still recognize, understand, decide, and act in the same way. Local truth and grammatical fit do not earn a phrase a place by themselves.
6. Resolve coordination and lists on two axes. First ask whether the receiving use needs a series at all. A list or parallel construction earns its form only when the reader must distinguish or retain its members together; otherwise select the governing claim, relation, or representative case. If a series is needed, determine its membership semantics. State the proposition or action it serves; use one kind or predicate only when it fits every member; distinguish a closed set, illustrative examples, alternatives, a sequence, several direct relations, and a failed ontology. A closed set needs its kind, membership rule, and closure. Illustrative examples need the proposition or kind first and a non-exhaustive cue when a plausible reader could mistake them for a classification. Then test discourse load: keep a member only when it adds a distinct consequence; reduce coordination repeated at several grammatical levels and modifier chains that make the reader retain needless branches or postpone the governing message. Length is evidence to inspect, not a verdict. If a list hides an FPF kind, relation, or structure that ordinary reading cannot recover, use the pattern that defines or tests it, or return the unresolved meaning as a blocker.
7. Foreground, rewrite, and compare. Put the governing event, claim, requested action, or decision before optional atmosphere, examples, caveats, and catalogues. A prerequisite may come first when it is needed for safe interpretation or action. Write the shortest ordinary technical sentence that preserves every live predicate and participant, established term, polarity, and action-changing detail. Such detail can include quantity or threshold, sequence or timing, criterion or tolerance, exception, and applicability. Compare before and after: any unsupported change of kind, relation, scope, use, currentness, or operational effect is a loss and blocks the rewrite unless another accepted decision authorizes it.

Keep ontology visible only where it carries the sentence. A term-source or type annotation is needed only when it changes how the reader identifies the object, kind, relation, slot, use, publication boundary, admissible use, or applicable rule. A record, card, table, schema, data structure, dashboard, or named form remains apparatus unless it carries one of those values. If ordinary domain wording already preserves them, keep the ordinary sentence. "The aircraft flies" is better than a typed expansion unless the flight function, system kind, or slot relation is under repair.

Precision before a coarsened rendering. When head kind, qualifier claim, or comparison basis remains unresolved in FPF-governed prose, use this working order:

Restore the head kind first; a narrowing qualifier such as comparative, safe, interactive, or reliable does not by itself restore that kind. Then unpack the qualifier claim, then check whether the comparison or escalation basis is homogeneous. Only after that may a later Plain, didactic, or coarsened rendering admissibly relax the sentence, while keeping the more precise upstream interpretation recoverable.

Judge homogeneity against the comparison or condition rule actually used; recover distinct relations separately when that rule combines them. The basis may be a homogeneous claim-kind criterion, threshold, or named defining, constraining, or source-relation condition.

Treat exact, direct, current, governed, subject, owner, defining, and similar qualifiers as content only when they distinguish live alternatives. Remove them when no such contrast changes the truth, action, stop, or reliance. A PatternID may remain an ordinary citation; expand it into a claim-bearing episteme, ClaimGraph, U.MethodDescription, U.Method, actor, assignment, U.Work, or another formal identity only when the current claim or a named later use depends on that distinction.

Keep ordinary practitioner action and instrumental pattern-use wording ordinary when it does not assert a particular dated Work occurrence. “Use E.9 to record the decision” and “the framework maintainer compares the editions” need no invented Method, MethodDescription, performer, assignment, or Work identity.

Open the identity-bearing branch only when the sentence deliberately asserts a particular dated U.Work occurrence. Then point to its basis: A.13 first, independent A.15.1 Work admission second, and F.6 afterward only for precise assignment-bound attribution. Add a local system-role kind or a separate System-classification judgment only when that neighboring claim matters. Treat a pattern episteme as a U.MethodDescription only after A.3.2 establishes that it has an already admitted Method as its EntityOfConcern and explains how that Method is performed. Otherwise cite the applicable pattern content as guidance and use A.3.1 for the Method itself.

#Plausible-reader guards and cold-reader recovery

Use two reader tests for different decisions.

• The plausible intended reader has the knowledge and task presupposed by the text. Use this reader to decide whether a foil, guard, warning, or contrast deserves mention. Do not substitute an adversarial reader who can imagine any false inference, or the author who already knows the answer.
• The cold intended reader lacks the author's private context and unpublished notes. Use this reader after the rewrite: they can recover the object, predicate, participants, relevant kind or ordinary status, relation, action-changing detail, and next useful action.

Recover the instruction from the publication, its stated prerequisites and the knowledge presupposed for its intended reader. An application-test scenario may supply task-specific inputs, such as workload or available resources. Distinguish those inputs from explanations of the instruction supplied only for the test. If only the test scenario explains the action denoted by B2, successful application demonstrates use of that supplied explanation; the publication's wording question remains unanswered. Name or reference the action in the publication, then check recovery without the test-only explanation.

Retain a negative alternative, denied consequence, warning, or non-use statement only when the exact rejected reading has an independent local ground; a plausible intended reader could take that reading here, including an evidenced type mistake; and the distinction changes truth, understanding, selection, safety, stop, reliance, or action. An earlier or source claim, an observed recurring mistake, a serious competing position, a visible representation feature, or an applicable safety risk can supply the ground. The guard itself cannot.

Even a grounded guard should be the smallest clear correction. When actor allocation is the useful content, state it positively: “On receiving new evidence, the reader decides whether to reopen checking or revision.” When currentness is the useful content, state the direct use: “This guide conveys the seminar of 1 February 2026; check current rules against the current FPF edition.” Keep material negation, documented anti-patterns, fair disputes, and safety stops when their polarity or boundary is itself the claim.

#Basis and coverage of a recovery judgement

State whether the judgement rests on an expert walkthrough, an actual reading, or a formal-model estimate, using the distinctions in C.2.8:4.5. An expert can judge recoverability from the public text for the intended reader. An actual response establishes what that reader recovered under those reading conditions. A formal-model estimate retains its stated observer, selected structure and model conditions under C.2.8:4.6.

Use expert reading for a bounded wording judgement when it resolves the question from the permitted public inputs and no actual response is required. Obtain actual public-only recovery when:

• the intended conclusion claims that a reader actually recovered the instruction;
• plausible reconstructions still differ in an action-changing participant, operation, result or condition, and the reader's response can change the repair or use decision;
• it remains materially uncertain whether the publication supplies the needed instruction or the evaluator supplies it from private knowledge or test-only explanation; or
• demonstrated misses undermine the sufficiency of the earlier expert reading for the affected instruction family.

A visible wording defect can be repaired directly. Select any reading still needed for the repaired text and intended conclusion. Give a cold reader the publication, its stated prerequisites and task inputs, withholding private rationale and suggested answers. Preserve the initial recovery before supplying further explanation; qualify subsequent source returns or help under C.2.8:4.3.

Limit a recovery conclusion to the natural text units and relations examined under its actual evidence basis. A whole-publication conclusion needs coverage of the whole publication, including relations needed to read its parts together. Successful application probes cover their tested uses; they leave unexamined text outside that result. A whole expert reading combined with local actual readings retains that mixed basis. Reuse a result for the same or explicitly unaffected text, recovery question, reader preparation, access, assistance and budget when those conditions still apply. A local revalidation by a reader familiar with the earlier wording retains that qualification.

State a material limit in the receiving judgement or result already needed by the work. When a required reading is unavailable, identify the missing basis and leave only the dependent conclusion open. Correct recovery of what the text asserts and the subject-matter warrant or practical adequacy of that assertion remain separate questions under C.2.8.

#Result and local revalidation

The ordinary result is the repaired text, or a blocker naming the unresolved meaning. Do not require a separate result form, card, table, progress row, or recorded answer for each facet of the reading.

After changing words or syntax, reread the changed sentence and only the nearby text needed to determine its referents, predicate, participants, contrast, modality, support, action, and result. The earlier semantic verdict does not transfer to new wording. Unchanged spans and conclusions remain reusable; a local edit does not trigger an automatic whole-document pass.

When a named high-risk or disputed decision needs inspectable evidence, show the before text, repaired text, live values that had to survive, and any unresolved blocker. Use the receiving decision's existing comparison or review result. The optional fields below can structure that result when its receiver needs them; ordinary corrections need no separate form.

If ordinary reading settles the issue, stop. Open E.10, E.10.ARCH, E.10.ROLE, A.6.F, F.18, or an exact subject pattern only for a genuinely unresolved FPF word, kind, relation, role, function, name, source-use, or admissible-use question. A trigger helps find a candidate; it neither bans the wording nor closes the judgement.

#Result form

Use this optional form when the receiving decision needs the corresponding inspectable detail.

#Pattern-prose specialization

When the repaired prose is an FPF pattern, apply the same method with one purpose test:

Does this sentence help the pattern's intended user recognize and perform the pattern, or does it record development, review, projection, landing, quality, or source-management evidence about this version?

If it records evidence about the pattern version, keep that evidence outside the pattern unless the pattern's own primary EntityOfConcern is that evaluation or projection object. The evidence can cause edits to the pattern; it is not automatically pattern content.

Pattern prose keeps:

• the pattern's own primary EntityOfConcern;
• the first useful move;
• the practical delta and cost of missing it;
• a local boundary that passes F.19:4's full independent-ground, plausible-reader, contribution, and smallest-clear-correction test; and
• short references to related patterns after the pattern's own content is visible.

Public architectural reasons stay with the explanation when they help the intended user understand, select, combine, or adapt the Methods and profiles. Apply E.8:4.2.3 to distinguish those reasons from the current version's development history.

Pattern prose moves out:

• rationale for the current draft's placement or promotion as a development decision;
• correspondence about producing or reviewing the draft rather than using the pattern;
• quality, projection, monolith-parity, landing, and source-management evidence; and
• repeated boundary doctrine already carried by another pattern.

#Archetypal Grounding

These cases show repairs and situations in which ordinary wording should remain.

Illustrative case — expert preparation and public wording. A production-planning guide says, “Use their exact result for the plan; it is not a completion certificate.” A private briefing identifies the result as the forecasting team's demand estimate in Report R for 1–7 June under scenario S. The planner must compare that demand with available production capacity; a changed period or scenario requires an applicable estimate before comparison. An expert who knows the briefing can reconstruct this operation. The public sentence still leaves the result, comparison operands and change condition unstated, and the case supplies no reason for its reader to expect a completion certificate.

Repair: “Compare the demand estimate in the forecasting team's Report R with available production capacity for 1–7 June under scenario S. If the period or scenario changes, obtain an estimate for the applicable period and scenario before comparing.” The repair makes the result, operands, applicability and action order public. It removes the empty intensifier and unsupported certificate alternative. The expert's reconstruction from private preparation and recovery from this repaired public instruction have different reading conditions.

#Bias-Annotation

F.19 deliberately biases toward direct, reader-usable technical prose. The protected value is kind-preserving clarity, not brevity by itself. A longer rewrite is better when it restores a participant, relation, boundary, or operational detail that the declared use needs.

#Conformance checklist

These questions guide one connected reading; they do not require separate recorded answers. KindPreservationCheck names the comparison required of every rewrite. Its separate result form is optional under F.19:4.1.

#Common anti-patterns and how to avoid them

#Consequences

Technical prose becomes easier to trust and use because every asserted relation has supported participants, every retained guard answers a plausible question, and lists serve a visible proposition or action. The pattern also removes a source of stylistic copying: authors no longer see defensive truth, false symmetry, and exhaustive-looking catalogues presented as the normal shape of precision.

The cost is one semantic reread of the changed wording and its meaning-dependent neighbours. That cost stays local. Ordinary correction produces repaired text; only a named high-risk or disputed decision needs comparison evidence.

#Rationale

Precise plain language has two obligations. The sentence must be semantically complete enough to recover its predicates, participants, referents, kinds, and operational detail. Every additional structure must also earn its place by changing understanding or use for the intended reader. Either obligation alone is insufficient: a fully typed sentence can still be noise, and a short sentence can still hide its object.

The order of repair therefore matters: recover the governing message and relations, remove unsupported structure and displaced apparatus, then write the shortest ordinary sentence that preserves the live meaning. E.10 remains a cue and a route for unresolved FPF wording; it is not a rival normal-pass algorithm. Attention management remains outside the language pattern.

#SoTA-Echoing

SoTA here means the best current contribution to the stated practice question, not the newest or most formal publication. The plain-language comparisons were qualified on 2026-08-19; the negative-parallelism row uses research published on 2026-08-20 and checked on 2026-09-01. A source's official status does not by itself make it SoTA.

Bounded choice for ordinary technical prose. Compare the audience-sensitive whole-span reading with cue-led sentence revision: find listed suspect expressions, improve their wording, and retain true ontological distinctions. The latter was the working default in the R11 case. It left “The evidence does not notice the error and does not begin a new cycle” after fluent rewriting because those verbs were outside the selector and the denial was true. With the same paragraph available, F.19's reading recovers the reader's already stated checking or revision, finds no independently grounded reader mistake that the denial prevents, and deletes the denial. The positive action stays; no new action is inferred from the deleted sentence.

Use one bounded reread of the same paragraph or short instruction as the comparison allowance. On the ordinary sentence “The diagram shows the dependency”, both approaches retain the wording; F.19 expressly preserves its recoverable metonymy. On the operational-detail case, applying either approach with meaning preservation rejects “Cook until ready”: it discards “five minutes after simmer begins”. The additional F.19 move is to examine the contribution and participants of an unflagged proposition, rather than taking a clear and locally true sentence as sufficient. Adapt the audience-sensitive line in F.19:4 steps 1–7 and CC-F19-9/CC-F19-12/CC-F19-17; keep lexical cues for recall. The accepted trade-off is a contextual judgement about each claim, including unflagged claims, instead of a fully mechanical vocabulary check. These are qualitative case comparisons, not measured timing or a controlled-language compliance test. Reopen the choice if that judgement repeatedly rejects useful prose or a lighter method catches the same defects while preserving the same uses.

#Relations

#F.19:End

---

Last Updated: 2026-09-10 — upstream FPF commit a87d0ef4 (github.com/ailev/FPF)