chaffjs 0.30.0 → 0.32.0

package/rules/date-stamp-order.yaml

@@ -0,0 +1,82 @@
+id: date-stamp-order
+layer: L3
+status: stable
+how_to_find: date-stamp-order
+word_list: stamp-order-label
+# The stamp words (制定, 最終改定, Established, Last updated) and whether each dates the first version or a change come from the
+# language's stamp-order-label lexicon.
+requires: [dates]
+languages: [ja, en]
+severity: error
+
+name:
+  ja: 制定日が改定日より後
+  en: An established date after the last update
+
+why:
+  ja: 規約やポリシーの末尾の「2023年4月1日 制定」「2026年9月1日 最終改定」は、この文書がいつ定められ、いつ直されたかを示します。定めた日が直した日より後だと、まだ無い文書を直したことになり、読み手はどちらの日付が正しいのか、今の版がいつのものなのかが分かりません。前の版の日付を書き換えるときに、片方だけ直し損ねると起きます。日付と制定・改定の語だけの行を読み、制定の日付が改定の日付より後なら、両方の行を指します。どちらが違っているかは分からないので、両方を確かめてもらいます。
+  en: 'The "Established: April 1, 2023" and "Last updated: September 1, 2026" lines of a policy or terms say when the document was first set and when it was last changed. An established date after an update means the document was changed before it existed, and the reader cannot tell which date is right or how old the current version is. It happens when the dates of the previous version are rewritten and one is missed. Lines holding only a date and an established or updated word are read, and when the established date is later than an update both lines are reported: nothing tells which of the two is wrong.'
+
+message:
+  ja: 制定の日付（{established}）が、改定の日付（{updated}）より後です
+  en: "The established date {established} is after the update {updated}"
+
+messages:
+  updated:
+    ja: 改定の日付（{updated}）が、制定の日付（{established}）より前です
+    en: "The update {updated} is before the established date {established}"
+
+how_to_fix:
+  ja: 制定と改定のどちらの日付が正しいかを確かめて、もう一方を直してください。
+  en: Check which is right, the established date or the update, and correct the other.
+
+levels: { strict: error, normal: error, relaxed: warning }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: A story's dates belong to the story, and a document quoted in it may be dated as the author likes.
+  speech: A transcript writes what was said, dates misspoken and corrected included.
+
+group: facts
+summary:
+  ja: 規約やポリシーの末尾で、制定の日付が改定の日付より後になっている所
+  en: An established date later than the last update at the foot of a policy or terms
+example:
+  ja:
+    before: |
+      # 利用規約
+
+      本規約は、日本法に準拠します。
+
+      2027年4月1日 制定
+
+      2026年7月1日 最終改定
+    after: |
+      # 利用規約
+
+      本規約は、日本法に準拠します。
+
+      2023年4月1日 制定
+
+      2026年7月1日 最終改定
+  en:
+    before: |
+      # Terms of Use
+
+      These Terms are governed by the laws of Japan.
+
+      Established: April 1, 2027
+
+      Last updated: July 1, 2026
+    after: |
+      # Terms of Use
+
+      These Terms are governed by the laws of Japan.
+
+      Established: April 1, 2023
+
+      Last updated: July 1, 2026
+
+not_flagged:
+  ja: 日付と制定・改定の語のほかに何かが書かれた行（「2020年12月21日に重点計画を策定」）と年の無い日付は読みません。一行に日付が二つあるときは、全角空白や縦棒で区切った一つひとつ（「作成：平成16年2月4日　最終改定：令和3年11月19日」）を読みます。制定か改定のどちらかの行が無ければ何も言いません。7行以上離れた刻印は、一つのファイルにまとめた別の文書の刻印と見て比べません。施行日は比べません。改定を先に決めて後から施行するのはふつうのことで、施行日は改定日より後になりえます。
+  en: A line with anything besides the date and the stamp word (We adopted the policy on April 1, 2023) and a date without its year are not read. A line with two dates is read part by part, split at tabs and bars. Without both an established and an updated line nothing is said. Stamps seven lines or more apart are taken as the stamps of two documents in one file and are not compared. An effective date is not compared. A policy is often updated ahead of the day it takes effect, so an effective date after the update is normal.

package/rules/date-without-year.yaml

@@ -12,12 +12,12 @@ name:
   en: Date without a year
 
 why:
-  ja: 文書のほかの日付には年があるのに、一つだけ年が無い日付は、読み手がどの年かを推し量ることになります。年をまたぐ日付が並ぶ文書（12月と1月）では、年の無い日付がどちらの年か決まりません。
-  en: When the document's other dates carry a year, a date without one leaves the reader to guess it. When the dates cross the turn of a year (December and January), a yearless date could be either year.
+  ja: 文書の日付が二つ以上の年にわたるとき（2025年の日付と2026年の日付）、年の無い日付はどの年のことか読み手には決まりません。年をまたぐ日付が並ぶ文書（12月と1月）でも、年の無い日付がどちらの年か決まりません。日付がみな同じ年なら、年が無くても読み手には分かります。
+  en: When the document's dates span more than one year (some in 2025, some in 2026), a date without a year leaves the reader unable to tell which year it means. The same holds where the dates cross the turn of a year (December and January). When every dated date is in one year, the reader can tell the year without it.
 
 message:
-  ja: 「{date}」には年がありません（この文書のほかの日付 {count} 個には年があります）
-  en: '"{date}" has no year (the document''s other {count} dates do)'
+  ja: 「{date}」には年がありません。この文書の日付は {from}年から{to}年にわたるので、どの年か決まりません
+  en: '"{date}" has no year, and the document''s dates run from {from} to {to}, so the year is unclear'
 messages:
   boundary:
     ja: 「{date}」には年がありません。年の変わり目をまたぐ日付が並んでいるので、どちらの年か決まりません
@@ -33,39 +33,39 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
 group: structure
 summary:
-  ja: ほかの日付には年があるのに年の無い日付と、年の変わり目をまたいで並ぶ年の無い日付
-  en: A date without a year where the document's other dates carry one, or where the dates cross the turn of a year
+  ja: 文書の日付が二つ以上の年にわたるときや年の変わり目をまたぐときの、年の無い日付
+  en: A date with no year where the document's dates span years or cross a new year
 example:
   ja:
     before: |
       # 日程
 
+      - 2025年10月15日（水）：前回の説明会
       - 2026年10月14日（水）：説明会
-      - 2026年10月21日（水）：申込の締め切り
       - 10月28日（水）：結果の連絡
     after: |
       # 日程
 
+      - 2025年10月15日（水）：前回の説明会
       - 2026年10月14日（水）：説明会
-      - 2026年10月21日（水）：申込の締め切り
       - 2026年10月28日（水）：結果の連絡
   en:
     before: |
       # Schedule
 
+      - October 15, 2025: last year's briefing
       - October 14, 2026: briefing
-      - October 21, 2026: applications close
       - October 28: results sent
     after: |
       # Schedule
 
+      - October 15, 2025: last year's briefing
       - October 14, 2026: briefing
-      - October 21, 2026: applications close
       - October 28, 2026: results sent
 
 not_flagged:
