chaffjs 0.16.0 → 0.18.0

package/genres.yaml

@@ -5,6 +5,10 @@
 #            A group's rules apply to every genre in it; a genre's own rules win over its group's.
 #            A rule turned off here is listed under "did not run" with the genre as the reason.
 #   profile: the document profile (profiles/*.yaml) this genre reads with, when chaff.yaml names none.
+#   suggest: when no genre is set, what makes a file look like this genre, strongest first:
+#            paths (the file's path), then per language an opening (the body's first line, past front matter and
+#            headings) or a line with min_lines (how many lines must have that shape). A wrong suggestion misleads
+#            more than none, so a cue is added only where the corpus shows it does not fire on other kinds.
 # Which genres a rule applies to at all is the rule's use_for; the numbers behind a level are the rule's by_genre.
 
 groups:
@@ -43,6 +47,10 @@ groups:
       paragraph-length-variance: off
       ai-tell: off
       ai-generated-composite: off
+      contrast-framing: off
+      stock-transition: off
+      announcing-opener: off
+      colon-lead-in: off
   # A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up.
   - id: docs
     name: { ja: 説明書, en: Documentation }
@@ -67,6 +75,10 @@ groups:
       paragraph-length-variance: off
       ai-tell: off
       ai-generated-composite: off
+      contrast-framing: off
+      stock-transition: off
+      announcing-opener: off
+      colon-lead-in: off
   # Science writes in the passive, hedges its claims on purpose (may, suggest) and cites numbers as its evidence.
   - id: academic
     name: { ja: 学術, en: Academic }
@@ -87,6 +99,7 @@ groups:
       rule-of-three: off
       section-length-uniformity: off
       paragraph-length-variance: off
+      stock-transition: off
   # 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.
   - id: literature
@@ -106,6 +119,7 @@ groups:
       no-mixed-desumasu: off
       contraction-consistency: off
       doubled-word: off
+      agreement-slip: off
       agentless-passive: off
       expletive-construction: off
       excessive-hedging: off
@@ -130,11 +144,19 @@ groups:
       paragraph-length-variance: off
       ai-tell: off
       ai-generated-composite: off
+      contrast-framing: off
+      stock-transition: off
+      announcing-opener: off
+      colon-lead-in: off
       dangling-reference: off
       duplicate-definition: off
       date-order: off
       date-weekday-mismatch: off
       total-mismatch: off
+      announced-count-mismatch: off
+      dangling-figure-reference: off
+      date-range-reversed: off
+      percent-sum-mismatch: off
   # A speech opens with greetings and closes with thanks: that is its form, not padding.
   - id: speech
     name: { ja: 話し言葉, en: Speech }
@@ -149,6 +171,10 @@ groups:
       rule-of-three: off
       section-length-uniformity: off
       paragraph-length-variance: off
+      contrast-framing: off
+      stock-transition: off
+      announcing-opener: off
+      colon-lead-in: off
 
 genres:
   - id: technical/spec
@@ -191,6 +217,11 @@ genres:
     summary:
       ja: 仕事のメールと手紙
       en: Work email and letters
+    # A letter is a letter even when it encloses an agreement (an offer letter), so it goes by how it opens.
+    # Not by an addressee line (〇〇御中, To: ...): quotes and proposals open with one too.
+    suggest:
+      ja: { opening: "^(?:拝啓|謹啓|前略)(?:\\s|$)|^件名\\s*[:：]" }
+      en: { opening: "^(?:Dear [^\\n]{1,60}|To whom it may concern)[,:]?$|^Subject\\s*:" }
   - id: business/press-release
     name: { ja: プレスリリース・お知らせ, en: Press release and notice }
     summary:
@@ -221,6 +252,8 @@ genres:
       dangling-reference: normal
       date-weekday-mismatch: normal
       total-mismatch: normal
+      dangling-figure-reference: normal
+      date-range-reversed: normal
   - id: legal/statute
     name: { ja: 法令・規程, en: Statute and regulation }
     summary:
@@ -232,6 +265,16 @@ genres:
       paths: ["(^|/)(laws?|statutes?|regulations?|kitei|kisoku)(/|[-_.])"]
       ja: { line: "(?:この|本)(?:法律|政令|省令|府令|規則|規程|条例|定款|通達)", min_lines: 2 }
       en: { line: "\\b(?:[Tt]his (?:Act|[Pp]art|[Ss]ubpart|[Rr]egulation)|[Tt]hese [Rr]egulations)\\b|^§\\s?\\d", min_lines: 3 }
