F.19:11 - 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.
| Practice question | Exact source and status | Selected payload and limit | Source-use decision, receiving locus, qualification, and reopen |
|---|---|---|---|
| How should ordinary technical prose help its intended reader act without being “dumbed down”? | ISO 24495-1:2023, Plain language — Part 1: Governing principles and guidelines, current published foundation (https://www.iso.org/standard/78907.html); Digital.gov, Principles of plain language and Writing for understanding, current living US-government practice guide (https://digital.gov/guides/plain-language/principles, https://digital.gov/guides/plain-language/writing), checked 2026-08-19. | Declare the reader and task; put the usable object and action first; organize for finding, understanding, and use; keep terms the intended reader needs. Neither source defines FPF ontology or requires expert prose to use general-public vocabulary. | Adapt — reason: these moves improve F.19’s ordinary path without changing its semantic boundary. Receiving loci: F.19:0 first useful move; F.19:4 steps 1 and 7; CC-F19-9 and CC-F19-12. Qualification/currentness: current standard and current practice guide, not FPF semantic authority. Reopen: a new edition changes a used principle, or cold-reader evidence shows that these moves no longer support the declared use. |
| How should plain prose address readers outside the author’s specialty while retaining scientific content? | ISO 24495-3:2026, Plain language — Part 3: Science writing, Edition 1, current published standard (https://www.iso.org/standard/86938.html). | It extends the reader-sensitive principles of Part 1 to science writing for people with different backgrounds and interests. It expressly does not govern specialist scientific writing, and it supplies no test for FPF kinds or terms. | Adapt — reason: the cross-specialty reader boundary sharpens the cold-reader check without authorizing loss of technical content. Receiving loci: F.19:4 step 7 and CC-F19-12. Qualification/currentness: current for plain science communication, not proof that a specialist FPF distinction is dispensable. Reopen: the standard changes materially, or an F.19 case needs a different expert-to-expert boundary. |
| When is controlled technical language worth its added restriction and maintenance cost? | ASD-STE100, Simplified Technical English: Standard for Technical Documentation, Issue 9 (2025-01-15), current issue (https://www.asd-ste100.org/). | Its controlled vocabulary and writing rules reduce lexical and syntactic ambiguity in multilingual, safety-sensitive maintenance documentation. That setting does not show that a controlled dictionary, one-word/one-meaning rule, or compliance apparatus improves ordinary FPF prose. | Reject as the default FPF language; retain as a conditional alternative — reason: the ordinary cases above require recovering contribution and preserving meaning, with no demonstrated need for a maintained controlled lexicon. They do not establish how an STE-compliant treatment would perform. A multilingual maintenance use can justify that separate restriction and its maintenance cost. Receiving loci: F.19:4 step 7 and CC-F19-9/CC-F19-12; no controlled-language machinery is imported. Qualification/currentness: current controlled-language practice with an aerospace-maintenance origin. Reopen: an F.19 case demonstrates that bounded restrictions outperform the ordinary path for its declared reader and risk. |
| What action-guiding detail must survive when the prose tells someone what to do? | IEC/IEEE 82079-1:2019, Preparation of information for use (instructions for use) of products — Part 1: Principles and general requirements, Edition 2, published and marked for revision (https://www.iso.org/standard/71620.html). | It distinguishes step-by-step instructions within information for use and treats usable instructions as purpose- and user-sensitive. Its full information-management process, competency scheme, and evaluation apparatus are much broader than a bounded F.19 rewrite. | Adapt the action-preservation branch; reject the surrounding documentation process — reason: sequence, condition, quantity, warning, and stop detail improve the worked case and checks, while the larger apparatus does not improve them at comparable effort. Receiving loci: F.19:4 step 7, ActionGuidingClaimDetails, the operational-detail case, and CC-F19-9/CC-F19-10/CC-F19-14. Qualification/currentness: current published product-information reference, already marked for revision. Reopen: its successor changes a used principle, or an F.19 case requires a further action detail. |
| Can legally constrained prose become clearer without losing controlled terms or obligations? | ISO 24495-2:2025, Plain language — Part 2: Legal communication, current published standard (https://www.iso.org/standard/85774.html). | The current standard shows that reader access can coexist with nuanced concepts, required structures, rights, and obligations. It does not make legal drafting or disclosure compliance part of ordinary FPF authoring. | Adapt the meaning-preservation lesson; reject legal-process transfer — reason: the branch supports necessary terms without importing a legal-document method. Receiving loci: F.19:4 step 7 and the plain-language-drift and synonym-churn boundaries. Qualification/currentness: current legal-communication guidance. Reopen: F.19 acquires a legal-use case, or a later source changes the retained lesson. |
| Which recurring AI-writing form deserves a contextual reread? | Pew Research Center Data Labs, How Much of the Internet Is Written With AI?, with methodology, published 2026-08-20; checked 2026-09-01. | In dated English Common Crawl pages published after 2022-11-30, the six-month averages plotted at 2023-01 and 2026-01 show negative parallelism rising from 0.87 to 2.36 uses per 10,000 words, while remaining rare. The whole study sampled 490,000 pages; its dated subset is not a random sample of the whole web. | Adapt as a recall cue: inspect contrasts such as not X, but Y through F.19:4’s contribution and plausible-reader tests and CC-F19-17/CC-F19-22. Frequency does not decide whether a particular contrast is useful or who wrote it. Reopen: changed measurement, or actual-use evidence that the cue misses defects or rejects useful contrasts. |
| What prevents a plain rewrite from changing an FPF claim while removing apparatus? | Current FPF patterns E.8, E.10, E.10.ARCH, E.10.ROLE, A.6.F, F.18, A.6.P, and E.21, internal governing dependencies. | They recover the actual word, head, role- or function-shaped claim, relation, name, use, and quality loss before the sentence is shortened. They are not external evidence that F.19 is SoTA. | Adopt as internal dependencies — reason: they define, constrain, or test the meaning that F.19 must preserve. Receiving loci: F.19:4 steps 2–7, the result form, conformance checks, and Relations. Qualification/currentness: current FPF dependencies, kept thin rather than copied here. Reopen: a dependency changes a distinction or check used by F.19. |