-  ja: 年を一度だけ書いて、あとの日付は月と日だけで書く文書（年の無い日付のほうが多い文書）は、書き方の選び方として指しません。ただしその場合も、年をまたぐ日付は指します。月だけ・年だけの日付は見ません。
-  en: A document that writes the year once and the rest as month and day (more yearless dates than dated ones) is a style, and not reported, except for a date across the turn of a year. Month-only and year-only dates are not checked.
+  ja: 年のある日付がみな同じ年の文書では、年の無い日付を指しません（どの年か読み手に分かるため）。年を一度だけ書いて、あとの日付は月と日だけで書く文書（年の無い日付のほうが多い文書）も、書き方の選び方として指しません。ただしどちらの場合も、年をまたぐ日付は指します。どの年のものでもない日付も指しません。毎年の日（毎年4月1日、年末年始閉庁日（12月29日～1月3日）、4月1日から翌年3月31日まで）と、例の日付（例えば…4月1日に届いた場合、例：のあとの日付）です。年のある日付が一つも無い文書、月だけ・年だけの日付は見ません。
+  en: A document whose dated dates are all in one year is not reported, since the reader can tell the year. A document that writes the year once and the rest as month and day (more yearless dates than dated ones) is a style, and not reported either. In both, a date across the turn of a year is still reported. Nor is a date of no one year, such as a day that comes round every year ("every year on April 1", "each December 31", "April 1 to March 31 of the following year") and a date in a worked example ("for example, a request received on April 1", the dates after "e.g."). A document with no dated date, and month-only and year-only dates, are not checked.
 rewrite:
   depth: light
   ja:

package/rules/deadline-after-event.yaml

@@ -0,0 +1,72 @@
+id: deadline-after-event
+layer: L3
+status: stable
+how_to_find: event-deadline
+# The event-date words come from the language's event-date-label lexicon, the registration and deadline words from
+# event-registration-word and event-deadline-word, and what may come after an event from event-aside.
+requires: [dates]
+languages: [ja, en]
+severity: error
+
+name:
+  ja: 申込締切が催しの日より後
+  en: A registration deadline after the event
+
+why:
+  ja: 案内状の「申込締切」や「出欠のご返信は…までに」が催しの当日より後だと、締め切りに間に合わせて申し込んでも、そのときには催しが終わっています。前の回の案内を使い回して、催しの日か締め切りの片方だけを直したときに起きます。「日時」「開催日」で始まり時刻のある行の日付を催しの日と読み、申込の語と締め切りの語のある文の日付がそれより後なら指します。修学旅行のような旅行の知らせでは、「出発日」「期間」の行の始まりの日を時刻が無くても出発の日と読み、それより後の代金の「納入期限」も指します。
+  en: When the registration deadline or the RSVP date of an invitation is after the event itself, a reader who signs up in time arrives after it is over. It happens when last year's invitation is reused and only one of the dates is changed. The date on a line starting with an event-date word (Date, When) and holding a time of day is read as the event's date, and a date in a sentence with a registration word and a deadline word (register by, Booking deadline) after it is pointed out. In a trip notice, the first day on a Departure or Dates line is read as the departure even without a time, and a payment deadline after it (Payment due, a Due by column) is pointed out too.
+
+message:
+  ja: 申込の締め切り（{deadline}）が、催しの日（{event}）より後です
+  en: "The registration deadline {deadline} is after the event on {event}"
+
+messages:
+  payment:
+    ja: 支払の期限（{deadline}）が、催しの日（{event}）より後です
+    en: "The payment deadline {deadline} is after the event on {event}"
+
+how_to_fix:
+  ja: 催しの日と締め切りのどちらが正しいかを確かめて、片方を直してください。
+  en: Check which is right, the event date or the deadline, and correct the other.
+
+levels: { normal: error, relaxed: warning }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  legal: "An invitation or an announcement sets an event and a registration deadline; in other genres a date is something reported on, not this document's own."
+  docs: "An invitation or an announcement sets an event and a registration deadline; in other genres a date is something reported on, not this document's own."
+  academic: "An invitation or an announcement sets an event and a registration deadline; in other genres a date is something reported on, not this document's own."
+  literature: "An invitation or an announcement sets an event and a registration deadline; in other genres a date is something reported on, not this document's own."
+  speech: "An invitation or an announcement sets an event and a registration deadline; in other genres a date is something reported on, not this document's own."
+
+group: facts
+summary:
+  ja: 案内状やお知らせで、申込や出欠の返信の締め切りが催しの日より後の所
+  en: A sign-up or RSVP deadline that falls after the event itself
+example:
+  ja:
+    before: |
+      日時：2026年11月20日（金）14:00〜17:00
+
+      申込締切：2026年11月27日（金）
+    after: |
+      日時：2026年11月20日（金）14:00〜17:00
+
+      申込締切：2026年11月13日（金）
+  en:
+    before: |
+      # Invitation
+
+      Date: Friday, November 20, 2026, 2:00 PM
+
+      Please register by Friday, November 27, 2026.
+    after: |
+      # Invitation
+
+      Date: Friday, November 20, 2026, 2:00 PM
+
+      Please register by Friday, November 13, 2026.
+
+not_flagged:
+  ja: 時刻の無い「日時」の行、年の無い日付、日付が二つある文は比べません。催しの日の行が複数あれば、いちばん後の催しの日と比べます。申込の語（申込、出欠、予約）と締め切りの語（まで、締切、期限）の両方がある文だけを読むので、アンケートの回答期限や資料の公開日は比べず、申込の語があってもアンケート、支払、資料などの語が同じ文にあれば比べません。支払の期限は、題名にチケットの語（チケット、入場券）があり請求の語の無いチケットの注文でだけ締め切りと読みます。請求書の支払は催しの後でよいからです。旅行の代金の期限は、題名に旅行の語（修学旅行、林間学校）があり請求の語の無い知らせでだけ読み、出発の日と比べます。請求の「期間」や納品の日とは比べません。法令・規約、手引き、論文、文学、スピーチのジャンルでは止めています。
+  en: A Date line without a time of day, a date without its year, and a sentence with two dates are not compared. With several event-date lines, the latest event is used. Only a sentence with both a registration word (register, RSVP, booking) and a deadline word (by, deadline, closes) is read, so a survey deadline or the date the slides go up is not compared, and a sentence that also names a survey, a payment or the slides is left alone. A payment deadline is read only in a ticket order, whose title names a ticket and which never mentions an invoice, since an invoice is paid after the event. A trip's payment deadline is read only in a notice whose title names a trip (trip, camp) and which never mentions an invoice, and is compared with the departure; a billing period or a delivery date is never the event. It is off in the legal, docs, academic, literature and speech genres.

package/rules/deductible-exceeds-limit.yaml