+    # A statute or an internal rule is read article by article against its own numbers, like a contract.
+    # The statutes in the corpus (yarn corpus) give these no findings, deleted articles (第三条　削除) and 第十条の二 included.
+    rules:
+      numbering-gap: normal
+      duplicate-definition: normal
+      dangling-reference: normal
+      date-weekday-mismatch: normal
+      total-mismatch: normal
+      dangling-figure-reference: normal
+      date-range-reversed: normal
   - id: legal/judgment
     name: { ja: 判決, en: Court decision }
     summary:
@@ -253,10 +296,9 @@ genres:
     summary:
       ja: 使い方の説明・手順書・ヘルプ
       en: User guides, how-to pages and help
+    # Path only: step and procedure headings are as common in tech blogs and specifications as in manuals.
     suggest:
       paths: ["(^|/)(manuals?|guides?|how-?tos?|help|tutorials?|user-?guides?)(/|[-_.])"]
-      ja: { line: "^#{1,6}\\s.*(?:手順|操作方法|設定方法)", min_lines: 2 }
-      en: { line: "^#{1,6}\\s*(?:Steps?\\b|Step \\d|Prerequisites|Before you begin|Troubleshooting)", min_lines: 2 }
   - id: docs/faq
     name: { ja: よくある質問, en: FAQ }
     summary:
@@ -275,6 +317,11 @@ genres:
       paths: ["(^|/)(glossary|glossaries|yogo|用語集)(/|[-_.])"]
       ja: { line: "^#{1,6}\\s*用語集", min_lines: 1 }
       en: { line: "^#{1,6}\\s*Glossary\\b", min_lines: 1 }
+    # A reader looks up one entry and reads only that. A definition is a noun phrase (風の吹いてくる方向。), and sibling
+    # entries share one wording on purpose (Portion of labor productivity change attributed to …), which no reader sees twice.
+    rules:
+      taigen-dome-in-prose: off
+      ngram-repetition: off
   - id: academic/paper
     name: { ja: 論文, en: Academic paper }
     summary:
@@ -293,8 +340,11 @@ genres:
     summary:
       ja: 小説・物語
       en: Novels and stories
+    # A line that is a spoken line (「…」, or 「…」と云った): a sentence in quotes, not a term being defined
+    # (「…」とは, 「…」という, 「…」とする, 「…」と定める, 「…」と称する, 「…」と呼ぶ).
     suggest:
       paths: ["(^|/)(novels?|fiction|stories|shosetsu)(/|[-_.])"]
+      ja: { line: "^「[^」]+」と(?!は|い[うい]|する|定め|称|呼)|^「[^」]*[、。？！…―][^」]*」$", min_lines: 10 }
   - id: literature/essay
     name: { ja: 随筆, en: Literary essay }
     summary:
@@ -305,15 +355,21 @@ genres:
     summary:
       ja: 詩・短歌・俳句
       en: Poems and verse
+    # Verse lines: short lines with no sentence punctuation (a tanka's three lines; a capitalised line of English verse).
+    # A glossary or a list of names has short lines too, so it takes many of them.
     suggest:
       paths: ["(^|/)(poems?|poetry|tanka|haiku)(/|[-_.])"]
+      ja: { line: "^(?=.*[ぁ-ゖ])[ぁ-ゖゝゞァ-ヺー-ヾ一-鿿々〆]{3,20}$", min_lines: 40 }
+      en: { line: "^\\s{0,8}[A-Z][a-z’']*,? [^.#|*\\[\\]()<>:0-9]{6,50}[a-z,;!?’—-]$", min_lines: 80 }
   - id: literature/play
     name: { ja: 戯曲・脚本, en: Play and script }
     summary:
       ja: 戯曲・脚本
       en: Plays and scripts
+    # A speaker's name before the line: 妻　　あたしは… (two ideographic spaces; a statute's 第一条　 has one), ALGERNON.
     suggest:
       paths: ["(^|/)(plays?|screenplays?|kyakuhon)(/|[-_.])"]
