Skip to content

Commit fb99628

Browse files
abeltranoCopilot
andcommitted
Reconcile no-add-content constraint with defining undefined terms
Address the internal contradiction between the "do not add or remove content" constraint and the requirement to eliminate undefined terms on first use. - revise-for-readability: clarify Non-Goals so a minimal definition or acronym expansion that restates existing meaning counts as prose revision, not new content - readability-revision-workflow: plain-language rule 4 now allows definitions only when they restate meaning already present; otherwise the undefined term is recorded as a residual issue Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 1d26569 commit fb99628

2 files changed

Lines changed: 9 additions & 3 deletions

File tree

protocols/reasoning/readability-revision-workflow.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,10 @@ Plain-language rules:
101101
1. One idea per sentence. Split a sentence that carries more than one.
102102
2. Front-load the point. State the conclusion or action first, then the detail.
103103
3. Prefer the plain word ("use" over "utilize", "help" over "assist").
104-
4. Define a needed term or expand an acronym on first use.
104+
4. Define a needed term or expand an acronym on first use, but only by restating
105+
meaning already present in or established by the document. If a correct
106+
definition would introduce information not derivable from the source, do not
107+
invent it — record the undefined term as a residual issue instead.
105108
5. Vary sentence length so the rhythm is not a drone.
106109
6. Keep terminology consistent — one term per concept, not a rotation of
107110
synonyms.

templates/revise-for-readability.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,8 +96,11 @@ prose becomes short, direct, plain prose; technical meaning stays exact.
9696
edit the prose around them.
9797
- Do NOT rewrite code, data, tables, diagrams, quoted text, or format
9898
scaffolding.
99-
- Do NOT restructure the document, reorder sections, or add or remove content;
100-
this task revises prose, it does not redesign the document.
99+
- Do NOT restructure the document, reorder sections, or add or remove
100+
substantive content or claims; this task revises prose, it does not redesign
101+
the document. Adding a minimal definition or acronym expansion that restates
102+
meaning already present in the source counts as prose revision, not new
103+
content.
101104
- Do NOT report an estimated Flesch score as a computed one, and do NOT claim a
102105
readability gain without a before/after comparison.
103106

0 commit comments

Comments
 (0)