@@ -0,0 +1,54 @@
+id: deductible-exceeds-limit
+layer: L3
+status: stable
+how_to_find: deductible-exceeds-limit
+requires: [quantities]
+# The deductible words are deductible-word, the limit words benefit-limit-word, the bases (1回, a claim, 1品, a single
+# item) and how they nest deductible-basis; rough amounts come from approximate-marker, ranges from range-connector, money
+# from currency-notation and amount-multiplier.
+severity: warning
+
+name:
+  ja: 免責金額が支払限度額より大きい
+  en: A deductible larger than the most paid
+
+why:
+  ja: 「免責金額は1回5,000円、1回あたりの支払限度額は3,000円」と書くと、読み手には一度も支払われない補償に見えます。免責金額か限度額の片方だけを直したとき、別の補償の数を写したときに起きます。一つの文に免責金額の語（免責金額、自己負担額）と支払限度額の語（支払限度額、限度額）が一つずつあり、それぞれのすぐ後ろに金額がちょうど一つあるとき、同じ補償の額として比べます。通貨と桁の語（万円）をそろえて比べ、何あたりの額か（1回、1事故、1品、1日）も読みます。同じ基準どうし、限度額に基準が無いとき（補償全体の上限）、1事故の免責金額と1品の限度額は比べます。1品だけの請求でも免責金額を丸ごと引かれ、払われるのは1品の限度額までだからです。基準を書いていない免責金額は1事故あたりと読みます。1日と1回のように入れ子にならない基準どうしは比べません。¥と円のように同じ通貨の別の書き方は同じ通貨として比べます。どの語がどの基準かは、言語パッケージの語彙表 deductible-basis にあります。
+  en: 'When a summary says "The excess is $80 a visit, and the most we pay for a visit is $50", the benefit reads as one that never pays. It happens when the excess or the limit is changed and the other is not, or when a figure is copied from another benefit. One sentence holding one deductible word (excess, deductible) and one limit word (the most we pay, maximum, limit, up to), each with exactly one amount of money right after it, is read as one benefit and the two amounts are compared, in the same currency and scale. What each amount is stated for is read too (a visit, a claim, a single item, a day). The same basis is compared, and so is a limit with no basis (the most paid for the whole benefit). An excess per claim is compared with a limit per item: a claim for one item meets the whole excess and is paid at most one item''s limit. An excess with no basis is read as one per claim. Bases that do not nest, such as a day and a claim, are not compared. One currency written two ways ($ and US$) is one currency. Which words name which basis is in the language package''s lexicon deductible-basis.'
+
+message:
+  ja: 「{deductibleWord}」の{deductible}が「{limitWord}」の{limit}より大きく、この補償は支払われないことになります
+  en: "The {deductibleWord} of {deductible} is more than the most paid, {limit}: this benefit would never pay out"
+
+how_to_fix:
+  ja: 免責金額と支払限度額のどちらが正しいかを確かめて、もう一方を直してください。
+  en: Check which of the deductible and the limit is right and correct the other.
+
+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: 「免責金額5,000円、限度額3,000円」のように、免責金額が支払う上限を超える所
+  en: A deductible or excess larger than the most paid for the same benefit
+example:
+  ja:
+    before: |
+      通院給付金の免責金額は1回5,000円、1回あたりの支払限度額は3,000円です。
+    after: |
+      通院給付金の免責金額は1回1,000円、1回あたりの支払限度額は3,000円です。
+  en:
+    before: |
+      The outpatient excess is $80 a visit, and the most we pay for a visit is $50.
+    after: |
+      The outpatient excess is $20 a visit, and the most we pay for a visit is $50.
+
+not_flagged:
+  ja: 免責金額と限度額が別の文にある所、表の中、文に免責金額か限度額の語が二つ以上ある所、語のすぐ後ろに金額が無いか二つある所、範囲（1,000〜5,000円）や目安（約5,000円、5,000円程度）の金額、通貨の違う金額、入れ子にならない基準どうし（1日と1回、1年と1回）、二つの基準を書いた所は比べません。免責金額と限度額が同じ額のときも指しません。
+  en: 'A deductible and a limit in different sentences, tables, a sentence with two deductible or two limit words, a word with no amount or two amounts right after it, a range ("$50 - $80") or a rough amount ("about $80"), amounts in different currencies, bases that do not nest (a day and a claim, a year and a claim), and an amount with two bases written around it are left alone. A deductible equal to the limit is not reported.'
+level_meaning:
+  ja: 一つの文の免責金額が、同じ基準の支払限度額より大きいとき指摘
+  en: reported when a deductible in a sentence is larger than the limit on a comparable basis

package/rules/defined-name-repeated.yaml

@@ -10,8 +10,8 @@ name:
   en: A long name used again after its short name was defined
 
 why:
-  ja: 「株式会社みなと製作所（以下「甲」という。）」と定めたら、そのあとは「甲」と書くのが決まりです。途中で「株式会社みなと製作所」と書き戻すと、読み手は甲と同じ会社なのか、別の立場の同じ会社なのかを確かめることになります。文の途中で括弧に入れて短い呼び名を定めた所の、括弧のすぐ前の名前（名詞と固有名詞の並び）を正式の名前とし、定義より後でその名前が出てくる所を指します。署名欄のように、呼び名と並べて書いた行や名前だけの行は見ません。
-  en: 'Once a contract says "Harbour Works Ltd (the "Supplier")", it refers to the Supplier as "the Supplier". Writing "Harbour Works Ltd" again later makes the reader check whether it is the same party in the same role. chaff takes the name right before an inline definition''s bracket (a run of nouns and names) as the long name, and points at each later use of it. Lines that give the short name too, or little more than the name (a signature block), are not read.'
+  ja: 「株式会社みなと製作所（以下「甲」という。）」と定めたら、そのあとは「甲」と書くのが決まりです。途中で「株式会社みなと製作所」と書き戻すと、読み手は甲と同じ会社なのか、別の立場の同じ会社なのかを確かめることになります。文の途中で括弧に入れて短い呼び名を定めた所の、括弧のすぐ前の名前（名詞と固有名詞の並び）を正式の名前とし、定義より後でその名前が出てくる所を指します。署名欄のように、呼び名と並べて書いた行や名前だけの行、「宛先：株式会社みなと製作所 総務部」のように名前を値に書いた項目の行、札がなくても文書の終わりの段落の頭に名前と部署だけを書いた署名の行（「株式会社みなと製作所 総務部」）は見ません。札が連絡先の語（窓口、お問い合わせ先、連絡先、担当）で終わる項目は、値が長くても、名前が値の途中にあっても、名前のあとが文として続かなければ見ません。
+  en: 'Once a contract says "Harbour Works Ltd (the "Supplier")", it refers to the Supplier as "the Supplier". Writing "Harbour Works Ltd" again later makes the reader check whether it is the same party in the same role. chaff takes the name right before an inline definition''s bracket (a run of nouns and names) as the long name, and points at each later use of it. Lines that give the short name too, little more than the name (a signature block), a field whose value is the name (Attention: Harbour Works Ltd, Legal Department), or a signature at the end with no label, the name and the parts of an address (Harbour Works Ltd, Customer Support) are not read. A field whose label is a contact label (Contact:, Attention:) is not read however long its value or wherever the name sits in it, unless the name goes on as a sentence.'
 
 message:
   ja: 「{name}」は {line} 行目で「{term}」と呼ぶと定めた名前です
@@ -33,7 +33,7 @@ off_for:
 group: consistency
 summary:
   ja: 「株式会社みなと製作所（以下「甲」という。）」のあとで、甲を正式の名前のまま書いている所
-  en: A party or a thing given a short name ("the Supplier") and later written out in full again
+  en: A party given a short name ("the Supplier") and later written out in full
 example:
   ja:
     config: { genre: legal/contract }

package/rules/defined-term-form.yaml

@@ -46,8 +46,8 @@ off_for:
 
 group: consistency
 summary:
