chaffjs 0.15.0 → 0.16.0

package/genres.yaml

@@ -0,0 +1,363 @@
+# The genres chaff knows, in the order `chaff genres` lists them.
+#
+# A genre is a preset: pick the kind of document and chaff checks it the way that kind is written.
+#   rules:   the level a rule runs at for this genre (strict / normal / relaxed / off), under chaff.yaml's rules.
+#            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.
+# 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:
+  - id: technical
+    name: { ja: 技術文書, en: Technical }
+  - id: blog
+    name: { ja: ブログ, en: Blog }
+  - id: business
+    name: { ja: ビジネス文書, en: Business }
+  # Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive
+  # (shall be deemed), and joins long noun compounds (個人情報取扱事業者). Those rules would only flag the form.
+  - id: legal
+    name: { ja: 法務, en: Legal }
+    rules:
+      agentless-passive: off
+      max-kanji-continuous: off
+      no-doubled-joshi: off
+      ngram-repetition: off
+      repeated-sentence-head: off
+      heading-echo: off
+      taigen-dome-in-prose: off
+      unqualified-superlative: off
+      excessive-hedging: off
+      proper-noun-density: off
+      expletive-construction: off
+      adverb-overuse: off
+      concrete-evidence-density: off
+      closing-cliche: off
+      padded-intro: off
+      preamble-length: off
+      cushion-phrase-density: off
+      sasete-itadaku: off
+      sentence-rhythm: off
+      rule-of-three: off
+      section-length-uniformity: off
+      paragraph-length-variance: off
+      ai-tell: off
+      ai-generated-composite: 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 }
+    rules:
+      heading-echo: off
+      agentless-passive: off
+      concrete-evidence-density: off
+      preamble-length: off
+      proper-noun-density: off
+      unqualified-superlative: off
+      expletive-construction: off
+      adverb-overuse: off
+      cushion-phrase-density: off
+      double-keigo: off
+      sasete-itadaku: off
+      sentence-initial-conjunction-run: off
+      closing-cliche: off
+      padded-intro: off
+      sentence-rhythm: off
+      rule-of-three: off
+      section-length-uniformity: off
+      paragraph-length-variance: off
+      ai-tell: off
+      ai-generated-composite: 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 }
+    rules:
+      agentless-passive: off
+      excessive-hedging: off
+      expletive-construction: off
+      concrete-evidence-density: off
+      proper-noun-density: off
+      adverb-overuse: off
+      closing-cliche: off
+      padded-intro: off
+      preamble-length: off
+      cushion-phrase-density: off
+      sasete-itadaku: off
+      double-keigo: off
+      sentence-rhythm: off
+      rule-of-three: off
+      section-length-uniformity: off
+      paragraph-length-variance: 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
+    name: { ja: 文学, en: Literature }
+    rules:
+      max-sentence-length: off
+      max-paragraph-length: off
+      ngram-repetition: off
+      repeated-sentence-head: off
+      heading-echo: off
+      empty-intensifier: off
+      no-doubled-joshi: off
+      no-nakaguro-parallel: off
+      taigen-dome-in-prose: off
+      max-kanji-continuous: off
+      hiragana-fukushi: off
+      no-mixed-desumasu: off
+      contraction-consistency: off
+      doubled-word: off
+      agentless-passive: off
+      expletive-construction: off
+      excessive-hedging: off
+      unqualified-superlative: off
+      adverb-overuse: off
+      sentence-initial-conjunction-run: off
+      repeated-conjunction: off
+      undefined-acronym: off
+      proper-noun-density: off
+      concrete-evidence-density: off
+      closing-cliche: off
+      padded-intro: off
+      preamble-length: off
+      cushion-phrase-density: off
+      sasete-itadaku: off
+      double-keigo: off
+      no-em-dash: off
+      emoji-density: off
+      sentence-rhythm: off
+      rule-of-three: off
+      section-length-uniformity: off
+      paragraph-length-variance: off
+      ai-tell: off
+      ai-generated-composite: off
+      dangling-reference: off
+      duplicate-definition: off
+      date-order: off
+      date-weekday-mismatch: off
+      total-mismatch: off
+  # A speech opens with greetings and closes with thanks: that is its form, not padding.
+  - id: speech
+    name: { ja: 話し言葉, en: Speech }
+    rules:
+      agentless-passive: off
+      preamble-length: off
+      padded-intro: off
+      closing-cliche: off
+      concrete-evidence-density: off
+      proper-noun-density: off
+      sentence-rhythm: off
+      rule-of-three: off
+      section-length-uniformity: off
+      paragraph-length-variance: off
+
+genres:
+  - id: technical/spec
+    name: { ja: 仕様書, en: Specification }
+    summary:
+      ja: 仕様書・RFC・設計文書。読み手に間違えさせないための文書
+      en: Specifications, RFCs and design documents, written so the reader cannot get it wrong
+  - id: technical/readme
+    name: { ja: README・技術文書, en: README and technical docs }
+    summary:
+      ja: README と開発者向けの説明
+      en: READMEs and documentation for developers
+  - id: blog/tech
+    name: { ja: 技術ブログ, en: Tech blog }
+    summary:
+      ja: 技術記事。ジャンルを決めないときはこれで見ます
+      en: Technical articles; the genre used when none is set
+  - id: blog/essay
+    name: { ja: エッセイ（ブログ）, en: Blog essay }
+    summary:
+      ja: 自分の考えを書くブログのエッセイ
+      en: Personal essays posted on a blog
+  - id: blog/owned-media
+    name: { ja: オウンドメディア, en: Owned media }
+    summary:
+      ja: 会社や団体が読者に向けて出す記事
+      en: Articles an organisation publishes for its readers
+  - id: business/proposal
+    name: { ja: 提案書・企画書, en: Proposal }
+    summary:
+      ja: 提案書・企画書・計画書
+      en: Proposals, plans and pitches
+  - id: business/report
+    name: { ja: 報告書, en: Report }
+    summary:
+      ja: 報告書・白書・社内文書
+      en: Reports, white papers and internal documents
+  - id: business/email
+    name: { ja: メール・手紙, en: Email and letter }
+    summary:
+      ja: 仕事のメールと手紙
+      en: Work email and letters
+  - id: business/press-release
+    name: { ja: プレスリリース・お知らせ, en: Press release and notice }
+    summary:
+      ja: プレスリリースと、お知らせ
+      en: Press releases and public notices
+  - id: business/meeting-notes
+    name: { ja: 議事録, en: Meeting notes }
+    summary:
+      ja: 議事録・議事要旨
+      en: Minutes and meeting notes
+  - id: legal/contract
+    name: { ja: 契約書・規約, en: Contract and terms }
+    summary:
+      ja: 契約書・利用規約・プライバシーポリシー
+      en: Contracts, terms of service and privacy policies
+    suggest:
+      paths: ["(^|/)(contracts?|agreements?|terms|tos|nda|keiyaku|kiyaku)(/|[-_.])", "(^|/)privacy[-_]?policy[-_.]"]
+      ja: { line: "本契約|本規約|本ポリシー|以下「(?:甲|乙|丙)」|^#{1,6}\\s*(?:プライバシーポリシー|個人情報保護方針|利用規約|契約書)", min_lines: 2 }
+      en:
+        {
+          line: "\\b(?:[Tt]his Agreement|[Tt]hese Terms|[Tt]his (?:Privacy )?Policy|the Parties)\\b|^#{1,6}\\s*(?:Terms of (?:Service|Use)|Privacy Policy)\\b",
+          min_lines: 3,
+        }
+    # A contract is read clause by clause against its own numbers, definitions and dates: these are its mistakes.
+    rules:
+      numbering-gap: normal
+      duplicate-definition: normal
+      dangling-reference: normal
+      date-weekday-mismatch: normal
+      total-mismatch: normal
+  - id: legal/statute
+    name: { ja: 法令・規程, en: Statute and regulation }
+    summary:
+      ja: 法令・規則・社内規程・通達
+      en: Statutes, regulations and internal rules
+    profile: statute
+    # Also suggested when the content has the statute profile's shape.
+    suggest:
+      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 }
+  - id: legal/judgment
+    name: { ja: 判決, en: Court decision }
+    summary:
+      ja: 判決文・決定
+      en: Court judgments and opinions
+    suggest:
+      ja: { line: "^(?:#{1,6}\\s*)?(?:主\\s*文|理\\s*由|判\\s*決)\\s*$", min_lines: 2 }
+      en: { line: "delivered the opinion of the Court|^(?:Reversed|Affirmed)\\.?$", min_lines: 1 }
+  - id: legal/patent
+    name: { ja: 特許明細書, en: Patent }
+    summary:
+      ja: 特許の明細書と請求項
+      en: Patent specifications and claims
+    suggest:
+      ja: { line: "【(?:課題|解決手段|請求項[0-9０-９]+|選択図|技術分野|背景技術|発明の詳細な説明|特許請求の範囲)】", min_lines: 2 }
+      en: { line: "^#{1,6}\\s*(?:BACKGROUND OF THE INVENTION|SUMMARY OF THE INVENTION|Claims\\b)|\\bof claim \\d+", min_lines: 3 }
+  - id: docs/manual
+    name: { ja: マニュアル・手順書, en: Manual and how-to }
+    summary:
+      ja: 使い方の説明・手順書・ヘルプ
+      en: User guides, how-to pages and help
+    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:
+      ja: 問いと答えを並べたページ
+      en: Pages of questions and answers
+    suggest:
+      paths: ["(^|[/_-])(faqs?|q-?and-?a)([/_.-]|$)"]
+      ja: { line: "^(?:#{1,6}\\s*)?(?:[QＱ][0-9０-９]*[.．:：、\\s　]|問[0-9０-９]+[.．:：\\s　])|^#{1,6}\\s*(?:よくある(?:ご)?質問|Ｑ＆Ａ|Q&A)", min_lines: 2 }
+      en: { line: "^(?:#{1,6}\\s*)?Q[0-9]*[.:)]\\s|^#{1,6}\\s*(?:FAQs?|Frequently asked questions)\\b", min_lines: 2 }
+  - id: docs/glossary
+    name: { ja: 用語集, en: Glossary }
+    summary:
+      ja: 用語と、その説明を並べたページ
+      en: Lists of terms and what they mean
+    suggest:
+      paths: ["(^|/)(glossary|glossaries|yogo|用語集)(/|[-_.])"]
+      ja: { line: "^#{1,6}\\s*用語集", min_lines: 1 }
+      en: { line: "^#{1,6}\\s*Glossary\\b", min_lines: 1 }
+  - id: academic/paper
+    name: { ja: 論文, en: Academic paper }
+    summary:
+      ja: 論文と、その要旨
+      en: Papers and abstracts
+    suggest:
+      paths: ["(^|/)(papers?|ronbun)(/|[-_.])"]
+      ja: { line: "^(?:#{1,6}\\s*)?(?:要旨|抄録|参考文献|引用文献|謝辞)\\s*(?:[（(].*)?$", min_lines: 2 }
+      en:
+        {
+          line: "^(?:#{1,6}\\s*)?(?:\\d+\\.?\\s+)?(?:Abstract|Keywords|Methods?|Methodology|Results|Discussion|Conclusions?|Related [Ww]ork|Bibliography|References)\\s*$",
+          min_lines: 4,
+        }
+  - id: literature/fiction
+    name: { ja: 小説, en: Fiction }
+    summary:
+      ja: 小説・物語
+      en: Novels and stories
+    suggest:
+      paths: ["(^|/)(novels?|fiction|stories|shosetsu)(/|[-_.])"]
+  - id: literature/essay
+    name: { ja: 随筆, en: Literary essay }
+    summary:
+      ja: 文学としての随筆。ブログのエッセイは blog/essay
+      en: Literary essays; a blog essay is blog/essay
+  - id: literature/poetry
+    name: { ja: 詩歌, en: Poetry }
+    summary:
+      ja: 詩・短歌・俳句
+      en: Poems and verse
+    suggest:
+      paths: ["(^|/)(poems?|poetry|tanka|haiku)(/|[-_.])"]
+  - id: literature/play
+    name: { ja: 戯曲・脚本, en: Play and script }
+    summary:
+      ja: 戯曲・脚本
+      en: Plays and scripts
+    suggest:
+      paths: ["(^|/)(plays?|screenplays?|kyakuhon)(/|[-_.])"]
+      en: { line: "^[A-Z][A-Z '-]{2,}\\.$", min_lines: 10 }
+  - id: speech/address
+    name: { ja: スピーチ・挨拶, en: Speech }
+    summary:
+      ja: 読み上げるために書いた演説・挨拶
+      en: Speeches and addresses written to be read aloud
+    suggest:
+      paths: ["(^|/)(speech(es)?|addresses)(/|[-_.])"]
+      ja: { line: "^(?:議長|御列席の皆様|ご列席の皆様|皆様|皆さん)、|ご清聴(?:いただき)?ありがとうございました", min_lines: 2 }
+      en: { line: "^(?:Mr\\.|Madam) (?:President|Speaker|Chair(?:man)?),|^Ladies and gentlemen,|Thank you for (?:your attention|listening)", min_lines: 2 }
+  - id: speech/transcript
+    name: { ja: 発言録, en: Transcript }
+    summary:
+      ja: 話したことを書き起こした記録（会見・国会の会議録）
+      en: Verbatim records of what was said (press conferences, parliamentary debates)
+    suggest:
+      paths: ["(^|/)(transcripts?|kaigiroku)(/|[-_.])"]
+      ja: { line: "^○[^　\\s]{1,30}　|^（(?:問|答)）|^【(?:記者|大臣|質問|回答)】", min_lines: 3 }
+      en: { line: "^(?:Mr|Ms|Mrs|Dr)\\. [A-Z][A-Z-]{2,}(?: of [A-Z][a-z]+)?\\. ", min_lines: 3 }
+    # A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix.
+    rules:
+      max-sentence-length: off
+      max-paragraph-length: off
+      ngram-repetition: off
+      repeated-sentence-head: off
+      heading-echo: off
+      empty-intensifier: off
+      no-doubled-joshi: off
+      no-nakaguro-parallel: off
+      taigen-dome-in-prose: off
+      max-kanji-continuous: off
+      hiragana-fukushi: off
+      no-mixed-desumasu: off
+      contraction-consistency: off
+      doubled-word: off
+      sasete-itadaku: off
+      double-keigo: off
+      cushion-phrase-density: off
+      excessive-hedging: off
+      unqualified-superlative: off
+      expletive-construction: off
+      adverb-overuse: off
+      sentence-initial-conjunction-run: off
+      repeated-conjunction: off
+      undefined-acronym: off
+      ai-tell: off
+      ai-generated-composite: off

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chaffjs",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Prose validation harness. Finds what is hard to read, and never rewrites it for you.",
   "keywords": [
     "chaff",
@@ -40,6 +40,7 @@
     "README.md",
     "bin",
     "dist",
+    "genres.yaml",
     "profiles",
     "rules",
     "skills",
@@ -54,8 +55,8 @@
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.125.0",
-    "@chaffjs/lang-en": "0.13.0",
-    "@chaffjs/lang-ja": "0.14.0",
+    "@chaffjs/lang-en": "0.14.0",
+    "@chaffjs/lang-ja": "0.15.0",
     "mdast-util-from-markdown": "^2.0.3",
     "mdast-util-frontmatter": "^2.0.1",
     "mdast-util-gfm-table": "^2.0.0",

package/rules/adverb-overuse.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: 1000 語あたり {density} 個の -ly 副詞があります（{limit} 個まで）
-  en: "{density} -ly adverbs per 1000 words (limit {limit})"
+  en: "{density} -ly {density|adverb|adverbs} per 1000 words (limit {limit})"
 
 how_to_fix:
   ja: 副詞ごと動詞に畳んでください。"said loudly" を "shouted" に。
@@ -25,4 +25,4 @@ how_to_fix:
 # 1000 語あたりの個数。件数で数えると長い文書ほど当たる（bold-density と同じ）。
 levels: { strict: 10, normal: 15, relaxed: 25 }
 
-use_for: [blog, business]
+use_for: [blog, business, legal, docs, academic, literature, speech]

package/rules/agentless-passive.yaml

@@ -25,4 +25,4 @@ how_to_fix:
 # 1 文に受け身がいくつまで許されるか。1 は「1 つでも指摘する」。
 levels: { strict: 1, normal: 1, relaxed: 2 }
 
-use_for: [business]
+use_for: [business, legal, docs, academic, literature, speech]

package/rules/ai-generated-composite.yaml

@@ -24,7 +24,7 @@ why:
 
 message:
   ja: 「{word}」が同じ文書にそろっています（{count} 種、{limit} 種から）
-  en: '"{word}" occur together in this document ({count} signals, {limit} needed)'
+  en: '"{word}" {count|occurs|occur together} in this document ({count} {count|signal|signals}, {limit} needed)'
 
 how_to_fix:
   ja: 自分が書きたかったことが残っているか、通して読み直してください。個々の指摘を 1 つずつ直すより、段落ごと書き直すほうが早いことがあります。
@@ -33,4 +33,4 @@ how_to_fix:
 # 何種そろったら出すか。spec §20.2 は 3。
 levels: { strict: 2, normal: 3, relaxed: 5 }
 
-use_for: [blog, business]
+use_for: [blog, business, legal, docs, academic, literature, speech]

package/rules/ai-tell.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: 「{word}」が揃っています（点 {density}、{limit} まで）
-  en: '"{word}" appear together (score {density}, limit {limit})'
+  en: '"{word}" {count|appears|appear together} (score {density}, limit {limit})'
 
 how_to_fix:
   ja: 自分の言葉に置き換えてください。置き換えられないなら、その段落は無くても通るかもしれません。
@@ -25,4 +25,4 @@ how_to_fix:
 # 重みの合計を 10 倍した点。0.9 の言い回しが 2 つで 18。
 levels: { strict: 10, normal: 18, relaxed: 30 }
 
-use_for: [blog, business]
+use_for: [blog, business, legal, docs, academic, literature, speech]

package/rules/bold-density.yaml

@@ -14,7 +14,7 @@ why:
 
 message:
   ja: このセクションは {chars} 字に太字が {bolds} 箇所あります（1000 字あたり {limit} 箇所まで）
-  en: "{bolds} bold spans in {chars} characters (limit {limit} per 1000)"
+  en: "{bolds} bold {bolds|span|spans} in {chars} {chars|character|characters} (limit {limit} per 1000)"
 
 how_to_fix:
   ja: 本当に強調したい 1〜2 箇所だけ残して、ほかは普通の文にしてください。
@@ -27,4 +27,4 @@ levels:
   normal: 20
   relaxed: 40
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/closing-cliche.yaml

@@ -28,4 +28,4 @@ levels:
   normal: 1
   relaxed: 2
 
-use_for: [blog]
+use_for: [blog, legal, docs, academic, literature, speech]

package/rules/concrete-evidence-density.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: 「{word}」の節に数値もコードもリンクもありません（そういう節が {count}/{total}）
-  en: 'Section "{word}" has no number, code or link ({count} of {total} sections)'
+  en: 'Section "{word}" has no number, code or link ({count} of {total} {total|section|sections})'
 
 how_to_fix:
   ja: 実例を 1 つ足してください。書けないなら、その節は他の節に畳めるかもしれません。
@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
-use_for: [blog, business]
+use_for: [blog, business, legal, docs, academic, literature, speech]

package/rules/contraction-consistency.yaml

@@ -25,4 +25,4 @@ how_to_fix:
 # 少数派が何種までなら「混在」と見るか。これを超えたら混在ではなく、そういう文体。
 levels: { strict: 4, normal: 2, relaxed: 1 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/cushion-phrase-density.yaml

@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 2, normal: 5, relaxed: 10 }
 
-use_for: [business]
+use_for: [business, legal, docs, academic, literature, speech]

package/rules/dangling-reference.yaml

@@ -24,4 +24,4 @@ how_to_fix:
 # 何件あれば指摘するか。1 は「1 件でもあれば」。
 levels: { strict: 1, normal: 1, relaxed: 1 }
 
-use_for: [business, technical, blog]
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]