+      ja: { line: "^[^\\s○◯●※・]{1,6}　　\\S", min_lines: 20 }
       en: { line: "^[A-Z][A-Z '-]{2,}\\.$", min_lines: 10 }
   - id: speech/address
     name: { ja: スピーチ・挨拶, en: Speech }
@@ -349,6 +405,7 @@ genres:
       no-mixed-desumasu: off
       contraction-consistency: off
       doubled-word: off
+      agreement-slip: off
       sasete-itadaku: off
       double-keigo: off
       cushion-phrase-density: off
@@ -361,3 +418,4 @@ genres:
       undefined-acronym: off
       ai-tell: off
       ai-generated-composite: off
+      assistant-residue: off

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chaffjs",
-  "version": "0.16.0",
+  "version": "0.18.0",
   "description": "Prose validation harness. Finds what is hard to read, and never rewrites it for you.",
   "keywords": [
     "chaff",
@@ -42,8 +42,10 @@
     "dist",
     "genres.yaml",
     "profiles",
+    "reference-headings.yaml",
     "rules",
     "skills",
+    "styles",
     "src"
   ],
   "engines": {
@@ -55,8 +57,8 @@
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.125.0",
-    "@chaffjs/lang-en": "0.14.0",
-    "@chaffjs/lang-ja": "0.15.0",
+    "@chaffjs/lang-en": "0.16.0",
+    "@chaffjs/lang-ja": "0.17.0",
     "mdast-util-from-markdown": "^2.0.3",
     "mdast-util-frontmatter": "^2.0.1",
     "mdast-util-gfm-table": "^2.0.0",

package/reference-headings.yaml

@@ -0,0 +1,17 @@
+# 文献一覧の見出し。言語の見当付け（どの言語パッケージを読むか）は、この見出しの下の一覧を数えない。
+# 文献一覧は本文の言語ではなく、引いた文献の言語で書かれる。日本語の論文の英語の文献が多いと、文書が英語に見える。
+# 見当付けは言語パッケージを読む前に動くので、どちらの言語の見出しもここに置く。大文字と小文字は区別しない。
+headings:
+  - 参考文献
+  - 引用文献
+  - 参照文献
+  - 文献
+  - 文献一覧
+  - 引用・参考文献
+  - 参考・引用文献
+  - References
+  - Reference
+  - Bibliography
+  - Works Cited
+  - Literature Cited
+  - Cited Literature

package/rules/adverb-overuse.yaml

@@ -26,3 +26,22 @@ how_to_fix:
 levels: { strict: 10, normal: 15, relaxed: 25 }
 
 use_for: [blog, business, legal, docs, academic, literature, speech]
+
+group: readability
+summary:
+  ja: 英語で、-ly の副詞が多すぎる所（弱い動詞の印になりやすい）
+  en: Too many -ly adverbs, which usually prop up a weak verb
+example:
+  en:
+    pad: true
+    before: |
+      She quickly walked to the room and quietly opened the door. He really badly needed the report and angrily asked for it.
+    after: |
+      She hurried to the room and eased the door open. He needed the report and demanded it.
+
+not_flagged:
+  ja: 短い文書（200 語より短いもの）は測りません。
+  en: Documents under 200 words are not measured.
+level_meaning:
+  ja: 1000 語あたり {limit} 個まで
+  en: up to {limit} per 1000 words

package/rules/agentless-passive.yaml

@@ -26,3 +26,22 @@ how_to_fix:
 levels: { strict: 1, normal: 1, relaxed: 2 }
 
 use_for: [business, legal, docs, academic, literature, speech]
+
+group: wording
+summary:
+  ja: 「〜が決定されました」のように、受け身で書いて、誰がしたのかが書かれていない所
+  en: A passive sentence ("the budget was approved") that never says who did it
+example:
+  ja:
+    before: 来期の予算が承認されました。
+    after: 取締役会が、来期の予算を承認しました。
+  en:
+    before: The budget for next year was approved.
+    after: The board approved the budget for next year.
+
+not_flagged:
+  ja: 「〜によって」のように、した人が同じ文に書いてある受け身は指しません。法務のジャンルは、受け身が書き方そのものなので見ません。
+  en: A passive that names the actor in the same sentence ("by the board") is not reported. Legal genres, where the passive is the form, do not run this rule.
+level_meaning:
+  ja: 一文に受け身が {limit} 個あれば指摘
+  en: reported when a sentence has {limit} passives with no actor

package/rules/agreement-slip.yaml

@@ -0,0 +1,49 @@
+id: agreement-slip
+layer: L3
+status: experimental
+how_to_find: agreement-slip
+requires: [pos]
+languages: [en]
+extra_word_lists: [singular-determiner, plural-determiner, invariant-noun, count-adjective, dependent-possessive, finite-auxiliary, misnumbered-phrase]
+severity: warning
+
+name:
+  ja: 語の形が合っていない
+  en: Words that do not agree
+
+why:
+  ja: 「a significant changes」「these new version」のように限定詞と名詞の単数・複数が食い違う文や、「Your can check」のように所有の語が主語の位置にある文は、書き換えの途中で片方だけ直した跡です。読み手はつまずき、急いで書いた文書に見えます。解析器の読みが一通りに決まる形だけを数え、単数と複数が同じ綴りの語（series / data）、代名詞にも読める this / these の直後の語、名詞を重ねた語（a sales team）は数えていません。
+  en: A determiner and a noun that differ in number ("a significant changes", "these new version"), or a possessive where the subject belongs ("Your can check"), is left over from an edit that fixed one word and not the other. The reader stumbles, and the document looks rushed. Only forms with one reading are counted; nouns spelled alike in both numbers ("series", "data"), a word right after "this" or "these" (which can stand alone), and nouns that modify another noun ("a sales team") are not.
+
+message:
+  ja: 「{word}」で単数と複数が合っていません
+  en: '"{word}" mixes singular and plural'
+
+messages:
+  number:
+    ja: 「{word}」で単数と複数が合っていません
+    en: '"{word}" mixes singular and plural'
+  possessive:
+    ja: 「{word}」で、所有の語が主語の位置にあります
+    en: '"{word}" puts a possessive where the subject belongs'
+
+how_to_fix:
+  ja: 限定詞か名詞のどちらかに揃えてください（a significant change / significant changes）。所有の語なら、主語の語に直してください（Your can → You can、their is → there is）。
+  en: Make the determiner and the noun agree ("a significant change" or "significant changes"). For a possessive, write the subject you meant ("Your can" becomes "You can", "their is" becomes "there is").
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+
+group: slips
+summary:
+  ja: 英語で、「these new version」のように単数と複数が合っていない所
+  en: Words that no longer agree after an edit, as in "these new version"
+example:
+  en:
+    before: These new version will ship in May.
+    after: This new version will ship in May.
+
+not_flagged:
+  ja: 単数と複数で形が同じ名詞（series、data）、this や these の直後の語、名詞を修飾する名詞（a sales team）は指しません。
+  en: Nouns spelled alike in both numbers ("series", "data"), a word right after "this" or "these", and nouns that modify another noun ("a sales team") are not reported.

package/rules/ai-generated-composite.yaml

@@ -13,6 +13,11 @@ from:
   - padded-intro
   - closing-cliche
   - no-em-dash
+  - contrast-framing
+  - stock-transition
+  - assistant-residue
+  - announcing-opener
+  - colon-lead-in
 
 name:
   ja: 生成文の特徴がそろっている
@@ -34,3 +39,100 @@ how_to_fix:
 levels: { strict: 2, normal: 3, relaxed: 5 }
 
 use_for: [blog, business, legal, docs, academic, literature, speech]
+
+group: ai-tells
+summary:
+  ja: 生成された文章の特徴がいくつも一つの文書にそろっている所（生成だと決めつけはしません）
+  en: Several signals of generated text together in one document (a place to reread, not a verdict)
+example:
+  ja:
+    config: { genre: blog/tech, rules: { ai-generated-composite: strict } }
+    before: |
+      # 在庫管理を見直す
+
+      現代社会において、データは重要な役割を果たすと言えるでしょう。
+
+      - 正確さ
+      - 速さ
+      - 安さ
+
+      毎日することです。
+
+      - 数える
+      - 記録する
+      - 見返す
+
+      よくある失敗です。
+
+      - 数え忘れ
+      - 記録の漏れ
+      - 見返さない
+    after: |
+      # 在庫管理を見直す
+
+      当社では、在庫の数を毎朝データで確かめてから発注しています。
+
+      - 正確さ
+      - 速さ
+
+      毎日することです。
+
+      - 数える
+      - 記録する
+      - 見返す
+      - 月末の棚卸しと突き合わせる
+
+      よくある失敗です。
+
+      - 数え忘れ
+      - 記録の漏れ
+      - 見返さない
+  en:
+    config: { genre: blog/tech, rules: { ai-generated-composite: strict } }
+    before: |
+      # Rethinking stock control
+
+      In today's fast-paced world, data plays a crucial role. Let us delve into why.
+
+      - Accuracy
+      - Speed
+      - Cost
+
+      Every day we:
+
+      - Count
+      - Record
+      - Review
+
+      Common mistakes:
+
+      - Missed counts
+      - Gaps in the record
+      - No review
+    after: |
+      # Rethinking stock control
+
+      We check stock levels every morning before placing orders.
+
+      - Accuracy
+      - Speed
+
+      Every day we:
+
+      - Count
+      - Record
+      - Review
+      - Match against the month-end count
+
+      Common mistakes:
+
+      - Missed counts
+      - Gaps in the record
+      - No review
+
+not_flagged:
+  ja: 特徴が一つだけなら何も言いません。そろっても、生成された文章だとは言いません。読み返す場所の目印です。
+  en: One signal alone says nothing. Even several together do not say the text was generated; they mark a place to reread.
+level_meaning:
+  ja: 特徴が {limit} 種そろえば指摘
+  en: reported once {limit} signals occur together

package/rules/ai-tell.yaml

@@ -26,3 +26,26 @@ how_to_fix:
 levels: { strict: 10, normal: 18, relaxed: 30 }
 
 use_for: [blog, business, legal, docs, academic, literature, speech]
+
+group: ai-tells
+summary:
+  ja: 「重要な役割を果たす」「と言えるでしょう」のような、生成された文章にありがちな言い回しが重なった所
+  en: Phrases common in generated text ("delve into", "plays a crucial role") piling up
+example:
+  ja:
+    before: |
+      現代社会において、データは重要な役割を果たすと言えるでしょう。
+    after: |
+      当社では、在庫の数を毎朝データで確かめてから発注しています。
+  en:
+    before: |
+      In today's fast-paced world, data plays a crucial role. Let us delve into why.
+    after: |
+      We check stock levels every morning before placing orders.
+
+not_flagged:
+  ja: どの言い回しも、一つだけなら普通の文章にあります。重みの合計が上限を超えるまでは何も言いません。これだけで生成された文章だとは言いません。
+  en: Each phrase is ordinary on its own; nothing is said until the weights add up past the limit. This alone never says the text was generated.
+level_meaning:
+  ja: 言い回しの重みの合計が {limit} 点まで
+  en: up to a score of {limit}

package/rules/announced-count-mismatch.yaml

@@ -0,0 +1,57 @@
+id: announced-count-mismatch
+layer: L3
+status: experimental
+how_to_find: announced-count
+severity: warning
+
+name:
+  ja: 予告した数と箇条書きの数が合わない
+  en: A list that does not have the number of items announced
+
+why:
+  ja: 「以下の3点」と書いたのに、すぐ下の箇条書きが2つや4つだと、読み手は抜けた項目があるのか、数え間違いなのかを確かめることになります。項目を足したり消したりしたあとに、予告の数を直し忘れると起きます。箇条書きのすぐ前の文が、「以下の」「次の」のような先を指す語か、終わりのコロン（：）と一緒に数（3点、2つ、4項目）を書いているときだけ、その数を箇条書きのいちばん外側の項目の数と比べます。
+  en: When a sentence says "the following three steps" and the list right below it has two or four, the reader has to check whether an item is missing or the count is wrong. It happens when an item is added or removed and the count is not updated. The number is compared with the items at the top level of the list only when the sentence right before the list announces it, with a word pointing ahead ("following", "below") or a colon at its end, and the number names what the list holds ("three steps", "two reasons").
+
+message:
+  ja: 「{phrase}」と予告していますが、すぐ下の箇条書きは{listed}項目です
+  en: '"{phrase}" is announced, but the number of items in the list below is {listed}'
+
+how_to_fix:
+  ja: 項目が抜けていないか確かめて、足りなければ足し、数が違うなら予告の数を直してください。
+  en: Check whether an item is missing. Add it, or correct the number in the announcement.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: facts
+summary:
+  ja: 「以下の3点」と書いたのに、下の箇条書きの数が違う所
+  en: A list whose number of items differs from the number announced just before it
+example:
+  ja:
+    before: |
+      申し込みの前に、次の3点を確認してください。
+
+      - 本人確認の書類
+      - 振込先の口座
+    after: |
+      申し込みの前に、次の2点を確認してください。
+
+      - 本人確認の書類
+      - 振込先の口座
+  en:
+    before: |
+      Before you apply, check the following three items:
+
+      - Your ID
+      - Your bank account
+    after: |
+      Before you apply, check the following two items:
+
+      - Your ID
+      - Your bank account
+
+not_flagged:
+  ja: 目安の数（約3点、3つ以上）、順番（3つ目）、選ぶ数（以下から1つ選ぶ）、見出しや表の前の数、箇条書きがすぐ後ろに無い数は比べません。予告の文に数が二つあるときも比べません。
+  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.

package/rules/announcing-opener.yaml

@@ -0,0 +1,51 @@
+id: announcing-opener
+layer: L2
+status: experimental
+how_to_find: opener-pile
+word_list: announcing-opener
+uses: [pos]
+severity: info
+
+name:
+  ja: 予告で始まる文が多い
+  en: Too many sentences that announce before they say
+
+why:
+  ja: 「重要なのは、」「ポイントは、」「正直に言うと、」は、中身の前に「これから大事なことを言う」と予告します。1 つなら目印ですが、重なるとどの文も同じ重さに見え、予告だけが残ります。生成文によく見られる癖として知られています。
+  en: '"The key point is", "Here''s the thing" and "Honestly," announce a point before making it. Once, that is a signpost; piled up, every sentence claims the same weight and the announcements are all that stand out. A habit well known in generated text.'
+
+message:
+  ja: 「{matched}」など、予告で始まる文が {count} 個あります（{limit} 個から）
+  en: '"{matched}" and other announcing openers start {count} sentences ({limit} needed)'
+
+how_to_fix:
+  ja: 予告を消して、中身から書き始めてください。本当に一番大事な一つだけなら、予告を残してもかまいません。
+  en: Delete the announcement and start with the point. If it really is the one point that matters most, keep that one.
+
+# 指摘に要る数。長さで割らない：人の記事は長くても 1 つ 2 つで、生成文は短くても重ねる。
+levels: { strict: 2, normal: 3, relaxed: 5 }
+
+use_for: [blog, business, legal, docs, academic, literature, speech]
+
+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'
+example:
+  ja:
+    before: |
+      重要なのは、設定を先に確かめることです。ポイントは、ログを残すことです。正直に言うと、手順書は古くなっています。
+    after: |
+      まず設定を確かめ、そのときのログを残してください。手順書は去年の版のままなので、画面の名前が違います。
+  en:
+    before: |
+      The key point is that settings come first. Here's the thing: logs matter too. Honestly, the manual is out of date.
+    after: |
+      Check the settings first and keep the log of that check. The manual is last year's, so the screen names differ.
+
+not_flagged:
+  ja: 文の途中の「このポイントは」と、指摘に要る数に届かない予告は言いません。「大事なのは」「結論から言うと」は、生成 AI 以前の人の記事にも同じくらいあるので数えません。
+  en: An announcing phrase inside a sentence, and fewer than the level needs, are not reported.
+level_meaning:
+  ja: 予告で始まる文が {limit} 個あれば指摘
+  en: reported once {limit} sentences open with an announcement

package/rules/assistant-residue.yaml

@@ -0,0 +1,52 @@
+id: assistant-residue
+layer: L2
+status: experimental
+how_to_find: assistant-residue
+word_list: assistant-residue
+uses: [pos]
+severity: warning
+
+name:
+  ja: 会話の返事の名残
+  en: Chat-reply residue
+
+why:
+  ja: 「私の知識は」「お役に立てれば幸いです」は、チャットの返事を文書に貼ったときに残る言葉です。知識の期限や AI としての断り書きは 1 つで言い、人も書く礼の言葉は 2 つ重なったときだけ言います。
+  en: '"As of my last knowledge update" and "I hope this helps" are what a chat reply leaves behind when pasted into a document. A knowledge-cutoff or AI disclaimer counts on its own; a courtesy people also write counts only when two come together.'
+
+message:
+  ja: 「{matched}」は会話の返事の言葉です（点 {density}、{limit} から）
+  en: '"{matched}" is chat-reply wording (score {density}, from {limit})'
+
+how_to_fix:
+  ja: 文書の読み手に向けた言葉に書き直すか、消してください。知識の期限を書いた文は、確かめた日付と出典に置き換えてください。
+  en: Rewrite it for the document's reader, or delete it. Replace a knowledge-cutoff line with the date you checked and the source.
+
+# 語彙表の重みの合計を 10 倍した点。名残そのものは重み 1 で 1 つで届き、人も書く礼は 0.5 で 2 つ重なって届く。
+# strict でも礼 1 つでは言わない。1 つなら人の書き方と区別がつかない。
+levels: { strict: 10, normal: 10, relaxed: 20 }
+
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+
+group: ai-tells
+summary:
+  ja: 「私の知識は」「お役に立てれば幸いです」のような、チャットの返事を貼ったときに残る言葉
+  en: What a pasted chat reply leaves behind ("As of my last knowledge update", "I hope this helps")
+example:
+  ja:
+    before: |
+      新しい棟の計画は検討中でした。私の知識は2023年時点のものです。
+    after: |
+      新しい棟の計画は、2026年9月の議会資料では検討中でした。
+  en:
+    before: |
+      As of my last knowledge update, plans for a new wing were under discussion.
+    after: |
+      The council's minutes of September 2026 say plans for a new wing are under discussion.
+
+not_flagged:
+  ja: 人も書く礼の言葉（「お役に立てれば幸いです」）が一つだけなら、何度書いてあっても指しません。同じ文の中の二つの言い回しは一つと数えます。
+  en: A single courtesy people also write ("I hope this helps"), however often it is repeated, is not reported. Two listed phrases in one sentence count as one.
+level_meaning:
+  ja: 重みの合計が {limit} 点で指摘
+  en: reported from a score of {limit}

package/rules/bold-density.yaml

@@ -28,3 +28,34 @@ levels:
   relaxed: 40
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+
+group: readability
+summary:
+  ja: 太字が多すぎて、どこが大事なのか分からなくなった所
+  en: So much bold text that nothing stands out any more
+example:
+  ja:
+    before: |
+      ## 申し込み
+
+      **申し込み**は**今月末**までに、**専用の用紙**で**総務部**へ出してください。用紙は社内の共有フォルダにあり、印刷して手で書いても、画面で入力してから印刷してもかまいません。**上長の印**が要るので、締め切りの三日前までには上長に渡してください。**遅れた場合**は、どんな理由でも**受け付けません**。分からないことがあれば、総務部の窓口に電話で問い合わせてください。受付の時間は平日の午前九時から午後五時までです。書き方の見本も、同じ共有フォルダに置いてあります。
+    after: |
+      ## 申し込み
+
+      申し込みは、専用の用紙で総務部へ出してください。**締め切りは今月末で、遅れた場合はどんな理由でも受け付けません。**用紙は社内の共有フォルダにあり、印刷して手で書いても、画面で入力してから印刷してもかまいません。上長の印が要るので、締め切りの三日前までには上長に渡してください。分からないことがあれば、総務部の窓口に電話で問い合わせてください。受付の時間は平日の午前九時から午後五時までです。書き方の見本も、同じ共有フォルダに置いてあります。
+  en:
+    before: |
+      ## How to apply
+
+      Send the **form** to **HR** by the **end of the month**. The form is in the shared folder. You can print it and fill it in by hand, or type into it on screen and then print it. It needs your **manager's signature**, so give it to your manager at least three days before the deadline. **Late forms** will **not** be **accepted**, whatever the reason. If you have a question, call the HR desk between nine and five on a weekday.
+    after: |
+      ## How to apply
+
+      Send the form to HR. **The deadline is the end of the month, and late forms will not be accepted, whatever the reason.** The form is in the shared folder. You can print it and fill it in by hand, or type into it on screen and then print it. It needs your manager's signature, so give it to your manager at least three days before the deadline. If you have a question, call the HR desk between nine and five on a weekday.
+
+not_flagged:
+  ja: 200 字より短い節は、1 箇所で割合が跳ねるので測りません。
+  en: Sections under 200 characters are not measured, since one bold span would swing the rate.
+level_meaning:
+  ja: 1000 字あたり太字 {limit} 箇所まで
+  en: up to {limit} bold spans per 1000 characters