-  ja: 契約・規約・規程で、定義した語を定義のあとでかぎ括弧に入れ直したり、大文字で定義した語を小文字で書いたり、「本業務」を「本件業務」と書いたり、「管理責任者」を「文書管理責任者」と長くしたりしている所
-  en: A defined term quoted again after its definition, a capitalised defined term written in lower case, a Japanese term with its other prefix (本件業務 for 本業務), or a term made longer with a word of its definition (Application for App)
+  ja: 契約や規程で、定義した語を、定義のあとで違う形（括弧付き、言い換え、長くした形）で書いた所
+  en: "A defined term later written in another form: quoted, lower case, or lengthened"
 example:
   ja:
     config: { genre: legal/contract }

package/rules/delivered-over-ordered.yaml

@@ -0,0 +1,57 @@
+id: delivered-over-ordered
+layer: L3
+status: stable
+how_to_find: delivered-over-ordered
+# The ordered and delivered columns are found by the language's order-quantity-column lexicon.
+extra_word_lists: [order-quantity-column]
+severity: warning
+
+name:
+  ja: 納品数量が発注数量より多い
+  en: A delivered quantity larger than the ordered quantity
+
+why:
+  ja: 納品書の分納の欄や発注残の一覧では、同じ行の納品数量は発注数量を超えないはずです。読み手はこの表で、何が届き何が残っているかを確かめます。発注数量を写し間違えたとき、別の品目の行と取り違えたとき、納品数量だけを直したときに、納品数量が発注数量を上回ります。どの列が発注数量で、どの列が納品数量かは、列の見出しの語（発注数量、注文数、納品数量、出荷数、Ordered、Delivered、Shipped）だけで決めます。列の並びでは決めません。比べるのは、どちらの升も同じ単位の書いた整数（40冊、300 folders）である行だけです。
+  en: "In the backorder section of a delivery note or a list of open orders, the delivered quantity of a row should not exceed the ordered quantity of the same row. Readers use the table to see what arrived and what is still to come. The delivered quantity exceeds the ordered one when the ordered quantity is copied wrong, when a row is mixed up with another item, or when only the delivered quantity is corrected. Which column is ordered and which is delivered is decided by the heading words alone (Ordered, Qty ordered, Delivered, Shipped), never by where a column stands. Only rows where both cells are written whole numbers in the same unit (40 reams, 300 folders) are compared."
+
+message:
+  ja: 納品数量「{delivered}」が、同じ行の発注数量「{ordered}」より多くなっています
+  en: 'The delivered quantity "{delivered}" is larger than the ordered quantity "{ordered}" on the same row'
+
+how_to_fix:
+  ja: 発注数量と納品数量のどちらが正しいかを確かめて、もう一方を直してください。多く納めたのが本当なら、そのことを表の外に書いてください。
+  en: Check which of the ordered and delivered quantities is right and correct the other. If more really was delivered, say so outside the table.
+
+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 row of an order table that delivers more than was ordered
+example:
+  ja:
+    before: |
+      | 品名 | 発注数量 | 納品数量 | 残数 |
+      | --- | --- | --- | --- |
+      | クリアファイル | 250枚 | 300枚 | 0枚 |
+    after: |
+      | 品名 | 発注数量 | 納品数量 | 残数 |
+      | --- | --- | --- | --- |
+      | クリアファイル | 300枚 | 300枚 | 0枚 |
+  en:
+    before: |
+      | Item | Ordered | Delivered | Backordered |
+      | --- | --- | --- | --- |
+      | Clear folders | 250 folders | 300 folders | 0 folders |
+    after: |
+      | Item | Ordered | Delivered | Backordered |
+      | --- | --- | --- | --- |
+      | Clear folders | 300 folders | 300 folders | 0 folders |
+
+not_flagged:
+  ja: 発注数量の列か納品数量の列が無い表、どちらかの列が二つ以上ある表（前回と今回の納品数量）は比べません。発注と納品の両方を言う見出しの列がある表も比べません。升が空、「-」、「未定」、小数、符号やかっこ付き、「以上」「程度」の付いた行、二つの升の単位が違う行も比べません。納品数量が発注数量と同じか少ない行は言いません。
+  en: "A table with no ordered or no delivered column, or with two of either (delivered previously and now), 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 two cells are in different units, is skipped. A delivered quantity equal to or less than the ordered one is not reported."

package/rules/demonstrative-opener-run.yaml

@@ -30,7 +30,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: readability
 summary:
   ja: 「これは」「その」「この」のような指示語で始まる文が、同じ段落の中で続く所
-  en: Sentences in a row, within one paragraph, that open with a word pointing back (This, That, It; これ, その)
+  en: Sentences in a row that open with a word pointing back (This, That, It)
 example:
   ja:
     before: |

package/rules/discount-rate-mismatch.yaml

@@ -0,0 +1,66 @@
+id: discount-rate-mismatch
+layer: L3
+status: stable
+how_to_find: discount-rate
+# The discount, price and list-price words, the words that make a rate no discount, and the unit marks come from the
+# language's discount-rate-label lexicon; the amounts in a sentence are currency-notation's.
+extra_word_lists: [discount-rate-label, currency-notation]
+severity: warning
+
+name:
+  ja: 割引率が定価と単価から出る率と合わない
+  en: A discount that the list price and the tier price do not give
+
+why:
+  ja: 数量別の価格表で、定価が1枚8.0円、1,000枚以上の単価が7.2円なら、割引率は10%です。表の割引率がこれと合わないと、読む人は単価と割引率のどちらが正しいかを確かめられません。単価を直して割引率を直し忘れたとき、別の段の率を写したときに起きます。見出しが割引率と単価を言う列の、同じ行の二つの升を、定価と比べます。定価は、表の定価の列、表の外の文（定価は1枚8.0円です）、または「| 定価 | 8.0円 |」の行から読み、文書に一つだけのときに使います。割引率＝1−単価÷定価で、書いた率の桁で丸めて比べます。
+  en: 'On a volume price list, with a list price of $0.080 per envelope and a tier price of $0.072, the discount is 10%. When the discount column says something else, the reader cannot tell whether the price or the discount is right. It happens when a price is corrected and its discount is not, or when another tier''s rate is copied. The two cells of one row, in the columns whose headings name the discount and the price, are compared with the list price: a list-price column of the table, else the one list price the document states, in a sentence ("The list price is $0.080 per envelope") or a row (| List price | $0.080 |). The discount is 1 − tier price ÷ list price, rounded to the digits the rate is written to.'
+
+message:
+  ja: 割引率「{written}」が、定価「{list}」と単価「{price}」から出る率（{expected}）と合いません
+  en: "The discount {written} is not what the list price {list} and the price {price} give ({expected})"
+
+how_to_fix:
+  ja: 定価と単価を確かめて、割引率を計算し直してください。
+  en: Check the list price and the tier price, and work the discount out again.
+
+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 discount on a price list that the list price and the tier price do not give
+example:
+  ja:
+    before: |
+      定価は1枚8.0円です。
+
+      | ご注文数 | 1枚の単価 | 割引率 |
+      | --- | --- | --- |
+      | 1,000枚以上 | 7.2円 | 15% |
+    after: |
+      定価は1枚8.0円です。
+
+      | ご注文数 | 1枚の単価 | 割引率 |
+      | --- | --- | --- |
+      | 1,000枚以上 | 7.2円 | 10% |
+  en:
+    before: |
+      The list price is $0.080 per envelope.
+
+      | Order quantity | Price per envelope | Discount |
+      | --- | --- | --- |
+      | 1,000 or more | $0.072 | 15% |
+    after: |
+      The list price is $0.080 per envelope.
+
+      | Order quantity | Price per envelope | Discount |
+      | --- | --- | --- |
+      | 1,000 or more | $0.072 | 10% |
+
+not_flagged:
+  ja: 書いた率の桁での切り捨て・四捨五入・切り上げは合っていると読み、単価の桁で丸めて合うものも合っていると読みます。定価が文書に無いもの、違う定価が二つ以上あるもの、定価と単価の単位が違うもの（円とドル、1箱と1枚）、単価が定価と同じか高いもの（請求書の割引前の単価）は比べません。見出しに税率・掛け率・上乗せなどの語がある列は割引率と読みません。割引率の列や単価の列が二つ以上ある表は読みません。
+  en: "Rounding down, to the nearest or up, to the digits the rate is written to, is read as right, and so is a tier price that the rate gives once rounded to the price's digits. Nothing is compared with no list price in the document, with two different list prices, with the list price and the tier price in different units ($ and €, per box and per envelope), or with a price not below the list price (an invoice's price before its discount). A column whose heading names tax, markup or margin is not read as a discount. A table with two discount or two price columns is not read."

