chaffjs 0.30.0 → 0.32.0

package/dist/whole-word-runs.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"whole-word-runs.d.ts","sourceRoot":"","sources":["../src/whole-word-runs.ts"],"names":[],"mappings":"AAAA,mEAAmE;AACnE,MAAM,MAAM,cAAc,GAAG;IAAE,QAAQ,CAAC,OAAO,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,IAAI,EAAE;QAAE,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;QAAC,QAAQ,CAAC,GAAG,EAAE,MAAM,CAAA;KAAE,CAAA;CAAE,CAAC;AAE3H,wHAAwH;AACxH,MAAM,MAAM,YAAY,GAAG;IAAE,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,IAAI,EAAE,MAAM,CAAA;CAAE,CAAC;AAEpG,+DAA+D;AAC/D,MAAM,MAAM,WAAW,GAAG,WAAW,CAAC,MAAM,CAAC,GAAG,WAAW,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;AAE5E,wGAAwG;AACxG,eAAO,MAAM,oBAAoB,IAAI,CAAC;AAgBtC;;;GAGG;AACH,eAAO,MAAM,aAAa,GAAI,QAAQ,SAAS,cAAc,EAAE,EAAE,OAAO,WAAW,KAAG,YAAY,EAOtF,CAAC"}

package/dist/whole-word-runs.js

@@ -0,0 +1,26 @@
+/** お + 嬢 + さま is the longest cut seen; a listed word is not looked for across more tokens than this. */
+export const MAX_WHOLE_WORD_PARTS = 3;
+const joinedSurface = (tokens, first, last) => tokens
+    .slice(first, last + 1)
+    .map((token) => token.surface)
+    .join("");
+/** The longest listed word written by tokens from `first` on, each touching the one before. */
+const longestFrom = (tokens, first, words) => {
+    const lasts = Array.from({ length: MAX_WHOLE_WORD_PARTS }, (_, extra) => first + extra).filter((last) => last < tokens.length);
+    const touching = lasts.filter((last) => tokens.slice(first + 1, last + 1).every((token, at) => tokens[first + at]?.span.end === token.span.start));
+    const written = touching.map((last) => ({ first, last, word: joinedSurface(tokens, first, last) }));
+    return written.filter(({ word }) => words.has(word)).at(-1);
+};
+/**
+ * The listed words in a sentence's tokens, each one run, however the tokenizer cut it: お客様 is one token and お客さま is お客 and
+ * さま, and the さま must not be read as the さま written after a name. Runs do not overlap; the earlier one wins.
+ */
+export const wholeWordRuns = (tokens, words) => words.size === 0
+    ? []
+    : tokens.reduce((runs, _, first) => {
+        if ((runs.at(-1)?.last ?? -1) >= first)
+            return runs;
+        const run = longestFrom(tokens, first, words);
+        return run === undefined ? runs : [...runs, run];
+    }, []);
+//# sourceMappingURL=whole-word-runs.js.map

