chaffjs 0.19.0 → 0.21.0

package/rules/elapsed-years-mismatch.yaml

@@ -0,0 +1,82 @@
+id: elapsed-years-mismatch
+layer: L3
+status: stable
+how_to_find: elapsed-years-mismatch
+requires: [dates]
+severity: warning
+
+name:
+  ja: 起点の年から数えた年数が、文書の日付と合わない
+  en: A count of years that does not match its starting year
+
+why:
+  ja: 「2015年創業」と書いた文書の「創業5年」や、「1980年生まれ（30歳）」は、どちらかが古いままです。去年の文書を写して日付だけ直したときによく起きます。文書の日付（日付だけの段落や「更新日：」の段落）の年から起点の年を引き、書いた年数と比べます。誕生日の前後や「10年目」の数え方があるので、一年までの違いは指しません。
+  en: 'A document that says "founded in 2015" and "5 years since its founding", or "born in 1980 (aged 30)", has kept one figure from an older version. It happens when last year''s document is copied and only the date is changed. The starting year is taken from the document''s own date (a paragraph holding only a date, or "Updated:") and compared with the count of years. A difference of one year is not pointed out, because of birthdays and of counting the tenth year as 10.'
+
+message:
+  ja: "{origin}から{reference}年までは{expected}年ですが、「{written}」と書かれています"
+  en: 'From {origin} to {reference} is {expected} years, but the text says "{written}"'
+
+how_to_fix:
+  ja: 年数と起点の年のどちらが正しいかを確かめて、もう一方を直してください。毎年変わる年数は、起点の年だけを書く手もあります。
+  en: Check whether the count or the starting year is right and correct the other. A count that changes every year can be replaced by the starting year alone.
+
+levels: { 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: 「2015年創業」と「創業5年」、「1980年生まれ」と「30歳」のように、文書の日付から計算した年数と合わない所
+  en: A count of years ("10 years since its founding", "aged 30") that does not match its starting year and the document's date
+example:
+  ja:
+    before: |
+      2026年4月1日
+
+      当社は2015年に創業し、今年で創業5年を迎えます。
+    after: |
+      2026年4月1日
+
+      当社は2015年に創業し、今年で創業11年を迎えます。
+  en:
+    before: |
+      April 1, 2026
+
+      Jane Doe (born in 1980, aged 30) leads the team.
+    after: |
+      April 1, 2026
+
+      Jane Doe (born in 1980, aged 46) leads the team.
+
+not_flagged:
+  ja: 文書に日付（日付だけの段落か「更新日：」の段落）が無ければ、比べる年が無いので見ません。一年までの違い、起点の語に直接付いていない年数（「創業後3年で上場」）、生まれた年と年齢が一つの文に一つずつでないものも見ません。
+  en: A document with no date of its own (a paragraph holding only a date, or "Updated:") has no year to count to and is not checked. A difference of one year, a count not attached to the origin word ("listed 3 years after its founding"), and a sentence without exactly one year of birth and one age are left alone.
+rewrite:
+  depth: light
+  ja:
+    direction: 年数と起点の年のどちらが正しいかを書き手に確かめ、もう一方を直してください。毎年変わる年数は「2015年創業」のように起点の年だけにすると、古くなりません。
+    pairs:
+      - before: 2015年に創業し、今年で創業5年を迎えます。
+        after: 2015年に創業し、今年で創業11年を迎えます。
+      - before: 山田（1980年生まれ、30歳）
+        after: 山田（1980年生まれ）
+    keep:
+      - 起点の年
+      - 誰の年齢か、何の年数か
+    avoid:
+      - 年数を推測で計算し直して、確かめないまま書く
+  en:
+    direction: Ask the writer whether the count or the starting year is right and correct the other. A count that changes every year stays right if it is replaced by the starting year ("founded in 2015").
+    pairs:
+      - before: Acme, founded in 2015, marks 5 years since its founding.
+        after: Acme, founded in 2015, marks 11 years since its founding.
+      - before: Jane Doe (born in 1980, aged 30)
+        after: Jane Doe (born in 1980)
+    keep:
+      - the starting year
+      - whose age, or the age of what
+    avoid:
+      - recomputing the count by guess without confirming it

package/rules/email-greeting-closing.yaml

@@ -0,0 +1,122 @@
+id: email-greeting-closing
+layer: L2
+status: stable
+how_to_find: email-frame
+severity: info
+
+name:
+  ja: メールの挨拶か結びが無い
+  en: Email without a greeting or a closing
+
+why:
+  ja: 仕事のメールは、挨拶で始まり結びで終わるのが読み手の期待です。挨拶が無いと用件だけを突きつけられたように読め、結びが無いと途中で切れたように見えます。下書きを貼り付けたときや、前のメールから本文だけを写したときに抜けます。本文の最初の数行に挨拶（お世話になっております、拝啓、Dear）が無いか、最後の数行（名前や連絡先の行を含む）に結び（よろしくお願いいたします、敬具、Best regards）が無いとき指します。語は語彙表から読みます。
+  en: 'A work email is expected to open with a greeting and end with a closing. Without the greeting it reads as a bare demand; without the closing it looks cut off. Both go missing when a draft is pasted in or the body is copied from an earlier email. chaff points out a body whose first lines hold no greeting ("Dear", "Hi", "Hello") or whose last lines, the name and contact lines included, hold no closing ("Best regards", "Sincerely", "Thanks"). The words come from a lexicon.'
+
+message:
+  ja: メールの挨拶か結びがありません
+  en: The email has no greeting or no closing
+
+messages:
+  greeting:
+    ja: 書き出しに挨拶がありません
+    en: The email does not open with a greeting
+  closing:
+    ja: 終わりに結びの言葉がありません
+    en: The email does not end with a closing
+
+how_to_fix:
+  ja: 書き出しに「いつもお世話になっております。」のような挨拶を、終わりに「よろしくお願いいたします。」のような結びを足してください。
+  en: Open with a greeting such as "Dear Ms Lee," and end with a closing such as "Best regards," before your name.
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [business/email, legal, docs, academic, literature, speech]
+off_for:
+  legal: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  docs: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  academic: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  literature: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  speech: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+
+group: structure
+summary:
+  ja: 仕事のメールで、書き出しの挨拶か終わりの結びが無いもの
+  en: A work email that opens without a greeting or ends without a closing
+example:
+  ja:
+    config: { genre: business/email }
+    before: |
+      件名: 打ち合わせの日程
+
+      打ち合わせの日程をお知らせします。10月13日の14時からです。
+
+      よろしくお願いいたします。
+    after: |
+      件名: 打ち合わせの日程
+
+      いつもお世話になっております。打ち合わせの日程をお知らせします。10月13日の14時からです。
+
+      よろしくお願いいたします。
+  en:
+    config: { genre: business/email }
+    before: |
+      Subject: Meeting date
+
+      The meeting is on 13 October at 14:00.
+
+      Best regards,
+      Ichiro
+    after: |
+      Subject: Meeting date
+
+      Dear facilities team,
+
+      The meeting is on 13 October at 14:00.
+
+      Best regards,
+      Ichiro
+not_flagged:
+  ja: 引用した返信（「>」の行）と、ヘッダーと署名（「-- 」の後ろ）は見ません。挨拶と結びの言い方は決めず、語彙表のどれかがあれば足ります。メール・手紙のジャンルでだけ見ます。
+  en: 'Quoted replies (lines starting with ">"), the header and the signature after "-- " are not read. Which greeting or closing is used is not decided; any word in the lexicon will do. Only the email and letter genre runs this rule.'
+rewrite:
+  depth: light
+  ja:
+    direction: 足りないほうだけを足してください。挨拶は本文の最初に一文、結びは名前の前に一文です。相手との関係が分からなければ「お世話になっております」「よろしくお願いいたします」を使います。用件の文は変えません。
+    pairs:
+      - before: 打ち合わせの日程をお知らせします。
+        after: いつもお世話になっております。打ち合わせの日程をお知らせします。
+      - before: |
+          ご都合をお知らせください。
+          佐藤
+        after: |
+          ご都合をお知らせください。
+          よろしくお願いいたします。
+          佐藤
+    keep:
+      - 用件の文
+      - 署名の名前と連絡先
+    avoid:
+      - 本文に無い用件や約束を足す
+      - 挨拶を何文も重ねる
+  en:
+    direction: Add only what is missing. The greeting is one line before the body, the closing one line before the name. If the relationship is unclear, use "Dear [name]," and "Best regards,". Leave the body as it is.
+    pairs:
+      - before: The meeting is on 13 October at 14:00.
+        after: |
+          Dear facilities team,
+
+          The meeting is on 13 October at 14:00.
+      - before: |
+          Let me know which time suits you.
+          Ichiro
+        after: |
+          Let me know which time suits you.
+
+          Best regards,
+          Ichiro
+    keep:
+      - the body's sentences
+      - the name and contact lines
+    avoid:
+      - adding a request or a promise the body does not make
+      - piling up several greetings

package/rules/email-subject-length.yaml

@@ -0,0 +1,112 @@
+id: email-subject-length
+layer: L2
+status: stable
+how_to_find: email-subject
+severity: warning
+
+name:
+  ja: 件名が空か長すぎる
+  en: Subject line empty or too long
+
+why:
+  ja: 受け手は件名を見て、開くか、いつ読むかを決めます。空の件名は用件が分からず、迷惑メールにも見えます。長い件名は一覧で途中から切れ、肝心の語が見えません。「件名：」「Subject:」の行があるメールだけを見て、その値の字数を数えます。返信や転送でメールソフトが足す「Re:」「Fwd:」は数えません。
+  en: 'Recipients decide from the subject whether to open a message and when. An empty subject says nothing and looks like spam; a long one is cut off in the inbox list before its key words. Only an email with a "Subject:" line is checked, and its value is counted in characters. The "Re:" and "Fwd:" a mail program adds are not counted.'
+
+message:
+  ja: 件名が {count} 字あります（{limit} 字まで）
+  en: The subject has {count} characters (up to {limit})
+
+messages:
+  empty:
+    ja: 件名が空です
+    en: The subject line is empty
+
+how_to_fix:
+  ja: 件名には、用件と、日付や案件名のような見分けの語だけを書いてください。説明は本文に移します。
+  en: Put only the request and a distinguishing word (a date, a project) in the subject, and move the explanation into the body.
+
+levels:
+  ja: { strict: 20, normal: 30, relaxed: 40 }
+  en: { strict: 50, normal: 70, relaxed: 90 }
+
+use_for: [business/email, legal, docs, academic, literature, speech]
+off_for:
+  legal: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  docs: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  academic: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  literature: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  speech: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+
+group: structure
+summary:
+  ja: 「件名：」の行がある仕事のメールで、件名が空か、字数の上限を超えるもの
+  en: A work email whose "Subject:" line is empty or longer than the limit
+example:
+  ja:
+    config: { genre: business/email }
+    before: |
+      件名: 来週の火曜日に予定している会議室の予約サービスの導入に向けた打ち合わせの日程について
+
+      いつもお世話になっております。打ち合わせの日程をお知らせします。
+
+      よろしくお願いいたします。
+    after: |
+      件名: 打ち合わせの日程（10月13日）
+
+      いつもお世話になっております。打ち合わせの日程をお知らせします。
+
+      よろしくお願いいたします。
+  en:
+    config: { genre: business/email }
+    before: |
+      Subject: Following up on our conversation last week about the meeting room booking service and a visit
+
+      Dear facilities team,
+
+      I would like to visit your office.
+
+      Best regards,
+      Ichiro
+    after: |
+      Subject: Visit for the room booking service
+
+      Dear facilities team,
+
+      I would like to visit your office.
+
+      Best regards,
+      Ichiro
+not_flagged:
+  ja: 「件名：」の行が無いメールや手紙、引用した返信の中の件名は見ません。メール・手紙のジャンルでだけ見ます。
+  en: 'An email or letter without a "Subject:" line, and subjects inside a quoted reply, are not checked. Only the email and letter genre runs this rule.'
+level_meaning:
+  ja: 件名 {limit} 字まで
+  en: up to {limit} characters in the subject
+rewrite:
+  depth: light
+  ja:
+    direction: 件名を、用件と見分けの語（日付・案件名・期限）だけに縮めてください。経緯や理由は本文に移します。空の件名には、本文の用件を短く書きます。
+    pairs:
+      - before: 来週の火曜日に予定している会議室の予約サービスの導入に向けた打ち合わせの日程について
+        after: 打ち合わせの日程（10月13日）
+      - before: 先日お送りいただいた見積書の内容についての確認とご相談
+        after: 見積書の確認（10月分）
+    keep:
+      - 用件
+      - 日付・案件名・期限
+    avoid:
+      - 本文に無い用件を件名に書く
+      - 「至急」「重要」を足す
+  en:
+    direction: Cut the subject to the request and a distinguishing word (a date, a project, a deadline). Move the background into the body. For an empty subject, state the body's request briefly.
+    pairs:
+      - before: Following up on our conversation last week about the meeting room booking service and a visit
+        after: Visit for the room booking service
+      - before: Some questions about the quote you sent us and a few things we would like to discuss
+        after: Questions on the October quote
+    keep:
+      - the request
+      - dates, project names and deadlines
+    avoid:
+      - stating a request the body does not make
+      - adding "Urgent" or "Important"

package/rules/emoji-density.yaml

@@ -1,6 +1,6 @@
 id: emoji-density
 layer: L1
-status: experimental
+status: stable
 how_to_find: emoji-density
 severity: info
 
@@ -24,6 +24,8 @@ how_to_fix:
 levels: { strict: 3, normal: 8, relaxed: 20 }
 
 use_for: [blog, business, technical, 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."
 sources: [zhang-2024]
 
 group: readability

package/rules/emoji-heading.yaml

@@ -0,0 +1,134 @@
+id: emoji-heading
+layer: L1
+status: stable
+how_to_find: emoji-heading
+requires: [markdown]
+severity: info
+
+name:
+  ja: 絵文字の付いた見出しが続く
+  en: Headings decorated with emoji
+
+why:
+  ja: 「## 🚀 はじめに」「## ✅ まとめ」のように、見出しごとに絵文字を付ける形です。どの見出しにも付くと、絵文字は節の中身を何も伝えず、目次と画面読み上げには意味の無い記号が並びます。生成文によく見られる形です。
+  en: 'A heading with an emoji in it ("## 🚀 Getting started", "## ✅ Summary"), heading after heading. When every heading has one, the emoji says nothing about the section, and the table of contents and a screen reader get a row of meaningless symbols. A shape common in generated text.'
+
+message:
+  ja: 見出し「{heading}」に絵文字があります（絵文字の付いた見出しが {count} 個、{limit} 個から）
+  en: 'Heading "{heading}" has an emoji ({count} {count|heading|headings} with one, {limit} needed)'
+
+how_to_fix:
+  ja: 見出しから絵文字を外し、節の中身が分かる言葉にしてください。一つだけ目印にしたい見出しがあれば、それだけ残してもかまいません。
+  en: Take the emoji out of the headings and let the words say what the section holds. If one heading really needs a marker, keep that one.
+
+# 指摘に要る見出しの数。長さで割らない：見出しの数は文書の長さとは別に決まる。
+levels: { strict: 2, normal: 3, relaxed: 5 }
+
+use_for: [blog, business, legal, docs, academic, literature, speech]
+off_for:
+  legal: "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 (個人情報取扱事業者). This rule would only flag the form."
+  docs: "A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up."
+  academic: "Science writes in the passive, hedges its claims on purpose (may, suggest) and cites numbers as its evidence."
+  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."
+sources: [zhang-2024]
+
+group: ai-tells
+summary:
+  ja: 「## 🚀 はじめに」のように、見出しごとに絵文字が付いている所
+  en: 'Headings with an emoji in them ("## 🚀 Getting started"), one after another'
+example:
+  ja:
+    config: { genre: blog/tech }
+    before: |
+      # 在庫の数え方
+
+      ## 🚀 はじめに
+
+      毎朝、倉庫の在庫を数えています。
+
+      ## 🛠️ 手順
+
+      棚ごとに数え、表に書きます。
+
+      ## ✅ まとめ
+
+      数え終えたら、表を共有します。
+    after: |
+      # 在庫の数え方
+
+      ## はじめに
+
+      毎朝、倉庫の在庫を数えています。
+
+      ## 手順
+
+      棚ごとに数え、表に書きます。
+
+      ## 数えた後
+
+      数え終えたら、表を共有します。
+  en:
+    config: { genre: blog/tech }
+    before: |
+      # Counting stock
+
+      ## 🚀 Getting started
+
+      We count the stock in the warehouse every morning.
+
+      ## 🛠️ Steps
+
+      Count shelf by shelf and write it in the sheet.
+
+      ## ✅ Summary
+
+      When the count is done, share the sheet.
+    after: |
+      # Counting stock
+
+      ## Getting started
+
+      We count the stock in the warehouse every morning.
+
+      ## Steps
+
+      Count shelf by shelf and write it in the sheet.
+
+      ## After the count
+
+      When the count is done, share the sheet.
+
+not_flagged:
+  ja: 指摘に要る数に届かない見出しと、矢印（→）や ™ のように絵文字として描かれない記号は数えません。説明書・法務・論文・文学のジャンルでは見ません。
+  en: Fewer headings than the level needs are not reported, nor symbols not drawn as emoji (→, ™). Documentation, legal, academic and literary genres do not run this rule.
+level_meaning:
+  ja: 絵文字の付いた見出しが {limit} 個あれば指摘
+  en: reported once {limit} headings carry an emoji
+rewrite:
+  depth: light
+  ja:
+    direction: 見出しから絵文字を外し、節の中身が分かる言葉にしてください。絵文字が言っていたこと（注意、完了）が要るなら、本文の最初の文で言います。
+    pairs:
+      - before: "## 🚀 はじめに"
+        after: "## はじめに"
+      - before: "## ⚠️ 注意点"
+        after: "## 注意点"
+    keep:
+      - 見出しの順番と深さ
+      - 見出しへのリンク先の名前
+    avoid:
+      - 絵文字を「【】」や「■」のような別の飾りに置き換える
+      - 見出しを長い文にする
+  en:
+    direction: Take the emoji out of each heading and let the words say what the section holds. If the emoji carried a meaning (a warning, done), say it in the section's first sentence.
+    pairs:
+      - before: "## 🚀 Getting started"
+        after: "## Getting started"
+      - before: "## ⚠️ Gotchas"
+        after: "## Gotchas"
+    keep:
+      - the order and level of the headings
+      - the anchors other pages link to
+    avoid:
+      - trading the emoji for another decoration (■, ★, brackets)
+      - turning a heading into a sentence

package/rules/empty-intensifier.yaml

@@ -28,6 +28,9 @@ levels:
   relaxed: 3
 
 use_for: [blog, business, technical, 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."
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 
 group: wording
 summary:
@@ -48,6 +51,7 @@ level_meaning:
   ja: 当てはまる言い回しが {limit} 箇所あれば指摘
   en: reported once there are {limit}
 rewrite:
+  depth: light
   ja:
     direction: 強める語（「非常に」「言うまでもなく」）を消し、何がどう大事なのかが本文にあれば、それを主語と述語で書いてください。無ければ書き手に聞きます。
     pairs:

package/rules/empty-list-item.yaml

@@ -0,0 +1,86 @@
+id: empty-list-item
+layer: L1
+status: stable
+how_to_find: empty-list-item
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 中身の無い箇条書きの項目
+  en: Empty list item
+
+why:
+  ja: 「担当：」のように見出しの語だけを書いて値の無い項目や、記号だけの項目です。同じ箇条書きのほかの項目には値が書いてあるので、書き忘れか、まだ決まっていないことが読み手には分かりません。
+  en: An item holding only a label ("Owner:") while the other items of the list give theirs a value, or an item with nothing after its bullet. The reader cannot tell a gap from an undecided point.
+
+message:
+  ja: 「{name}」の後に値がありません（同じ箇条書きのほかの項目には書いてあります）
+  en: 'Nothing after "{name}" (the other items in this list give a value)'
+messages:
+  empty:
+    ja: 中身の無い箇条書きの項目です
+    en: This list item is empty
+
+how_to_fix:
+  ja: 値を書いてください。まだ決まっていないなら「未定（いつ決めるか）」と書きます。要らない項目なら消します。
+  en: Write the value. If it is not decided, write "TBD" and when it will be. If the item is not needed, remove it.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 「担当：」のように見出しの語だけで値の無い項目と、記号だけの項目
+  en: A list item holding only a label ("Owner:") where its siblings give values, or an item with nothing in it
+example:
+  ja:
+    before: |
+      - 日時：10月14日 10時
+      - 場所：第2会議室
+      - 担当：
+    after: |
+      - 日時：10月14日 10時
+      - 場所：第2会議室
+      - 担当：山田
+  en:
+    before: |
+      - Date: October 14, 10:00
+      - Room: Meeting Room 2
+      - Owner:
+    after: |
+      - Date: October 14, 10:00
+      - Room: Meeting Room 2
+      - Owner: Yamada
+
+not_flagged:
+  ja: 見出しの語だけの項目は、同じ箇条書きのほかの項目に「見出し：値」の形が一つも無ければ指しません（記入用の書式）。下に入れ子の箇条書きや段落が続く項目（「手順：」の下に手順を並べたもの）も指しません。Markdown の箇条書きでだけ動きます。
+  en: 'A label-only item is not reported when no other item in its list has a "label: value" form (a blank form to fill in). An item followed by a nested list or paragraph (a lead-in) is not reported. Markdown lists only.'
+rewrite:
+  depth: light
+  ja:
+    direction: 空の項目に入るものを本文から探して書いてください。本文に無ければ作らず、「未定」と書いて書き手に聞きます。中身の無い記号だけの項目は消します。
+    pairs:
+      - before: "- 担当："
+        after: "- 担当：山田"
+      - before: "- 期限："
+        after: "- 期限：未定（来週の定例で決める）"
+    keep:
+      - ほかの項目の中身と並び
+      - 見出しの語
+    avoid:
+      - 本文に無い名前や日付を作って埋める
+      - 値の無い項目を黙って消す（決めるべきことが消える）
+  en:
+    direction: Find what belongs after the label in the text and write it. If the text does not say, do not invent it; write "TBD" and ask the writer. Remove an item with nothing in it.
+    pairs:
+      - before: "- Owner:"
+        after: "- Owner: Yamada"
+      - before: "- Due:"
+        after: "- Due: TBD (set at next week's meeting)"
+    keep:
+      - the other items and their order
+      - the label
+    avoid:
+      - inventing a name or date the text does not give
+      - quietly removing a label-only item, which drops a decision still to be made

package/rules/empty-section.yaml

@@ -1,6 +1,6 @@
 id: empty-section
 layer: L1
-status: experimental
+status: stable
 how_to_find: empty-section
 requires: [markdown]
 severity: warning

package/rules/empty-table-cell.yaml

@@ -0,0 +1,90 @@
+id: empty-table-cell
+layer: L1
+status: stable
+how_to_find: empty-table-cell
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 表の空欄
+  en: Blank table cell
+
+why:
+  ja: 表のほかの行がすべて埋めている列で、一つの行だけが空欄です。書き忘れたのか、該当しないのか、まだ決まっていないのかが読み手には分かりません。担当や期限の列なら、その行の仕事は誰もしないまま残ります。
+  en: Every other row fills this column, and one row leaves it blank. The reader cannot tell whether it was forgotten, does not apply, or is not decided yet. In an owner or due-date column, that row's task is left to no one.
+
+message:
+  ja: 表の「{name}」の列で、この行だけが空欄です
+  en: 'The "{name}" column is blank in this row only'
+
+how_to_fix:
+  ja: 中身を書いてください。該当しないなら「なし」「—」、まだ決まっていないなら「未定（いつ決めるか）」と書きます。
+  en: Fill it in. If it does not apply, write "none" or "—"; if it is not decided, write "TBD" and when it will be.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: ほかの行がすべて埋めている列で、一つの行だけが空いている表のセル
+  en: A table cell left blank in a column every other row fills
+example:
+  ja:
+    before: |
+      | 期限 | 担当 | 内容 |
+      | --- | --- | --- |
+      | 10月16日 | 伊藤 | 修正予定を共有する |
+      | 10月21日 |  | 手順書の案を配る |
+      | 10月28日 | 高橋 | 説明会の日程を決める |
+    after: |
+      | 期限 | 担当 | 内容 |
+      | --- | --- | --- |
+      | 10月16日 | 伊藤 | 修正予定を共有する |
+      | 10月21日 | 鈴木 | 手順書の案を配る |
+      | 10月28日 | 高橋 | 説明会の日程を決める |
+  en:
+    before: |
+      | Due | Owner | Task |
+      | --- | --- | --- |
+      | Oct 16 | Ito | Share the fix plan |
+      | Oct 21 |  | Send the draft manual |
+      | Oct 28 | Takahashi | Set the briefing date |
+    after: |
+      | Due | Owner | Task |
+      | --- | --- | --- |
+      | Oct 16 | Ito | Share the fix plan |
+      | Oct 21 | Suzuki | Send the draft manual |
+      | Oct 28 | Takahashi | Set the briefing date |
+
+not_flagged:
+  ja: 一番左の列は見ません（空欄で「上と同じ」を表す書き方があるため）。同じ列に空欄が二つ以上ある列、本文の行が三つより少ない表、「—」「なし」と書いたセルは指しません。Markdown の表でだけ動きます。
+  en: The first column is not checked, since a blank there often means "same as above". A column with two or more blanks, a table with fewer than three body rows, and a cell holding "—" or "none" are not reported. Markdown tables only.
+rewrite:
+  depth: light
+  ja:
+    direction: 空欄に入るものを本文から探して書いてください。本文に無ければ作らず、「未定」と書いて、決める人か時期を書き手に聞きます。
+    pairs:
+      - before: "| 10月21日 |  | 手順書の案を配る |"
+        after: "| 10月21日 | 鈴木 | 手順書の案を配る |"
+      - before: "| 保守 |  | 月額 |"
+        after: "| 保守 | 未定（10月末に決定） | 月額 |"
+    keep:
+      - ほかの行とセルの中身
+      - 表の列の並び
+    avoid:
+      - 本文に無い名前や数を作って埋める
+      - 空欄の行を消す
+  en:
+    direction: Find what belongs in the blank cell in the text and write it. If the text does not say, do not invent it; write "TBD" and ask the writer who decides and when.
+    pairs:
+      - before: "| Oct 21 |  | Send the draft manual |"
+        after: "| Oct 21 | Suzuki | Send the draft manual |"
+      - before: "| Support |  | Monthly |"
+        after: "| Support | TBD (decided by Oct 31) | Monthly |"
+    keep:
+      - the other rows and cells
+      - the order of the columns
+    avoid:
+      - inventing a name or figure the text does not give
+      - deleting the row with the blank