Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:15:10 UTC

WORDING — Repair language without replacing the project question

  • Situation: A load-bearing sentence hides the subject, relation, kind or use, or invites a false inference.
  • Question: What should the reader understand and do, and which distinctions matter for that use?
  • First useful result or blocker: One plain repaired sentence, direct clarification, local naming result, or the missing subject, sense, test, or reader use.
  • Mantra: Recover the ordinary project sentence first. Name what it is about, what it claims, and who must use it; add ontological distinctions only where they change truth, understanding, or action; choose a durable name only when later use needs one; rewrite in plain technical language; check that a reader without private context can recover the intended claim and action; retain a guard only under F.19’s full grounded-contribution test; return to the domain task.
  • Start with: F.19; use E.10 for unresolved FPF wording, and F.18, F.0.1, F.9, or the subject’s direct pattern only when needed.
  • Stop or return: Stop when the reader can understand the claim and carry out its intended use.