package/rules/date-order.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 1 }
 
-use_for: [business, technical, blog]
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]

package/rules/date-weekday-mismatch.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 1 }
 
-use_for: [business, technical, blog]
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]

package/rules/double-keigo.yaml

@@ -25,4 +25,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 2 }
 
-use_for: [business]
+use_for: [business, legal, docs, academic, literature, speech]

package/rules/doubled-word.yaml

@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 1 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/duplicate-definition.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 1 }
 
-use_for: [business, technical, blog]
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]

package/rules/emoji-density.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 # 1000 語あたりの個数。件数で数えると長い文書ほど当たる。
 levels: { strict: 3, normal: 8, relaxed: 20 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/empty-conclusion.yaml

@@ -34,4 +34,5 @@ levels:
   normal: warning
   relaxed: info
 
-use_for: [blog]
+# メール・議事録・プレスリリースの結びは挨拶か連絡先で、判断を書く所ではない。
+use_for: [blog, business/report, business/proposal]

package/rules/empty-intensifier.yaml

@@ -27,4 +27,4 @@ levels:
   normal: 1
   relaxed: 3
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/excessive-hedging.yaml

@@ -1,8 +1,11 @@
 id: excessive-hedging
 layer: L2
 status: experimental
-how_to_find: hedging-density
+how_to_find: hedging
 word_list: excessive-hedging
+# 1 つの文の重なりを数えるときの、それだけでは逃げていない包む言い方（「という状況です」、may）と、
+# 逃げの表現のうちどこで成り立つかを言うもの（「場合がある」、in some cases）。
+extra_word_lists: [hedge-frame, hedge-scope]
 uses: [pos]
 severity: warning
 
@@ -11,17 +14,24 @@ name:
   en: Too much hedging
 
 why:
-  ja: 断言を避けるほど、読み手は何が決まったのか分からなくなります。1 つなら慎重さですが、重なると誰も責任を取らない文書になります。
-  en: The more the text avoids claiming, the less the reader can tell what was decided. One hedge is caution; many mean nobody is accountable.
+  ja: 断言を避けるほど、読み手は何が決まったのか分からなくなります。1 つなら慎重さですが、重なると誰も責任を取らない文書になります。chaff は 2 つの見方で探します。1 つの文に逃げを重ねたもの（「〜という状況であると考えられます」「〜かもしれないと思われます」）は、短い文書でも 1 文で指摘します。文書全体で逃げの表現が多すぎるものは、短い文書では測りません。重なりを数えるとき、鉤括弧や引用符で引いた発言の中の逃げは、話した人のものなので数えません。
+  en: The more the text avoids claiming, the less the reader can tell what was decided. One hedge is caution; many mean nobody is accountable. chaff looks two ways. A sentence that stacks hedges ("may possibly", "it could perhaps be argued") is reported on its own, even in a short document. Too many hedges across the whole document is measured only on longer documents. When counting hedges stacked in a sentence, a hedge inside a quotation is the speaker's, not the writer's, and is left out.
 
 message:
   ja: 「{matched}」など、逃げの表現が 1000 語あたり {density} 個あります（{limit} 個まで）
   en: '"{matched}" and other hedges: {density} per 1000 words (limit {limit})'
 
+# 1 つの文に重ねたもの。上の message は文書全体の密度。
+messages:
+  stacked:
+    ja: この文は逃げの表現を {count} つ重ねています（「{matched}」）
+    en: 'This sentence stacks {count} hedges ("{matched}")'
+
 how_to_fix:
-  ja: 言い切れるものは言い切ってください。言い切れないなら、何が分かれば言い切れるのかを書いてください。
-  en: Commit where you can. Where you cannot, say what you would need to know.
+  ja: 言い切れるものは言い切ってください。言い切れないなら、何が分かれば言い切れるのかを書いてください。重ねた逃げは、1 つ残すか、全部外して言い切ってください。
+  en: Commit where you can. Where you cannot, say what you would need to know. Where hedges are stacked, keep one or drop them all and commit.
 
+# 文書全体の、1000 語あたりの数の上限。1 つの文に 2 つ以上重ねたものは、どの段でも指摘する。
 levels: { strict: 3, normal: 6, relaxed: 12 }
 
-use_for: [business, blog, technical]
+use_for: [business, blog, technical, legal, docs, academic, literature, speech]

package/rules/expletive-construction.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: '"{word} is ..." の形が文書内に {count} 回あります（{limit} 回まで）'
-  en: '"{word} is ..." appears {count} times (limit {limit})'
+  en: '"{word} is ..." appears {count} {count|time|times} (limit {limit})'
 
 how_to_fix:
   ja: 主語を前に出してください。"There is a need to review" を "The board must review" に。
@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
-use_for: [blog, business]
+use_for: [blog, business, legal, docs, academic, literature, speech]

package/rules/heading-echo.yaml

@@ -27,4 +27,4 @@ levels:
   normal: 60
   relaxed: 75
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/hiragana-fukushi.yaml

@@ -25,4 +25,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 3 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/internal-jargon.yaml

@@ -15,7 +15,7 @@ why:
 
 message:
   ja: 「{matched}」は社内でしか通じないかもしれません（そういう語が {count} 箇所）
-  en: '"{matched}" may only be understood inside your team ({count} such words)'
+  en: '"{matched}" may only be understood inside your team ({count} such {count|word|words})'
 
 how_to_fix:
   ja: 初出のところで普通の言葉に言い換えるか、括弧で説明を添えてください。jargon には辞書形（握る）でも語幹（巻き取）でも書けますが、複合動詞は語幹のほうが確実です。
@@ -24,4 +24,4 @@ how_to_fix:
 # チームが並べた語なので、1 つでも指摘する。並べた時点で「使わない」と決めている。
 levels: { strict: 1, normal: 1, relaxed: 3 }
 
-use_for: [business, blog, technical]
+use_for: [business, blog, technical, legal, docs, academic, literature, speech]