package/dist/whole-word-runs.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"whole-word-runs.js","sourceRoot":"","sources":["../src/whole-word-runs.ts"],"names":[],"mappings":"AASA,wGAAwG;AACxG,MAAM,CAAC,MAAM,oBAAoB,GAAG,CAAC,CAAC;AAEtC,MAAM,aAAa,GAAG,CAAC,MAAiC,EAAE,KAAa,EAAE,IAAY,EAAU,EAAE,CAC/F,MAAM;KACH,KAAK,CAAC,KAAK,EAAE,IAAI,GAAG,CAAC,CAAC;KACtB,GAAG,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,OAAO,CAAC;KAC7B,IAAI,CAAC,EAAE,CAAC,CAAC;AAEd,+FAA+F;AAC/F,MAAM,WAAW,GAAG,CAAC,MAAiC,EAAE,KAAa,EAAE,KAAkB,EAA4B,EAAE;IACrH,MAAM,KAAK,GAAG,KAAK,CAAC,IAAI,CAAC,EAAE,MAAM,EAAE,oBAAoB,EAAE,EAAE,CAAC,CAAC,EAAE,KAAK,EAAE,EAAE,CAAC,KAAK,GAAG,KAAK,CAAC,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,GAAG,MAAM,CAAC,MAAM,CAAC,CAAC;IAC/H,MAAM,QAAQ,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,MAAM,CAAC,KAAK,CAAC,KAAK,GAAG,CAAC,EAAE,IAAI,GAAG,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE,EAAE,EAAE,CAAC,MAAM,CAAC,KAAK,GAAG,EAAE,CAAC,EAAE,IAAI,CAAC,GAAG,KAAK,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC,CAAC;IACnJ,MAAM,OAAO,GAAG,QAAQ,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,EAAE,IAAI,EAAE,aAAa,CAAC,MAAM,EAAE,KAAK,EAAE,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC;IACpG,OAAO,OAAO,CAAC,MAAM,CAAC,CAAC,EAAE,IAAI,EAAE,EAAE,EAAE,CAAC,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,CAAC;AAC9D,CAAC,CAAC;AAEF;;;GAGG;AACH,MAAM,CAAC,MAAM,aAAa,GAAG,CAAC,MAAiC,EAAE,KAAkB,EAAkB,EAAE,CACrG,KAAK,CAAC,IAAI,KAAK,CAAC;IACd,CAAC,CAAC,EAAE;IACJ,CAAC,CAAC,MAAM,CAAC,MAAM,CAAiB,CAAC,IAAI,EAAE,CAAC,EAAE,KAAK,EAAE,EAAE;QAC/C,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC,CAAC,EAAE,IAAI,IAAI,CAAC,CAAC,CAAC,IAAI,KAAK;YAAE,OAAO,IAAI,CAAC;QACpD,MAAM,GAAG,GAAG,WAAW,CAAC,MAAM,EAAE,KAAK,EAAE,KAAK,CAAC,CAAC;QAC9C,OAAO,GAAG,KAAK,SAAS,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,GAAG,IAAI,EAAE,GAAG,CAAC,CAAC;IACnD,CAAC,EAAE,EAAE,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chaffjs",
-  "version": "0.30.0",
+  "version": "0.32.0",
   "description": "Prose validation harness. Finds what is hard to read, and never rewrites it for you.",
   "keywords": [
     "chaff",
@@ -67,6 +67,7 @@
   "files": [
     "LICENSE",
     "README.md",
+    "README.ja.md",
     "bin",
     "dist",
     "genres.yaml",
@@ -87,8 +88,8 @@
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.125.0",
-    "@chaffjs/lang-en": "0.27.0",
-    "@chaffjs/lang-ja": "0.29.0",
+    "@chaffjs/lang-en": "0.29.0",
+    "@chaffjs/lang-ja": "0.31.0",
     "character-entities": "^2.0.2",
     "mdast-util-from-markdown": "^2.0.3",
     "mdast-util-frontmatter": "^2.0.1",

package/profiles/listing.yaml

@@ -0,0 +1,20 @@
+id: listing
+
+name:
+  ja: 不動産の物件広告
+  en: Property listing
+
+why:
+  ja: 日本の不動産の広告は、徒歩の分数を道路距離80mを1分として出し、1分未満の端数を1分に切り上げると決められています（不動産の表示に関する公正競争規約施行規則）。物件広告では、速さを書いていなくても、この速さで徒歩の分数と距離を比べます。ほかの文書の徒歩の分数は、速さを書いたときだけ比べます。
+  en: Japanese property advertising computes walking times at 80 m of road per minute, a part minute rounded up (the real-estate fair-competition code). In a Japanese listing, walking times are compared with their distances at that rate even when it is not written. There is no such standard for English listings, so this profile has no English part.
+
+# 設定（chaff.yaml の profile / by_path）が無いときに、内容から選ぶ。物件概要の項目（交通、賃料、敷金、間取り…）の行が
+# min_lines 行以上あれば物件広告として読む。表の行（| 賃料 | …）も、「賃料：…」の行も数える。
+detect:
+  ja:
+    line: "^[ \\t]*\\|?[ \\t]*(?:交通|賃料|家賃|管理費|共益費|敷金|礼金|保証金|間取り|専有面積|入居可能日|築年月)[ \\t]*[|｜:：]"
+    min_lines: 3
+
+ja:
+  # 文書に速さを書いていないときの、徒歩の分数の速さ。1分に歩く m と、端数を切り上げるか（walk-time-distance-mismatch）。
+  walk_rate: { metres_per_minute: 80, round_up: true }

package/rules/absolute-exception.yaml

@@ -43,7 +43,7 @@ off_for:
 group: structure
 summary:
   ja: 「すべての〜は…しなければならない」と言い切った決まりに、別の条や段落で「ただし…を除く」と例外を書いた所
-  en: 'A rule stated without exception ("must always") that another article or paragraph makes an exception to ("except")'
+  en: A rule said to have no exception ("must always") that another part excepts
 example:
   ja:
     before: |

package/rules/ai-generated-composite.yaml

@@ -49,7 +49,7 @@ off_for:
 group: ai-tells
 summary:
   ja: 生成された文章の特徴がいくつも一つの文書にそろっている所（生成だと決めつけはしません）
-  en: Several signals of generated text together in one document (a place to reread, not a verdict)
+  en: Many signs of generated text in one document (a place to reread, not a verdict)
 example:
   ja:
     config: { genre: blog/tech, rules: { ai-generated-composite: strict } }

package/rules/ai-tell.yaml

@@ -36,7 +36,7 @@ sources: [kobak-2025, liang-2024, juzek-ward-2025]
 group: ai-tells
 summary:
   ja: 「重要な役割を果たす」「と言えるでしょう」のような、生成された文章にありがちな言い回しが重なった所
-  en: Phrases common in generated text ("delve into", "plays a crucial role") piling up
+  en: Phrases common in generated text ("delve into", "plays a crucial role") piled up
 example:
   ja:
     before: |

package/rules/amount-range-reversed.yaml

@@ -31,7 +31,7 @@ off_for:
 group: facts
 summary:
   ja: 「月給30万円〜25万円」のように、金額の範囲の終わりが始まりより小さい所
-  en: An amount range whose second amount is smaller than its first, such as "$90,000–$70,000"
+  en: An amount range that ends lower than it starts, such as "$90,000–$70,000"
 example:
   ja:
     before: |

package/rules/amount-scale-consistency.yaml

@@ -27,7 +27,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: consistency
 summary:
   ja: 「30万円」と「250,000円」のように、同じ桁の金額を「万」と数字だけの二通りで書いている所
-  en: Amounts of one order of magnitude written both with and without a word of scale, such as "$1.5 million" and "$2,500,000"
+  en: Amounts written with and without a scale word ("$1.5 million", "$2,500,000")
 example:
   ja:
     before: |

package/rules/announced-count-mismatch.yaml

@@ -60,5 +60,5 @@ example:
       - Your bank account
 
 not_flagged:
-  ja: 目安の数（約3点、3つ以上）、順番（3つ目）、選ぶ数（以下から1つ選ぶ）、見出しや表の前の数、箇条書きがすぐ後ろに無い数は比べません。予告の文に数が二つあるときも比べません。コロンだけで予告する文は、コロンにいちばん近い数を予告の数とみなし、その数の後ろにまだ数があれば比べません（「1 つのページを 2 ページに分けました:」）。どの行も「ラベル：A / B」の形の箇条書きは、斜線（/）で区切って並べた項目の数が合っていれば指摘しません。一行に並べた名前は、区切りが決まらないとき（名前の中に「と」「・」がある、括弧が閉じていない、途中で文が終わる）と、並びが閉じていないとき（「ほか」「など」で終わる、「5名ほか」）は比べません。
-  en: An estimate (about three, three or more), a rank (the first three), how many to pick (choose two), a number before a heading or a table, and a number with no list right after it are not compared. Nor is a sentence with two numbers in it. When only a colon announces the list, the number nearest the colon is the count, so a number followed by another one is not compared ("We merged three tasks into 2 pages:"). A list whose every item is a label, a colon and members split at slashes is not reported when the members add up to the count. Names listed on one line are not compared when the split is unclear ("and" or "&" inside a name, an unclosed bracket, a sentence ending midway) or the list is left open ("etc.", "and others").
+  ja: 目安の数（約3点、3つ以上）、順番（3つ目）、選ぶ数（以下から1つ選ぶ）、条や節の番号（7.1、第3条）、見出しや表の前の数、箇条書きがすぐ後ろに無い数は比べません。予告の文に数が二つあるときも比べません。コロンだけで予告する文は、コロンにいちばん近い数を予告の数とみなし、その数の後ろにまだ数があれば比べません（「1 つのページを 2 ページに分けました:」）。どの行も「ラベル：A / B」の形の箇条書きは、斜線（/）で区切って並べた項目の数が合っていれば指摘しません。一行に並べた名前は、区切りが決まらないとき（名前の中に「と」「・」がある、括弧が閉じていない、途中で文が終わる）と、並びが閉じていないとき（「ほか」「など」で終わる、「5名ほか」）は比べません。
+  en: An estimate (about three, three or more), a rank (the first three), how many to pick (choose two), the number of a clause or section (7.1, Article 7), a number before a heading or a table, and a number with no list right after it are not compared. Nor is a sentence with two numbers in it. When only a colon announces the list, the number nearest the colon is the count, so a number followed by another one is not compared ("We merged three tasks into 2 pages:"). A list whose every item is a label, a colon and members split at slashes is not reported when the members add up to the count. Names listed on one line are not compared when the split is unclear ("and" or "&" inside a name, an unclosed bracket, a sentence ending midway) or the list is left open ("etc.", "and others").

package/rules/announcing-opener.yaml

@@ -35,7 +35,7 @@ off_for:
 group: ai-tells
 summary:
   ja: 「重要なのは、」「ポイントは、」「正直に言うと、」のように、中身の前に予告する文頭が重なっている所
-  en: 'Openers that announce a point before making it ("The key point is", "Here''s the thing", "Honestly,") piling up'
+  en: Openers that announce a point before making it ("The key point is") piled up
 example:
   ja:
     before: |

package/rules/annual-holidays-mismatch.yaml

@@ -0,0 +1,65 @@
+id: annual-holidays-mismatch
+layer: L3
+status: stable
+how_to_find: annual-holidays-mismatch
+# The labels are annual-holidays-label; the weekly phrases and the days a year each gives are weekly-days-off (every-week
+# gives a minimum, not-every-week gives none); the other words are annual-holidays-word, approximate-marker,
+# range-connector and amount-range-word.
+severity: warning
+
+name:
+  ja: 毎週の休みから決まる日数より少ない年間休日
+  en: Annual days off fewer than the weekly days off give
+
+why:
+  ja: 求人の「完全週休2日制」は毎週2日休むという意味なので、一年（52週）で少なくとも104日の休みになります。そこに「年間休日 90日」と書いてあれば、どちらかが間違いです。別の求人の行を写したときや、休日の制度だけを書き直したときに起きます。年間休日の日数を、毎週の休みの語から決まる最低の日数（完全週休2日制と4週8休は104日、完全週休3日制は156日）と比べ、少ないときだけ指します。祝日・夏季休暇・年末年始で多くなるのは普通なので、多い方は見ません。「完全」の付かない「週休2日制」は「月に1回以上、2日休む週がある」という意味で、毎週2日休むとは限らないので比べません。この区別は語彙表（weekly-days-off）に書いてあります。
+  en: '"Two days off every week" in a job posting means at least 104 days off in a year of 52 weeks, so "Annual days off: 90 days" beside it cannot both be right. It happens when a line is copied from another posting, or when the weekly days off are rewritten and the annual count is not. The annual count of days off is compared with the fewest the weekly phrase gives (two days off every week or a five-day work week is 104, three days off every week or a four-day work week is 156) and pointed out only when it is fewer. More is normal (public holidays, summer, the new year) and is not looked at. Only phrases that say every week count; vague ones ("weekends off", "two days off a week") are not compared. The phrases and their minimums are in the weekly-days-off lexicon.'
+
+message:
+  ja: 年間休日（{written}）が、「{weekly}」から決まる最低の{minimum}日より少なくなっています
+  en: 'The annual days off ({written}) are fewer than the {minimum} days a year that "{weekly}" gives'
+
+how_to_fix:
+  ja: 年間休日と休日の制度のどちらが正しいかを確かめて、もう片方を直してください。毎週2日休めない週があるなら「完全」を外して「週休2日制」と書いてください。
+  en: Check which of the annual days off and the weekly days off is right, and correct the other. If some weeks have fewer days off, say so instead of "every week".
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 「完全週休2日制」で「年間休日 90日」のように、毎週の休みから決まる104日より少ない年間休日
+  en: Annual days off fewer than the 104 days that two days off every week give
+example:
+  ja:
+    before: |
+      | 項目 | 内容 |
+      | --- | --- |
+      | 休日 | 完全週休2日制（土曜日・日曜日）、祝日 |
+      | 年間休日 | 90日 |
+    after: |
+      | 項目 | 内容 |
+      | --- | --- |
+      | 休日 | 完全週休2日制（土曜日・日曜日）、祝日 |
+      | 年間休日 | 125日 |
+  en:
+    before: |
+      | Item | Details |
+      | --- | --- |
+      | Days off | Two days off every week (Saturday and Sunday) and public holidays |
+      | Annual days off | 90 days |
+    after: |
+      | Item | Details |
+      | --- | --- |
+      | Days off | Two days off every week (Saturday and Sunday) and public holidays |
+      | Annual days off | 125 days |
+
+not_flagged:
+  ja: 「完全」の付かない週休2日制・週休3日制が文書のどこかにあれば比べません（毎週2日休むとは限らないため）。「完全週休2日制ではありません」のように打ち消したもの、同じ行に「除く」「ただし」「出勤」などの例外の語があるものも比べません。年間休日は「年間休日」「年間休日数」などの見出しの日数だけを読み、年次有給休暇の日数は読みません。「約」「以上」「から」の付いた日数、「100〜120日」のような幅、年間休日の日数が二つ以上あって違う文書、毎週の休みの語が二つ以上あって最低の日数が違う文書（職種ごとに違う求人など）も比べません。休みの多い方は見ません。
+  en: 'Only phrases that say every week count ("two days off every week", "a five-day work week"); "weekends off" and "two days off a week" are not compared. A phrase that is negated in its sentence ("does not offer two days off every week") or followed on its line by an exception ("except", "excluding", "some Saturdays worked") leaves the posting unchecked. Only an annual count of every day off is read ("Annual days off", "days off a year"): "annual holidays" and "annual leave" are paid leave in British usage and are not read. A count with "about", "from", "or more" or "+", a range ("100–120 days"), a posting with two different annual counts, and one whose weekly phrases give different minimums (one per role) are not compared. More days off than the minimum is never pointed out.'
+level_meaning:
+  ja: 年間休日が毎週の休みから決まる最低の日数より少ないとき指摘
+  en: reported when the annual days off are fewer than the weekly days off give

package/rules/annual-pay-mismatch.yaml

@@ -0,0 +1,64 @@
+id: annual-pay-mismatch
+layer: L3
+status: stable
+how_to_find: annual-pay-mismatch
+# The amounts are read with currency-notation and amount-multiplier; the labels are annual-pay-label, the other words
+# annual-pay-word, approximate-marker, duration-month, number-word (digit), range-connector and amount-range-word.
+severity: warning
+
+name:
+  ja: 月給と賞与から計算した額と合わない年収例
+  en: An example annual pay that is not the monthly pay and bonus
+
+why:
+  ja: 求人の「年収例 450万円（月給28万円の場合）」は、読み手が月給と賞与から確かめずに信じる数字です。月給や賞与の月数を書き直したときや、別の求人の行を写したときに、年収例だけが古いまま残ります。年収例・想定年収の金額を、月給の12か月分と賞与の月数分を足した額（月給28万円、賞与3ヶ月分なら28万円 × 15 = 420万円）と比べます。月給と賞与は、年収例の行に書いてあればそれを、無ければ文書に一つだけ書いてあるものを使います。年収例は書いた桁までの丸めを認めます（「420万円」なら1万円未満の差、数字だけの「4,200,000円」なら1,000円未満の差）。年収例と月給がどちらも幅で書いてあれば、下の端どうし・上の端どうしを比べます。
+  en: 'A posting''s "Example annual pay: $75,000 (with a monthly salary of $4,800)" is a figure readers believe without working it out. It goes wrong when the monthly pay or the bonus is changed and the example is not, or a line is copied from another posting. An example annual pay is compared with twelve months of the monthly pay plus the bonus months ($4,800 with three months of bonus is $4,800 × 15 = $72,000). The monthly pay and the bonus are those on the annual line, else the one each the posting states. The annual figure may be rounded to its last written place ("$72k" to a thousand; plain digits to a thousand). When both the annual pay and the monthly pay are ranges, the low ends and the high ends are compared.'
+
+message:
+  ja: 年収 {annual} が、月給 {monthly} の12か月分と賞与 {bonus} を足した{months}か月分と合いません
+  en: "{annual} is not {months} months of the monthly pay {monthly} (twelve months and a bonus of {bonus})"
+
+how_to_fix:
+  ja: 月給・賞与の月数・年収例のどれが正しいかを確かめて、ほかを直してください。年収例に残業代や手当を含めるなら、そう書いてください。
+  en: Check which of the monthly pay, the bonus and the annual figure is right, and correct the others. If the annual figure includes overtime or allowances, say so.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 「月給28万円、賞与3ヶ月分」で「年収例 450万円」のように、月給の12か月分と賞与を足した額と合わない年収例
+  en: An example annual pay that is not 12 months' pay plus the bonus months
+example:
+  ja:
+    before: |
+      | 項目 | 内容 |
+      | --- | --- |
+      | 賞与 | 年2回（合計で月給の3ヶ月分） |
+      | 年収例 | 450万円（入社3年目、月給28万円の場合） |
+    after: |
+      | 項目 | 内容 |
+      | --- | --- |
+      | 賞与 | 年2回（合計で月給の3ヶ月分） |
+      | 年収例 | 420万円（入社3年目、月給28万円の場合） |
+  en:
+    before: |
+      | Item | Details |
+      | --- | --- |
+      | Bonus | Twice a year, three months' salary in total |
+      | Example annual pay | $75,000 (with a monthly salary of $4,800) |
+    after: |
+      | Item | Details |
+      | --- | --- |
+      | Bonus | Twice a year, three months' salary in total |
+      | Example annual pay | $72,000 (with a monthly salary of $4,800) |
+
+not_flagged:
+  ja: 月給・賞与の月数（「賞与なし」を含む）・年収例の三つがそろわない求人は比べません。年俸・年俸制の語がある文書は比べません（月給が年俸の12分の1とも14分の1・16分の1ともありうるため）。ただの「年収」（平均年収など）は年収例として読みません。年収例の行か、年収例について書いた文に残業・時間外・手当・インセンティブ・歩合・みなしの語があれば、その文書の年収例は比べません。「約」「以上」「から」の付いた額、「400万円〜」のように開いた幅、片方だけが幅の組、月給の違う行が二つ以上ある文書、賞与の月数が「2〜3ヶ月」のような幅のもの・「各1ヶ月」のように1回あたりのもの・「夏1ヶ月、冬1ヶ月」のように月数が二つあるもの・「年2回、1ヶ月分」のように「計」「合計」の無いもの・金額で書いたもの・「別途」「決算賞与」のあるものも比べません。「給与」の見出しは「月額」「/月」があるときだけ月給として読みます。通貨の違う額は比べません。
+  en: 'A posting without all three of a monthly pay, a bonus in months (or "no bonus") and an annual figure is not compared. A document that mentions an annual salary is not compared, since its monthly pay may be the salary over 12, 14 or 16, and a bare "annual pay" (an average, a past pay) is not read as an example. When the annual line or a sentence about it mentions overtime, allowances, incentives, commission or tips, the document''s annual figures are not compared. An amount with "about", "from", "or more" or "+", an open range, a range on one side only, a posting that states two different monthly pays, and a bonus given as a range of months, per payment ("one month each"), as two counts, paid more than once a year without "in total" ("twice a year, one month"), as an amount, or with another bonus besides are not compared. A "Salary" label is read as monthly only with "a month" or "per month" beside it. Amounts in different currencies are not compared.'
+level_meaning:
+  ja: 年収例が月給の12か月分と賞与の月数分を足した額と合わないとき指摘
+  en: reported when an example annual pay is not twelve months of the monthly pay plus the bonus

package/rules/article-sound.yaml

@@ -33,7 +33,7 @@ off_for:
 group: slips
 summary:
   ja: 英語で、「a apple」「an user」のように、次の語の音に合わない a / an
-  en: '"a" before a vowel sound or "an" before a consonant sound, such as "a apple" or "an user"'
+  en: '"a" or "an" that does not fit the next sound, as in "a apple" or "an user"'
 example:
   en:
     before: |

package/rules/assistant-residue.yaml

@@ -34,7 +34,7 @@ sources: [hayashi-aizawa-2026]
 group: ai-tells
 summary:
   ja: 「私の知識は」「お役に立てれば幸いです」のような、チャットの返事を貼ったときに残る言葉
-  en: What a pasted chat reply leaves behind ("As of my last knowledge update", "I hope this helps")
+  en: Words left from a pasted chat reply, such as "I hope this helps"
 example:
   ja:
     before: |

package/rules/attachment-not-attached.yaml

@@ -33,7 +33,7 @@ off_for:
 group: facts
 summary:
   ja: 本文が「添付します」と書いているのに、添付の欄もファイル名も無いメール
-  en: An email that says something is attached but shows no attachment line or file name
+  en: An email that says something is attached but shows no attachment
 example:
   ja:
     config: { genre: business/email }

package/rules/backorder-mismatch.yaml

@@ -0,0 +1,57 @@
+id: backorder-mismatch
+layer: L3
+status: stable
+how_to_find: backorder-mismatch
+# The ordered, delivered and backordered columns are found by the language's order-quantity-column lexicon.
+extra_word_lists: [order-quantity-column]
+severity: warning
+
+name:
+  ja: 残数が発注数量から納品数量を引いた数と合わない
+  en: A backordered quantity that is not the ordered less the delivered
+
+why:
+  ja: 納品書の分納の欄や発注残の一覧では、残数（未納数、発注残）は同じ行の発注数量から納品数量を引いた数です。読み手は残りがいくつ届くかをこの数で知り、引き算し直しません。納品数量だけを直したとき、別の行の残数を写したとき、桁を打ち間違えたときに食い違います。どの列が発注数量、納品数量、残数かは、列の見出しの語（発注数量、納品数量、残数、未納数、Ordered、Delivered、Backordered、Remaining）だけで決めます。列の並びでは決めません。比べるのは、三つの升がどれも同じ単位の書いた整数である行だけです。
+  en: "In the backorder section of a delivery note or a list of open orders, the backordered (remaining, outstanding) quantity of a row is the ordered quantity less the delivered quantity of the same row. Readers learn from it how much is still to come and do not do the subtraction again. It goes wrong when only the delivered quantity is corrected, when the remainder of another row is copied, or when a digit is mistyped. Which column is ordered, delivered and backordered is decided by the heading words alone (Ordered, Delivered, Shipped, Backordered, Remaining, Outstanding), never by where a column stands. Only rows where all three cells are written whole numbers in the same unit are compared."
+
+message:
+  ja: 残数「{backordered}」は、同じ行の発注数量と納品数量からは {computed} です
+  en: 'The backordered quantity "{backordered}" is written, but the ordered and delivered quantities on the row give {computed}'
+
+how_to_fix:
+  ja: 発注数量、納品数量、残数のどれが正しいかを確かめて、ほかを直してください。
+  en: Check which of the ordered, delivered and backordered quantities is right, and correct the others.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 表の同じ行で、残数が発注数量から納品数量を引いた数と違う所
+  en: A backordered quantity that is not the ordered less the delivered on its row
+example:
+  ja:
+    before: |
+      | 品名 | 発注数量 | 納品数量 | 残数 |
+      | --- | --- | --- | --- |
+      | ホッチキス針 | 50箱 | 30箱 | 25箱 |
+    after: |
+      | 品名 | 発注数量 | 納品数量 | 残数 |
+      | --- | --- | --- | --- |
+      | ホッチキス針 | 50箱 | 30箱 | 20箱 |
+  en:
+    before: |
+      | Item | Ordered | Delivered | Backordered |
+      | --- | --- | --- | --- |
+      | Staples (box) | 50 boxes | 30 boxes | 25 boxes |
+    after: |
+      | Item | Ordered | Delivered | Backordered |
+      | --- | --- | --- | --- |
+      | Staples (box) | 50 boxes | 30 boxes | 20 boxes |
+
+not_flagged:
+  ja: 発注数量、納品数量、残数の列のどれかが無い表、どれかの列が二つ以上ある表（前回と今回の納品数量は、片方だけでは残りを決めない）は比べません。発注と納品の両方を言う見出しの列がある表も比べません。升が空、「-」、「未定」、小数、符号やかっこ付き、「以上」「程度」の付いた行、三つの升の単位が違う行も比べません。ほかの列にも同じ単位の数がある行（期首在庫）は、残数がそれも数えているかもしれないので比べません。納品数量が発注数量より多い行は、残数を比べず delivered-over-ordered に任せます。
+  en: "A table missing the ordered, delivered or backordered column, or with two of any of them (delivered previously and now: neither alone says what is left), is not compared. Neither is a table with a heading that names both ordered and delivered. A row whose cell is blank, a dash, TBD, a decimal, signed, bracketed or a bound (10 or more), or whose three cells are in different units, is skipped. A row with another count in the same unit (opening stock) is skipped: the remainder may count it too. A row that delivered more than was ordered is left to delivered-over-ordered and its remainder is not compared."

package/rules/bmi-mismatch.yaml

@@ -0,0 +1,63 @@
+id: bmi-mismatch
+layer: L3
+status: stable
+how_to_find: bmi-mismatch
+severity: warning
+
+name:
+  ja: BMI が身長と体重から出る値と合わない
+  en: A BMI the height and weight beside it do not give
+
+why:
+  ja: 健診の結果の「BMI 22.0」は、同じ人の体重（kg）を身長（m）の二乗で割った値です。読み手は割り算し直さずに信じます。体重だけを直したとき、BMI を去年の結果や別の人の欄から写したときに食い違います。一つの節（見出しから次の見出しまで）を一人の結果として読み、その節に身長・体重・BMI の行が一つずつ、同じ表に（または三つとも「身長：160.0 cm」のような「名前：値」の行に）あれば、列ごとに比べます。身長は cm や m、体重は kg で、単位を値の後ろか行の見出しの括弧に書いたものを読みます。語彙表の単位（ft、in、lb）も換算して読みます。どの語が身長・体重・BMI かは、言語パッケージの語彙表 bmi-term にあります。書いた数はどれも、最後の桁の半分までの丸めを認めます（22.0 は 21.95 から 22.05、160.0 cm は 159.95 cm から 160.05 cm）。身長と体重の丸めの範囲で出る BMI のいちばん小さい値（いちばん軽い体重 ÷ いちばん高い身長²）からいちばん大きい値までに、BMI の丸めの範囲が少しでも重なれば言いません。
+  en: The "BMI 22.0" of a checkup result is the weight in kilograms of the same person divided by the square of their height in metres. Readers trust it without working it out again. It goes wrong when the weight is corrected and the BMI is not, or when the BMI is copied from last year's result or another person's. One section (a heading to the next) is read as one person's results. When it has one height, one weight and one BMI row, in one table (or all three as lines of a name, a colon and a value, such as "Height" then "178 cm"), they are compared column by column. A height in cm or m and a weight in kg are read, with the unit after the value or in brackets in the row label; the other units of the lexicons (ft, in, lb) are converted too. Which words name a height, a weight and a BMI is in the language package's lexicon bmi-term. Every written number may be rounded to half its last digit (22.0 is anything from 21.95 to 22.05, 178 cm from 177.5 to 178.5 cm). A BMI is not reported when its rounding overlaps the range the height and weight can give, from the lightest weight over the tallest height squared to the heaviest weight over the shortest.
+
+message:
+  ja: 「BMI {written}」は、身長と体重からは {computed} です
+  en: "BMI {written} is written, but the height and weight give {computed}"
+
+how_to_fix:
+  ja: 身長・体重・BMI のどれが正しいかを確かめて、ほかを直してください。
+  en: Check which of the height, the weight and the BMI is right, and correct the others.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 健診の BMI が、体重 ÷ 身長² と合わない所
+  en: A BMI in a checkup that the weight divided by the height squared does not give
+example:
+  ja:
+    before: |
+      | 項目 | 結果 |
+      | --- | --- |
+      | 身長 | 160.0 cm |
+      | 体重 | 56.3 kg |
+      | BMI | 24.0 |
+    after: |
+      | 項目 | 結果 |
+      | --- | --- |
+      | 身長 | 160.0 cm |
+      | 体重 | 56.3 kg |
+      | BMI | 22.0 |
+  en:
+    before: |
+      | Item | Result |
+      | --- | --- |
+      | Height | 178 cm |
+      | Weight | 74.0 kg |
+      | BMI | 21.4 |
+    after: |
+      | Item | Result |
+      | --- | --- |
+      | Height | 178 cm |
+      | Weight | 74.0 kg |
+      | BMI | 23.4 |
+
+not_flagged:
+  ja: 身長・体重・BMI のどれかが無い節、二つある節（二人分、前と後）、三つが別々の表にある節、三つの行の升の数が違う表は比べません。範囲（160〜165 cm）、目安（約60 kg）、二つの数（5 ft 10 in）、単位の無い身長や体重、語彙表に無い単位の升、見出しの括弧に単位でないもの（体重（前年）、BMI（パーセンタイル））がある行は読みません。丸めで届く範囲の BMI は言いません。
+  en: "A section without a height, a weight or a BMI, with two of one (two people, a before and an after), with the three in different tables, or whose three rows have different numbers of cells is not compared. A range (160–165 cm), a rough figure (about 60 kg), two numbers (5 ft 10 in), a height or weight with no unit, a unit not in the lexicons, and a row whose label notes something other than a unit in brackets (Weight (last year), BMI (percentile)) are not read. A BMI the rounding of the values can reach is not reported."

package/rules/bold-label-list.yaml

@@ -40,7 +40,7 @@ sources: [zhang-2024]
 group: ai-tells
 summary:
   ja: 「- **速さ**：〜」のように、太字の札とコロンで始まる項目が並び、説明が札の続きだけになっている所
-  en: 'List items that open with a bold label and a colon ("- **Speed**: ..."), one after another'
+  en: List items, one after another, that open with a bold label and a colon
 example:
   ja:
     config: { genre: blog/tech }

package/rules/broken-link.yaml

@@ -39,7 +39,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: structure
 summary:
   ja: 行き先が空のリンク、文書に無い見出しを指すリンク、定義の無い参照の形のリンク
-  en: A link with no destination, a link to a heading the page does not have, or a reference-style link with no definition
+  en: "A link that goes nowhere: no address, a missing heading, or no definition"
 example:
   ja:
     before: |

package/rules/capacity-runtime-mismatch.yaml

@@ -0,0 +1,66 @@
+id: capacity-runtime-mismatch
+layer: L3
+status: stable
+how_to_find: capacity-runtime-mismatch
+# Item names are read with battery-label (capacity, consumption, runtime, standby, peak, bound), units with battery-unit and
+# unit-time, ranges with range-connector, rough values with approximate-marker.
+severity: warning
+
+name:
+  ja: 電池の容量を消費電流で割った時間より長い使用時間
+  en: A runtime longer than the battery capacity divided by the consumption
+
+why:
+  ja: 「容量 5000 mAh、消費電流 500 mA、連続使用時間 15時間」のように書くと、5000 mAh ÷ 500 mA は 10時間なので、15時間はどうやっても届きません。消費電流か使用時間のどちらかを、別の条件の値や別の機種の値に書き換えたときに起きます。実際の使用時間は変換の損失で割り算の値より短くなるのが普通なので、短いほうは言いません。割り算の値を、使用時間の書いた桁の一つ分（15時間なら1時間）より大きく超えたときだけ言います。三つのどれかに「約」「最大」などが付いていれば、その幅を二倍にします。
+  en: 'When a spec states "Capacity 5000 mAh, current draw 500 mA, runtime 15 hours", 5000 mAh at 500 mA lasts 10 hours, so 15 hours cannot be reached. It happens when the consumption or the runtime is replaced with the value of another condition or another model. A real runtime is normally shorter than the division because of conversion losses, so a shorter one is not reported. Only a runtime above the division by more than one step of its last written digit (1 hour for "15 hours") is reported; when any of the three is marked "about" or "up to", that margin is doubled.'
+
+message:
+  ja: "{capacity} ÷ {consumption} は {expected} 時間ですが、使用時間は{runtime}と書かれています"
+  en: "{capacity} at {consumption} lasts {expected} hours, but the runtime is given as {runtime}"
+
+how_to_fix:
+  ja: 容量・消費電流・使用時間が同じ条件の値かを確かめて、違っているほうを直してください。
+  en: Check that the capacity, the consumption and the runtime are values of the same condition, and correct the one that is not.
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: facts
+summary:
+  ja: 「5000 mAh、500 mA、連続使用時間15時間」のように、容量を消費電流で割った時間より長い使用時間
+  en: A runtime longer than the battery capacity divided by its consumption
+example:
+  ja:
+    before: |
+      | 項目 | 仕様 |
+      | --- | --- |
+      | バッテリー容量 | 5000 mAh |
+      | 消費電流 | 500 mA |
+      | 連続使用時間 | 15時間 |
+    after: |
+      | 項目 | 仕様 |
+      | --- | --- |
+      | バッテリー容量 | 5000 mAh |
+      | 消費電流 | 500 mA |
+      | 連続使用時間 | 10時間 |
+  en:
+    before: |
+      | Item | Specification |
+      | --- | --- |
+      | Battery capacity | 50 Wh |
+      | Power consumption | 10 W |
+      | Runtime | 8 hours |
+    after: |
+      | Item | Specification |
+      | --- | --- |
+      | Battery capacity | 50 Wh |
+      | Power consumption | 10 W |
+      | Runtime | 5 hours |
+
+not_flagged:
+  ja: 容量・消費電流・使用時間を、表の行（項目名と値）か「項目名：値」の行に書き、同じ節の同じ表か行にそろっているときだけ読みます。幅の広い表は列ごとに一台と読みます。mAh は mA でだけ、Wh は W でだけ割り、mAh を W で割ることはしません（電圧が公称か動作時かを決められないため）。最大の消費電流（項目名の「最大」、列の見出しの「最大」）は使わず、待機の消費電流は待受時間とだけ組みます。消費電流と使用時間が二つ以上あれば、括弧の中の条件（音量50%）が同じものどうしだけを組みます。範囲（8〜10時間、300〜500 mA）は書き手に有利な端（使用時間の短いほう、消費電流の小さいほう、容量の大きいほう）で比べます。「以上」「以下」「以内」で片側だけを決めた値と、文の中に書いた値は読みません。
+  en: 'Only a capacity, a consumption and a runtime written as table rows (item name and value) or "item name: value" lines, in the same table or the lines of the same section, are read; a wider table is one device per column. mAh is divided only by mA and Wh only by W; mAh is never divided by W, since whether the voltage is the nominal or the operating one cannot be told. A maximum consumption ("max" in the item name, a "Max" column) is not used, and a standby consumption pairs only with a standby time. With two or more consumptions and runtimes, only those with the same condition in brackets ("(50% volume)") are paired. A range ("8-10 hours", "300-500 mA") is compared at the end that favours the writer (the shorter runtime, the smaller consumption, the larger capacity). A value bounded on one side ("at least", "under") and values in running sentences are not read.'
+level_meaning:
+  ja: 容量を消費電流で割った時間を、使用時間が書いた桁を超えて上回るとき指摘
+  en: reported when the runtime is above the capacity divided by the consumption by more than its written precision

package/rules/change-rate-mismatch.yaml

@@ -11,8 +11,8 @@ name:
   en: A rate of change the two values do not give
 
 why:
-  ja: 「前年同月の1,000社から20%増えて1,200社」のように、もとの値・今の値・増減率を一つの文に書くと、読み手は率を確かめずに信じます。数字を一つだけ更新したとき、率だけを去年の文書から写したときに食い違います。一つの文に、もとの値（「から」「に比べて」「前年の」の付いた値）、同じ単位の今の値、向きの語（増加、減少）の付いた百分率が一つずつあるとき、二つの値から率を計算して比べます。率のそばにもとの値が無くても、「昨年の100万円から今年は150万円になり、前年比50%の増加」「2025年度は100万円、2026年度は150万円で」のように二つの値が並んですぐ後に率が続くなら読みます（年が書いてあれば早い年の値がもとの値）。値は書いた桁までの丸めを認めます（12億円は11.5億円から12.5億円のどれか）。
-  en: When one sentence gives the earlier value, the current one and the rate of change ("1,200 companies, up 20% from 1,000"), readers trust the rate without checking it. It goes wrong when one figure is updated and the others are not, or when the rate is copied from last year's text. When a sentence has one earlier value (marked by "from" or "compared with"), one current value in the same unit, and one percentage with a word of direction (up, decline), chaff computes the rate from the two values and compares. The two values may also stand together right before the rate ("rose from $1.0 million last year to $1.5 million, an increase of 50%", "$1.0 million in 2025 and $1.5 million in 2026, up 50%"; with years, the earlier year's value is the earlier one). Each value may be rounded to its last written digit ($12 million is anything from $11.5 million to $12.5 million).
+  ja: 「前年同月の1,000社から20%増えて1,200社」のように、もとの値・今の値・増減率を一つの文に書くと、読み手は率を確かめずに信じます。数字を一つだけ更新したとき、率だけを去年の文書から写したときに食い違います。一つの文に、もとの値（「から」「に比べて」「前年の」の付いた値）、同じ単位の今の値、向きの語（増加、減少）の付いた百分率が一つずつあるとき、二つの値から率を計算して比べます。率のそばにもとの値が無くても、「昨年の100万円から今年は150万円になり、前年比50%の増加」「2025年度は100万円、2026年度は150万円で」のように二つの値が並んですぐ後に率が続くなら読みます（年が書いてあれば早い年の値がもとの値）。今の値は率の後ろでも、「前年同期の2,400百万円から10.0%増加し、2,640百万円となりました」のように動いた先と分かれば読みます。値は書いた桁までの丸めを認めます（12億円は11.5億円から12.5億円のどれか）。表も読みます。見出しの語で前期の列（前期、前年同期）、当期の列（当期、当第2四半期）、増減率の列（増減率、前年同期比）が一つずつ分かる表（見出しの語が無くても、二つの列の見出しに年が一つずつ書いてあれば早い年の列が前期）では、行ごとに二つの値から率を計算し、書いた率と比べます。△・▲・−の付いた率は減少です。「増減」の列は、升に % があるときだけ率と読みます。
+  en: When one sentence gives the earlier value, the current one and the rate of change ("1,200 companies, up 20% from 1,000"), readers trust the rate without checking it. It goes wrong when one figure is updated and the others are not, or when the rate is copied from last year's text. When a sentence has one earlier value (marked by "from" or "compared with"), one current value in the same unit, and one percentage with a word of direction (up, decline), chaff computes the rate from the two values and compares. The two values may also stand together right before the rate ("rose from $1.0 million last year to $1.5 million, an increase of 50%", "$1.0 million in 2025 and $1.5 million in 2026, up 50%"; with years, the earlier year's value is the earlier one). The rate may also come first, with the value reached and then the earlier one ("rose 10.0% to $2,640 million from $2,400 million"). Each value may be rounded to its last written digit ($12 million is anything from $11.5 million to $12.5 million). Tables are read too. When the headings name one column of the earlier value (Prior year), one of the current value (Current year) and one of the rate (YoY, Change (%)), or two columns are each headed by one year (FY2025, FY2026; the earlier year's column holds the earlier value), each row's rate is computed from its two values and compared. A rate marked -, −, ▲ or △ is a decrease. A column headed only "Change" or "Growth" is read as a rate only where its cells carry %.
 
 message:
   ja: 「{rate}%」と書いていますが、二つの値からは {computed}% です
@@ -30,8 +30,8 @@ off_for:
 
 group: facts
 summary:
-  ja: 「1,000社から20%増えて1,200社」のように、一つの文の二つの値と増減率が合わない所
-  en: A rate of change that the two values in the same sentence do not give
+  ja: 「1,000社から20%増えて1,200社」のように、一つの文や表の一行の二つの値と増減率が合わない所
+  en: A rate of change the two values in one sentence or table row do not give
 example:
   ja:
     before: 利用企業は1,300社となり、前年の1,000社から20%増えました。
@@ -41,5 +41,5 @@ example:
     after: Revenue was $1.0 million in 2025 and $1.5 million in 2026, up 50%.
 
 not_flagged:
-  ja: 向きの語の付いた率が二つある文、もとの値が「から」「に比べて」や年で名指されていない文、二つの値と率のあいだで主語が変わる文（「…に増え、利益は20%増えた」）、二つの値のあいだで主語が変わる文（"$1,000 in 2025 and costs were $1,500 in 2026"）、同じ単位の今の値が一つでない文、向きの語が率のそばに無い文は比べません。「前年比20%増」のように値が一つしか無いもの、ポイントの差、倍は見ません。丸めで届く範囲の率は言いません。
-  en: 'A sentence with two rates that each have a word of direction, with no value marked as the earlier one (by a word or a year), with another subject between the values and the rate ("…, and costs rose 20%") or between the two values ("$1,000 in 2025 and costs were $1,500 in 2026"), with no single current value in the same unit, or with no word of direction beside the rate is not compared. A change given with one value ("up 20% year on year"), percentage points and "times" are not read. A rate the rounding of the values can reach is not reported.'
+  ja: 向きの語の付いた率が二つある文、もとの値が「から」「に比べて」や年で名指されていない文、二つの値と率のあいだで主語が変わる文（「…に増え、利益は20%増えた」）、二つの値のあいだで主語が変わる文（"$1,000 in 2025 and costs were $1,500 in 2026"）、同じ単位の今の値が一つでない文、向きの語が率のそばに無い文は比べません。「前年比20%増」のように値が一つしか無いもの、ポイントの差、倍は見ません。丸めで届く範囲の率は言いません。表では、列の役割が見出しから一つずつ決まらない表、前期と当期の列の見出しが違う単位を書いた表（千円と百万円）、値や率の升が数でない行（—、1.0pt、0.5ポイント、(5.0)%）、値が負か百分率の行、二つの値の単位の書き方が違う行、前期の値が0の行は比べません。
+  en: 'A sentence with two rates that each have a word of direction, with no value marked as the earlier one (by a word or a year), with another subject between the values and the rate ("…, and costs rose 20%") or between the two values ("$1,000 in 2025 and costs were $1,500 in 2026"), with no single current value in the same unit, or with no word of direction beside the rate is not compared. A change given with one value ("up 20% year on year"), percentage points and "times" are not read. A rate the rounding of the values can reach is not reported. In a table, nothing is compared when the headings do not name one column for each part or name different units for the two periods (thousand yen, million yen); nor is a row whose value or rate cell is not a number (—, 1.0pt, (5.0)% in brackets), whose values are negative or percentages, whose two values are written with different units, or whose earlier value is zero.'

package/rules/chat-citation-residue.yaml

@@ -28,8 +28,8 @@ use_for: [blog, business, technical, legal, docs, academic, literature, speech]
 
 group: slips
 summary:
-  ja: 「?utm_source=chatgpt.com」の付いたリンクや「oaicite」のように、チャットの答えを貼ったときに残る印
-  en: 'Marks a pasted chat answer leaves behind: links ending in "?utm_source=chatgpt.com", ":contentReference[oaicite:0]"'
+  ja: 「?utm_source=chatgpt.com」の付いたリンクのように、チャットの答えを貼ったときに残る印
+  en: Marks a pasted chat answer leaves behind, such as "?utm_source=chatgpt.com"
 example:
   ja:
     before: |