package/rules/due-before-issue.yaml

@@ -3,7 +3,23 @@ layer: L3
 status: stable
 how_to_find: due-date
 # The issue-date and due-date words come from the language's issue-date-label and due-date-label lexicons; the words of
-# minutes from minutes-title-word, meeting-date-label, action-section-heading, earlier-section-word, action-due-label and item-done-word.
+# minutes from minutes-title-word, meeting-date-label, action-section-heading, earlier-section-word, action-due-label and item-done-word;
+# the other pairs of dates that must come in order (a listing date and a move-in date, a posting date and an application
+# deadline, an earnings call and the reporting period, an examination and its report, a purchase and its registration
+# deadline, a recall notice and its request deadline, a loan contract and its first payment, check-in and check-out, a
+# rental's pick-up and drop-off, a booking's cancellation deadline and its start, a payslip's pay date and its pay period,
+# a trip's departure and return, an order and its delivery, a transcript's enrolment, graduation and issue dates, a tax
+# statement's issue date and the end of its tax year or the leaving date, a shipment and its arrival, a medical visit
+# and its bill's issue date, a hospital admission and discharge, a tenancy's move-in, notice and move-out, a car's
+# service date and its next inspection, a construction start and its completion or handover, a service's or a contract's start and end dates, a price list's or a policy's validity start and end, a statement's period
+# start and end, a financial year and its audit, a property sale's contract and its settlement or handover, a banquet
+# quote's validity and its event date) from
+# dated-pair-label and date-now-word,
+# the column headers of a table whose rows each hold both dates of a pair (a points statement's earning date and
+# expiry) from dated-pair-label and the header-only dated-column-label,
+# and the words whose line states
+# a period, compared by its end, from dated-span-label.
+# An insurance claim's date and the incident it claims for are a pair in dated-pair-label too.
 requires: [dates]
 languages: [ja, en]
 severity: error
@@ -13,17 +29,23 @@ name:
   en: A due date before the issue date
 
 why:
-  ja: 請求書の「お支払期限」や見積書の「有効期限」が「発行日」より前だと、受け取った時点で期限が過ぎていることになり、読み手はどちらの日付が正しいのかを問い合わせることになります。前の月の請求書を使い回して、片方の日付だけ直したときに起きます。発行日の語で始まる行と期限の語で始まる行の日付を比べ、期限が発行日より前なら指します。議事録の宿題も同じで、会議の日（日時）より前の期限は、会議の時点で過ぎています。宿題の節の、期限の列の日付や「（期限 11月2日）」を、頭の方の「日時」の日付と比べます。
-  en: When the payment due date of an invoice or the expiry of a quote is before its issue date, the document is overdue on arrival and the reader has to ask which date is right. It happens when last month's invoice is reused and only one date is changed. The date on a line starting with an issue word (Issued, Invoice date) is compared with the date on a line starting with a due word (Payment due, Valid until), and an earlier due date is pointed out. Minutes are read the same way. An action item due before the meeting it was set in is overdue when it is written down. The dates in the due column, or after "due" in a list item, of an action-items section are compared with the date on the "Date" line near the top.
+  ja: 請求書の「お支払期限」や見積書の「有効期限」が「発行日」より前だと、受け取った時点で期限が過ぎていることになり、読み手はどちらの日付が正しいのかを問い合わせることになります。前の月の請求書を使い回して、片方の日付だけ直したときに起きます。発行日の語で始まる行と期限の語で始まる行の日付を比べ、期限が発行日より前なら指します。議事録の宿題も同じで、会議の日（日時）より前の期限は、会議の時点で過ぎています。宿題の節の、期限の列の日付や「（期限 11月2日）」を、頭の方の「日時」の日付と比べます。物件の案内の「入居可能日」も同じで、「掲載日」や「情報公開日」より前の入居可能日は、載せた時点で過ぎています。求人の「応募締切」も同じで、「掲載日」や「募集開始日」より前の締切は、載せた時点で過ぎています。決算短信の「決算説明会」も同じで、「対象期間」が終わる前の説明会では、まだ締まっていない期間の業績を説明することになります。対象期間のように期間を書く行は、その終わりの日と比べます。健診や検査の結果も同じで、「受診日」や「採血日」より前の「報告日」では、受ける前の結果を報告することになります。保証書の「登録の締切」も同じで、「お買い上げ日」より前の締切は、買った時点で過ぎています。宿泊やレンタカーの予約も同じで、「チェックイン」より前の「チェックアウト」、「貸出」より前の「返却」は、泊まる前に発ち、借りる前に返すことになります。「無料キャンセル期限」がチェックインや貸出より後なら、泊まり始めてからでも無料で取り消せることになり、どちらかの日付が違っています。二つの日付は、後に書いた方の行で指します。前後の決まった日付の組は、言語の語彙表に組ごとに書いてあります。ローンや分割払いの「初回お支払日」も同じで、「ご契約日」より前の初回は、契約した時点で過ぎています。製品の回収のお知らせも同じで、「お知らせ日」より前の交換や返金の「受付期限」は、知らせた時点で過ぎています。給与明細の「支給日」も同じで、「支給対象期間」や「計算期間」が終わる前の支給日では、まだ働き終えていない期間の給与を払うことになります。出張の精算書の「帰着」も同じで、「出発」より前の帰着では、発つ前に帰ったことになります。発注書や納品書の「納期」や「納品日」も同じで、「発注日」や「注文日」より前の納期では、頼む前に届いたことになります。成績証明書や卒業・修了の証明書も同じで、「入学年月日」より前の「卒業年月日」や「修了年月日」では入学する前に卒業したことになり、卒業や修了の日より前の「発行日」や「証明日」では、まだ卒業していない人の卒業を証明することになります。給与所得と源泉徴収税額の年間の明細書も同じで、「対象期間」が終わる前や「退職日」より前の「交付日」では、まだ締まっていない年の金額を証明することになります。梱包明細書やインボイスも同じで、「船積日」より前の「到着日」や「到着予定日」では、積む前に着くことになります。診療明細書や領収書も同じで、「診療日」より前の「発行日」では、まだ受けていない診療の代金を受け取ったことになります。入院の明細も同じで、「入院日」より前の「退院日」では、入院する前に退院したことになります。賃貸借の敷金精算書も同じで、「入居日」より前の「退去日」では入居する前に退去したことになり、「退去日」より後の「解約通知日」では、退去してから解約を知らせたことになります。車の整備記録も同じで、「整備日」や「点検日」より前の「次回点検日」や「次回車検」では、次の点検の日が整備した時点で過ぎています。工事やリフォームの見積書も同じで、「着工日」より前の「完工予定日」や「引渡日」では、始める前に工事が終わったことになります。携帯電話やサービスの契約の利用期間も同じで、「ご利用開始日」や「契約開始日」より前の「ご利用終了日」や「契約終了日」では、始まる前に終わったことになります。価格表やクーポンも同じで、「適用開始日」や「発効日」より前の「適用終了日」や「有効期限」では、始まる前に終わることになります。取引明細の期間を二つの行に分けて書いたときも同じで、「照会開始日」や「期間開始日」より前の「照会終了日」や「期間終了日」では、期間が始まる前に終わることになります。保険金や給付金の請求書も同じで、「事故日」や「発病日」より前の「請求日」では、起きる前の事故や病気の保険金を請求することになります。会計報告書や収支決算報告書も同じで、「会計年度」が終わる前の「監査日」では、まだ締まっていない年度の会計を監査したことになります。ポイントの明細のように、一つの表の見出しに組の二つの列（「ご利用日」と「有効期限」）があれば、行ごとに二つの日付を比べます。ご利用日より前の有効期限では、得た時点でポイントが失効しています。別の行や別の表の日付とは比べません。不動産の売買の精算書も同じで、「売買契約日」より前の「決済日」や「引渡日」では、契約する前に代金を払い物件を渡したことになります。宴会や会議室の見積書は向きが逆で、「有効期限」が「開催日」より後なら、催しが終わってから見積を受けられることになります。
+  en: When the payment due date of an invoice or the expiry of a quote is before its issue date, the document is overdue on arrival and the reader has to ask which date is right. It happens when last month's invoice is reused and only one date is changed. The date on a line starting with an issue word (Issued, Invoice date) is compared with the date on a line starting with a due word (Payment due, Valid until), and an earlier due date is pointed out. Minutes are read the same way. An action item due before the meeting it was set in is overdue when it is written down. The dates in the due column, or after "due" in a list item, of an action-items section are compared with the date on the "Date" line near the top. A property listing is read the same way. An "Available from" date before the "Listed" date has passed when the listing goes up. A job posting is read the same way. An "Application deadline" before the "Posted" date has passed when the posting goes up. An earnings release is read the same way. An "Earnings call" before the "Reporting period" ends would discuss results for a period that has not closed; a line stating a period is compared by the period's last day. A checkup or lab report is read the same way. A "Report date" before the "Examination date" or the "Collection date" reports results that did not exist yet. A product warranty is read the same way. A "Registration deadline" before the "Purchase date" has passed when the product is bought. A hotel or car rental booking is read the same way. A "Check-out" before the "Check-in", or a "Drop-off" before the "Pick-up", leaves before arriving; a "Free cancellation until" date after the check-in or the pick-up lets the booking be cancelled free once it has started, so one of the dates is wrong. The finding is on whichever of the two dates is written second. The pairs of dates that must come in order are listed, pair by pair, in the language's vocabulary. A loan or an installment plan is read the same way. A "First payment date" before the "Contract date" has passed when the contract is signed. A recall notice is read the same way. A deadline for replacement or refund requests before the "Notice date" has passed when the notice goes out. A payslip is read the same way. A "Pay date" before the "Pay period" ends pays for work not yet done. A trip or an expense report is read the same way. A "Return" before the "Departure" comes back before leaving. A purchase order or a delivery note is read the same way. A "Delivery date" before the "Order date" delivers goods not yet ordered. An academic transcript or a certificate of graduation or completion is read the same way. A "Date of graduation" or "Date of completion" before the "Date of enrolment" ends the course before it began, and a "Date of issue" before the graduation or completion date certifies a graduation that has not happened yet. An annual earnings and tax withholding statement is read the same way. An "Issue date" before the "Tax year" ends, or before the "Leaving date", states the year's amounts before they are final. A packing list or a commercial invoice is read the same way. An "Arrival date" or "Estimated arrival" before the "On-board date" arrives before the goods are shipped. An itemized medical bill is read the same way. A "Date issued" before the "Date of visit" bills a visit that has not happened yet, and a "Date of discharge" before the "Date of admission" leaves hospital before arriving. A tenancy's deposit settlement is read the same way. A "Move-out date" before the "Move-in date" leaves before moving in, and a "Notice date" after the "Move-out date" gives notice once the tenant has already left. A car's service record is read the same way. A "Next inspection due" before the "Service date" has passed when the car is serviced. A construction or renovation quote is read the same way. A "Completion date" or "Handover date" before the "Start date" or "Construction start" finishes the work before it begins. A phone bill or a service contract is read the same way. A "Service end date" or "Contract end date" before the "Service start date" or "Contract start date" ends the service before it began. A price list, a coupon or a policy is read the same way. A "Valid until" or an "Expiry date" before the "Valid from" or the "Effective date" ends before it begins. A bank statement whose period is written as two lines is read the same way. A "Period end" before the "Period start" ends the period before it begins. An insurance or benefit claim is read the same way. A "Date of claim" before the "Date of incident" claims for a loss that has not happened yet. A treasurer's report or an income and expenditure statement is read the same way. An audit date before the "Fiscal year" or the "Financial year" ends audits accounts that have not closed. When one table's header names both columns of a pair, as a points statement's "Date" and "Expires" do, the two dates of each row are compared. Points that expire before the date they were earned have lapsed on arrival. A row is never compared with another row or another table. A property sale's settlement statement is read the same way. A "Settlement date" or "Closing date" before the "Contract date" pays and hands over the property before the sale is agreed. A banquet or meeting room quote runs the other way. A "Valid until" date after the "Event date" lets the quote be accepted once the event is over.
 
 message:
-  ja: 期限 {due} が、発行日 {issued} より前です
+  ja: 期限（{due}）が、発行日（{issued}）より前です
   en: "The due date {due} is before the issue date {issued}"
 
 messages:
   meeting:
-    ja: 宿題の期限 {due} が、会議の日 {meeting} より前です
+    ja: 宿題の期限（{due}）が、会議の日（{meeting}）より前です
     en: "The action item's due date {due} is before the meeting date {meeting}"
+  order:
+    ja: 「{later_label}」（{later}）が、「{earlier_label}」（{earlier}）より前です
+    en: '"{later_label}" {later} is before "{earlier_label}" {earlier}'
+  period:
+    ja: 「{later_label}」の {later} が、「{earlier_label}」の終わり {earlier} より前です
+    en: '"{later_label}" {later} is before the end of the "{earlier_label}", {earlier}'
 
 how_to_fix:
   ja: 発行日と期限のどちらが正しいかを確かめて、片方を直してください。
@@ -33,16 +55,19 @@ levels: { normal: error, relaxed: warning }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 off_for:
-  legal: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
-  docs: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
+  legal/statute: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
+  legal/judgment: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
+  legal/patent: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
+  docs/faq: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
+  docs/glossary: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
   academic: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
   literature: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
   speech: "An invoice or a quote sets an issue date and a deadline; in other genres a past deadline is something reported on, not this document's own."
 
 group: facts
 summary:
-  ja: 請求書や見積書で、支払期限や有効期限が発行日より前の所。議事録で、宿題の期限が会議の日より前の所
-  en: A payment due date or an expiry before the issue date of an invoice or a quote, or an action item in minutes due before the meeting
+  ja: 支払期限や締切など、後に来るはずの日付が先の日付より前の所
+  en: A due date or other later date that falls before the date it must follow
 example:
   ja:
     before: |
@@ -64,5 +89,5 @@ example:
       Payment due: December 25, 2026
 
 not_flagged:
-  ja: 行の頭に発行日や期限の語が無い日付（文の中の「12月25日までにお支払いください」）、年の無い日付、一行に日付が二つある行は比べません。発行日が二つあれば、最初のものと比べます。発行日から8行以上離れた期限と、期限が過ぎたことを書いた行（「期限切れ」「延滞」）は、この文書の期限ではなく報告している期限と読んで比べません。議事録として読むのは題に「議事録」などのある文書だけです。議事録では、宿題の節（見出しに「宿題」など）の外の日付、済んだ印のある宿題（升だけの「済」、括弧の中や行末の「完了」、チェック済みの箱）、前回の宿題を振り返る節、年の無い日付で年を越す期限（12月の会議の「1月10日」）は比べません。法令・規約、手引き、論文、文学、スピーチのジャンルでは止めています。
-  en: A date without a word at the head of its line (a due date in a sentence), a date without its year, and a line with two dates are not compared. With two issue dates, the first is used. A due date eight lines or more from the issue date, and a line that says the deadline has passed (overdue, expired), are read as reporting on a deadline rather than setting this document's own, and are not compared. Only a document whose title names it as minutes (Minutes, Meeting notes) is read as minutes. In minutes, a date outside an action-items section (a heading with Action items or the like), an item marked done (a Done cell, done in brackets or at the end of the line, a checked box), a section reviewing the previous meeting's items, and a deadline without a year that falls early in the next year (Jan 10 at a December meeting) are not compared. It is off in the legal, docs, academic, literature and speech genres.
+  ja: 行の頭に発行日や期限の語が無い日付（文の中の「12月25日までにお支払いください」）、年の無い日付、一行に日付が二つある行は比べません。発行日が二つあれば、最初のものと比べます。発行日から8行以上離れた期限と、期限が過ぎたことを書いた行（「期限切れ」「延滞」）は、この文書の期限ではなく報告している期限と読んで比べません。議事録として読むのは題に「議事録」などのある文書だけです。議事録では、宿題の節（見出しに「宿題」など）の外の日付、済んだ印のある宿題（升だけの「済」、括弧の中や行末の「完了」、チェック済みの箱）、前回の宿題を振り返る節、年の無い日付で年を越す期限（12月の会議の「1月10日」）は比べません。物件の案内では、「即入居可」のように日付の無い入居可能日、年の無い日付、「即入居」「即日」のある行、掲載日から40行以上離れた日付は比べません。求人では、「随時」のように日付の無い締切と年の無い日付は比べません。決算短信では、対象期間の行の無い文書、年の無い説明会の日、行の頭が「前回説明会」のように別の回を言う日、「発表日」や「説明会開催日」だけの日は比べません。健診や検査の結果では、「報告日」とだけ比べ、「発行日」や「作成日」とは比べません。受診券や検査の依頼書は、受診日や採血日より前に発行するからです。保証書では、日付の無い締切（「お早めに」）と年の無い日付は比べません。予約では、同じ日のチェックインとチェックアウト（日帰り）、同じ日のキャンセル期限、時刻だけの行（「15:00から」）、年の無い日付は比べません。「出発日」は、旅券や書類の返却日より後に来ることがあるので、貸出の日と読みません。チェックアウトとキャンセル期限、返却とチェックインのように、別の組の語どうしは比べません。法令、判決、特許、よくある質問、用語集、論文、文学、スピーチのジャンルでは止めています。契約と手引きでは動きます。保証書や規約は、その文書の日付と締切を自分で決めるからです。ローンや分割払いでは、初回お支払日を「ご契約日」とだけ比べ、「発行日」や「お申込日」とは比べません。変更や借り換えの申込書は、今の返済予定より後に申し込むからです。回収のお知らせでは、交換や返金の受付期限だけを比べ、年の無い日付と、「受付期限」「お申し込み期限」だけの締切や「発表日」「公表日」は比べません。受付を終えたお知らせは過ぎた締切を書き、懸賞の結果は締切より後に発表するからです。給与明細では、支給日を支給対象期間、計算期間、対象期間の終わりとだけ比べ、同じ日の支給日と年の無い日付は比べません。出張では、帰着を出発とだけ比べ、同じ日の帰着（日帰り）と年の無い日付は比べません。「返却日」は帰着と読みません。旅の案内では、書類の返却日が出発日より前に来るからです。発注書や納品書では、納期、納品日、納入日を発注日、注文日、受注日とだけ比べ、同じ日の納品と年の無い日付は比べません。「納期限」は納期と読みません。成績証明書では、卒業や修了の日を入学の日（入学年月日、入学日）と、発行日と証明日を卒業や修了の日とだけ比べ、入学の日と発行日は比べません。同じ日と年の無い日付も比べません。組の先の日付と後の日付がどちらも何行もある文書（学歴の表のように一行に一件ずつ書いたもの）では、後の日付を、いちばん近くに書いた先の日付より前のときだけ指します。一度だけ書いた後の日付（記録の下の発行日）は、最初の先の日付と比べます。給与所得と源泉徴収税額の明細書では、「交付日」を対象期間の終わりと退職日とだけ比べ、同じ日と年の無い日付は比べません。「発行日」は交付日と読みません。前払いの請求書は対象期間の初めに発行し、退職の手続きの案内は退職日より前に発行するからです。梱包明細書やインボイスでは、到着日と到着予定日を船積日とだけ比べ、「請求日」とは比べません。インボイスの日付は、船積みの前にも後にも来るからです。予定の日（到着予定日）は後に来る側にだけ読み、同じ日と年の無い日付は比べません。診療明細書では、「発行日」を「診療日」とだけ比べ、「受診日」とは比べません。受診券は受診日より前に発行するからです。入院では、退院日を入院日とだけ比べ、同じ日の退院と年の無い日付は比べません。賃貸借では、退去日、明渡日、退去予定日を、入居日や入居開始日と、解約通知日や解約予告日とそれぞれ比べ、同じ日と年の無い日付は比べません。予定の日（退去予定日）は後に来る側にだけ読み、「入居予定日」は入居日と読みません。空室の案内の入居予定日は、前の借主の退去日より後に来るからです。車の整備では、次回点検日、次回点検予定日、次回車検を、整備日、入庫日、点検日、作業日とだけ比べ、同じ日と年の無い日付は比べません。「前回点検日」は後に来る側に読みません。前の点検は今回の整備より前に来るからです。健診の「検査日」や「報告日」とは組みません。工事では、完工日、完工予定日、竣工日、竣工予定日、引渡日を、着工日、工事開始日、着工予定日とだけ比べ、同じ日と年の無い日付は比べません。サービスの利用期間では、ご利用終了日、利用終了日、契約終了日、サービス終了日を、ご利用開始日、利用開始日、契約開始日、サービス開始日とだけ比べ、同じ日と年の無い日付は比べません。「開始日」「終了日」だけの語は組みません。工程表や作業の記録も使うからです。「契約日」は契約開始日と読みません。価格表や証書では、適用終了日、有効終了日、有効期限を、適用開始日、有効開始日、発効日とだけ比べ、同じ日と年の無い日付は比べません。「有効期限」は、これまでどおり発行日とも別の組として比べます。明細では、照会終了日、対象期間終了日、期間終了日を、照会開始日、対象期間開始日、期間開始日とだけ比べ、同じ日と年の無い日付は比べません。「対象期間開始日」は、期間を書く「対象期間」と読みません。保険金の請求では、事故日、事故発生日、発生日、受傷日、発病日を、請求日、請求書作成日、申請日とだけ比べ、同じ日と年の無い日付は比べません。会計報告書では、監査日、会計監査日、監査実施日を、会計年度と事業年度の終わりとだけ比べ、同じ日、年の無い期間、期間を書いていない年度（「2025年度」）は比べません。「承認日」「総会承認日」「報告日」は年度の終わりと比べません。予算書は年度が始まる前に承認し、中間の報告は年度の途中に出すからです。行の頭に語の無い監査や承認の日（署名の行の日付、文の中の「定期総会で承認」）も比べません。
+  en: A date without a word at the head of its line (a due date in a sentence), a date without its year, and a line with two dates are not compared. With two issue dates, the first is used. A due date eight lines or more from the issue date, and a line that says the deadline has passed (overdue, expired), are read as reporting on a deadline rather than setting this document's own, and are not compared. Only a document whose title names it as minutes (Minutes, Meeting notes) is read as minutes. In minutes, a date outside an action-items section (a heading with Action items or the like), an item marked done (a Done cell, done in brackets or at the end of the line, a checked box), a section reviewing the previous meeting's items, and a deadline without a year that falls early in the next year (Jan 10 at a December meeting) are not compared. In a listing, a move-in date without a date (Available now), a date without its year, a line saying immediately, and a date forty lines or more from the listing date are not compared. In a job posting, a deadline without a date (Open until filled) and a date without its year are not compared; a bare "Posted" pairs only with an application deadline, not with the dates of a blog post or release notes. In an earnings release, a document without a reporting period line, a call date without its year, a line naming another call (Previous call) and a bare "Release date" or "Conference call" are not compared. In a checkup or lab report, only a report date (Report date, Date reported) is compared, not a bare "Issue date", since an admission ticket or a lab order is issued before the test or collection date it names. In a warranty, a deadline without a date, a date without its year, and "Register by" followed directly by the date without a colon are not compared. In a booking, a same-day check-in and check-out (a day use), a cancellation deadline on the check-in day, a line with only a time (from 3:00 PM) and a date without its year are not compared; a bare "Return" is not read as a drop-off, since an order's return window uses it too. Words of different pairs are not compared either (a check-out and a cancellation deadline, a drop-off and a check-in). It is off for statutes, judgments, patents, FAQs, glossaries, and the academic, literature and speech genres. It runs on contracts and manuals, which set their own dates and deadlines, as a warranty does. In a loan or an installment plan, a first payment date is compared only with the contract date (Contract date, Agreement date), not with the issue date or an application date, since a change or refinancing form is signed after the current schedule began. In a recall notice, only a replacement, refund or exchange deadline is compared; a date without its year and a bare "Requests accepted until" or "Deadline for requests" are not, since a notice that a window has closed states the deadline that has passed. In a payslip, a pay date is compared only with the end of the pay period; a pay date on the period's last day and a date without its year are not compared. In a trip, a return is compared only with the departure; a same-day return (a day trip) and a date without its year are not compared, and a "Return date" is not read as the trip's return, since a guide's return date for forms comes before the departure. In a purchase order or a delivery note, a delivery date is compared only with the order date (Order date, PO date); a same-day delivery and a date without its year are not compared, and a bare "Due date" is not read as a delivery date, since an invoice uses it for the payment due date. In a transcript, a graduation or completion date is compared only with the enrolment date (Date of enrolment, Date of admission), and the issue date only with the graduation or completion date, never with the enrolment date; a same-day date and a date without its year are not compared. Where both dates of a pair are written on several lines (an education history listing one school per row), a later date is pointed out only when it is also before the earlier date written closest to it; a later date written once (an issue date below the records) is compared with the first. In a tax statement, the issue date (Issue date, Date of issue) is compared only with the end of the tax year (Tax year) and the leaving date (Leaving date, Date of leaving); a same-day date and a date without its year are not compared, and a "Period covered" is not read as the tax year, since an invoice billed in advance is issued at the start of the period it covers. In a packing list or a commercial invoice, an arrival date (Arrival date, Estimated arrival, ETA) is compared only with the shipment date (On-board date, Shipment date), never with the invoice date, since an invoice may be dated before or after shipment; an estimated date is read only as the later side, and a same-day arrival and a date without its year are not compared. In a medical bill, the issue date (Date issued) is compared only with the date of visit; a same-day issue and a date without its year are not compared. In a hospital stay, a discharge date is compared only with the admission date; a same-day discharge is not reported, and a "Date of admission" is compared with a discharge date and with a graduation date as two separate pairs. In a tenancy, a move-out date (Move-out date, Planned move-out date) is compared with the move-in date and, separately, with the notice date (Notice date, Date of notice); a same-day date and a date without its year are not compared, a planned date is read only as the later side, and a "Planned move-in date" is not read as the move-in date, since a vacancy notice's planned move-in comes after the previous tenant's move-out. In a car's service record, the next inspection (Next inspection, Next inspection due, Next service due) is compared only with the service date (Service date, Date of service); a same-day date and a date without its year are not compared, and a "Last inspection date" is not read as the later side, since the last inspection comes before this service. A lab report's "Test date" or "Report date" is not paired with it. In a construction or renovation document, a completion or handover date (Completion date, Expected completion, Handover date) is compared only with the start (Work start, Construction start, Start date); a same-day date and a date without its year are not compared. A bare "Start date" is compared with a completion date only, never with a "Handover date", since it also heads a new hire's first day, and a handover can come before that; a transcript's "Date of completion" is not read as the end of the works. In a service period, the end date (Service end date, End of service, Contract end date) is compared only with the start date (Service start date, Start of service, Contract start date); a same-day end and a date without its year are not compared, and a bare "Start date" or "End date" is not read, since a project plan or a timesheet uses them too. In a price list, a coupon or a policy, the end of the validity (Valid until, Valid to, Expiry date, Expires) is compared only with its start (Valid from, Effective date, Effective from); a same-day date and a date without its year are not compared, and "Expires" is read only at the head of a line followed by a colon or the date, not in a sentence (your password expires). "Valid until" and "Expires" are still compared with the issue date, as a separate pair. In a statement whose period is written as two lines, the end (Period end, Statement period end) is compared only with the start (Period start, Statement period start); a same-day date and a date without its year are not compared. In an insurance claim, the incident date (Date of incident, Date of loss, Incident date, Date of injury) is compared only with the claim date (Date of claim, Claim date); a same-day claim and a date without its year are not compared. In a treasurer's report, an audit date (Audited, Date audited, Audit date, Date of audit) is compared only with the end of the fiscal or financial year; a same-day date, a period without its year and a year written without its dates (Financial year 2025–26) are not compared. An approval or report date (Approved, Report date) is not compared with the year's end, since a budget is approved before its year begins and an interim report is dated inside the year. An audit or approval date without a word at the head of its line (the date on a signature line, an approval at the annual general meeting in a sentence) is not compared either.