chaffjs 0.35.0 → 0.37.0

package/rules/total-mismatch.yaml

@@ -61,5 +61,5 @@ example:
       | Total | $8,000 |
 
 not_flagged:
-  ja: 単位や列の違う金額は足しません。合計の語に表の見出しが名指さない語を付けた行（見出しが「項目」の表の「消費税合計」）は、別の種類の合計かもしれないので比べません。差引合計・控除合計も、表の最後の行でないとき、上に合計の行や総支給額・支給合計の行があるとき、金額の列が二つ以上あるときは比べず、下から続けた行の和か、その上の行の和からそれを引いた額と合えば指しません。面積のように、上の行の和とは限らない量の合計（面積合計）も比べません。前の期間の合計（前年合計）は読まず、期間を付けた合計が内訳の和を一年に直した額（ちょうど4倍・12倍・52倍。月額の内訳に年間合計）なら比べません。重さ・容量・長さ（mg、g、mL、L、cm、km）は、列のどの行も同じ種類の量なら換算して足します（500mg と 0.5g は 1g）。何あたりかを書いた量（300mg/錠）、目安の量（約300mg）、範囲（300〜400mg）がある列は足しません。足し方が何通りもあるとき（小計と税のあとの総計など）は、どれとも合わないときだけ指します。文の中では、合計の語（合計・総額）のすぐ後ろの金額か内訳の語（内訳は）のすぐ前の金額だけを合計と読み、内訳の金額が二つ以上あるときだけ比べます。並びの一部（単価や上限など、合計の語から離れた金額を除いた並び）の和か、一つを引いた額（値引き）と合えば指しません。合計のすぐ後ろの「：」から続く内訳は、「うち」「または」「最大」のように内訳のすべてとは限らない語があるとき、ほかの単位の金額や割合を並べたときは比べません。
-  en: Amounts in another unit or column are not added. A total with a word the table's header does not name ("Total tax" under "Item") is not compared, as it may be a total of another kind, nor is a total of a quantity that need not be the sum of the rows (Total area). Under such a header, "Total deductions" is not compared when it is not the last row, when a total or a gross or net amount (Gross pay) is above it, or when the table has two columns of amounts; it is not reported when it matches the last few rows, or the rows above those less them. A total for another span ("Prior-year total") is not read, and a total naming its span that is the items scaled to a year (exactly 4, 12 or 52 times their sum, as monthly items under an annual total) is not compared. Mass, volume and length (mg, g, mL, L, cm, km) are converted and added when every row of the column is the same kind of measure (500 mg and 0.5 g make 1 g); a column with an amount per something (300 mg/tablet), a rough amount (about 300 mg) or a range (300-400 mg) is not added. Where there is more than one way to add them up, it is reported only when none matches. In a sentence, only the amount right after a total phrase (a total of) or right before a breakdown phrase (made up of) is read as a total, and only when two or more items in its unit are listed. It is not reported when the items nearest the phrase add up to it, or when it matches with one item taken away (a discount). Items after a colon or a dash right after a total are not compared when "including", "or" or "up to" shows they may not be every item, when one of them is in another unit, or when they are percentages.
+  ja: 単位や列の違う金額は足しません。合計の語に表の見出しが名指さない語を付けた行（見出しが「項目」の表の「消費税合計」）は、別の種類の合計かもしれないので比べません。差引合計・控除合計も、表の最後の行でないとき、上に合計の行や総支給額・支給合計の行があるとき、金額の列が二つ以上あるときは比べず、下から続けた行の和か、その上の行の和からそれを引いた額と合えば指しません。面積のように、上の行の和とは限らない量の合計（面積合計）も比べません。前の期間の合計（前年合計）は読まず、期間を付けた合計が内訳の和を一年に直した額（ちょうど4倍・12倍・52倍。月額の内訳に年間合計）なら比べません。重さ・容量・長さ（mg、g、mL、L、cm、km）は、列のどの行も同じ種類の量なら換算して足します（500mg と 0.5g は 1g）。何あたりかを書いた量（300mg/錠）、目安の量（約300mg）、範囲（300〜400mg）がある列は足しません。足し方が何通りもあるとき（小計と税のあとの総計など）は、どれとも合わないときだけ指します。文の中では、合計の語（合計・総額）のすぐ後ろの金額か内訳の語（内訳は）のすぐ前の金額だけを合計と読み、内訳の金額が二つ以上あるときだけ比べます。並びの一部（単価や上限など、合計の語から離れた金額を除いた並び）の和か、一つを引いた額（値引き）と合えば指しません。合計のすぐ後ろの「：」から続く内訳は、「うち」「または」「最大」のように内訳のすべてとは限らない語があるとき、ほかの単位の金額や割合を並べたときは比べません。内訳の前に主なものだけだと言う語（「主な設備投資は」「主な内訳は」「主に」）があれば、内訳は合計のすべてではないので比べません。合計と内訳のどれもが丸めた単位（百万円・千円・億円、million）で有効数字3桁以上（6,655百万円。4億円は除く）で書いてあれば、ずれが（内訳の数 − 1）× 最後の桁一つ分まで（三つの内訳を百万円で書いたなら2百万円まで）は、四捨五入や切り捨てのずれとして指しません。
+  en: Amounts in another unit or column are not added. A total with a word the table's header does not name ("Total tax" under "Item") is not compared, as it may be a total of another kind, nor is a total of a quantity that need not be the sum of the rows (Total area). Under such a header, "Total deductions" is not compared when it is not the last row, when a total or a gross or net amount (Gross pay) is above it, or when the table has two columns of amounts; it is not reported when it matches the last few rows, or the rows above those less them. A total for another span ("Prior-year total") is not read, and a total naming its span that is the items scaled to a year (exactly 4, 12 or 52 times their sum, as monthly items under an annual total) is not compared. Mass, volume and length (mg, g, mL, L, cm, km) are converted and added when every row of the column is the same kind of measure (500 mg and 0.5 g make 1 g); a column with an amount per something (300 mg/tablet), a rough amount (about 300 mg) or a range (300-400 mg) is not added. Where there is more than one way to add them up, it is reported only when none matches. In a sentence, only the amount right after a total phrase (a total of) or right before a breakdown phrase (made up of) is read as a total, and only when two or more items in its unit are listed. It is not reported when the items nearest the phrase add up to it, or when it matches with one item taken away (a discount). Items after a colon or a dash right after a total are not compared when "including", "or" or "up to" shows they may not be every item, when one of them is in another unit, or when they are percentages. Items introduced as only the main ones ("mainly", 主な) are not compared, as they need not be every item. When the total and every item are written in a rounded unit (millions, billions, 百万円) with at least three significant digits ($6,655 million, not $4 million), a difference of up to (number of items − 1) last digits ($2 million for three items in whole millions) is rounding and is not reported.

package/rules/translationese-density.yaml

@@ -43,8 +43,8 @@ example:
       この機能を使うと、設定を共有できます。速度にはキャッシュが大きく効きます。設定は設定画面からいつでも変えられます。
 
 not_flagged:
-  ja: 一つ一つは誤りではないので、短い文書（500 字未満）は測りません。人の書いた技術記事でもふつうに使う言い回し（〜を提供する、〜に焦点を当てる、〜することができる）は数えません。文学のジャンルでは既定で止めています（人物を「彼女は」と呼ぶのは小説の書き方です）。
-  en: None of these is wrong alone, so documents shorter than 500 characters are not measured. Phrasings common in human technical writing (を提供する, に焦点を当てる, することができる) are not counted. The literature preset turns it off, since a novel calls its characters 彼女.
+  ja: 一つ一つは誤りではないので、短い文書（500 字未満）は測りません。人の書いた技術記事でもふつうに使う言い回し（〜を提供する、〜に焦点を当てる、〜することができる）は数えません。読み手への呼びかけ（あなたの、あなたは）だけの文書は、読み手に語りかける書き方を選んだものとして言いません（ほかの言い回しと重なれば数えます）。文学のジャンルでは既定で止めています（人物を「彼女は」と呼ぶのは小説の書き方です）。
+  en: None of these is wrong alone, so documents shorter than 500 characters are not measured. Phrasings common in human technical writing (を提供する, に焦点を当てる, することができる) are not counted. A document whose only such phrases address the reader (あなたの, あなたは) has chosen to speak to its reader and is not reported; beside other phrases they count. The literature preset turns it off, since a novel calls its characters 彼女.
 level_meaning:
   ja: 1000 字あたり翻訳調の言い回し {limit} 個まで
   en: up to {limit} translated phrasings per 1000 characters

package/rules/undefined-acronym.yaml

@@ -8,6 +8,7 @@ extra_word_lists:
     definition-marker,
     definition-verb,
     definition-statement,
+    definition-alternative,
     meridiem,
     time-zone,
     currency-code,
@@ -21,6 +22,7 @@ extra_word_lists:
     http-method,
     reference-list-heading,
     legal-form,
+    company-form,
     citation-series,
     carrier-name,
     name-prefix,
@@ -28,6 +30,7 @@ extra_word_lists:
     tax-code,
     capital-phrase,
     name-determiner,
+    abbreviation-mention,
   ]
 uses: [pos]
 severity: info
@@ -76,8 +79,8 @@ example:
     after: Our key goal indicator (KGI) this term is to reach product-market fit (PMF).
 
 not_flagged:
-  ja: 誰でも知っている略語（URL、PDF など）と、前後の括弧で説明した略語は指しません。
-  en: Common acronyms (URL, PDF) and acronyms spelled out in brackets next to them are not reported.
+  ja: 誰でも知っている略語（URL、PDF など）と、前後の括弧で説明した略語、会社の名前の中の英字（㈱ADEKA、CO.,LTD.）は指しません。ひな形の名前の置き場所（OOOO、XX 月）と、外のページへのリンクを並べた一覧の題名の中の略語も指しません（題名の略語は数には入れます）。大文字の違うだけの書き方で説明した略語（TCoP と TCOP）、略語を話題にする文で語に書き出した略語（略語の DOB … date of birth）、一覧で語のすぐ下にその語を名指すリンクを入れ子にした語（- GPL の下の GNU General Public License）も指しません。
+  en: Common acronyms (URL, PDF), acronyms spelled out in brackets next to them, and the letters of a company name (㈱ADEKA, CO.,LTD.) are not reported. Neither are a template's placeholders (OOOO, XX 月) or an acronym in the title of a page in a list of links (it still counts towards the limit). Nor are an acronym explained under another capitalisation (TCoP, then TCOP), one a sentence about the abbreviation writes out (the abbreviation DOB … date of birth), or a term in a list whose nested link names it (- GPL above GNU General Public License).
 level_meaning:
   ja: 説明のない略語が {limit} 種類あれば指摘。文書が自分で略語を {limit} 個展開していれば、1 つの抜けから指摘
   en: reported once {limit} different acronyms go unexplained, or from the first one when the document itself spells out {limit} others

package/rules/undefined-term.yaml

@@ -69,8 +69,8 @@ example:
       1. The Supplier shall provide the hosting services (the "Services") to the Customer.
 
 not_flagged:
-  ja: 文書が「本」を付けた語を一つも定義していなければ見ません。定義した語とその言い換え（本件業務、defined-term-form が見ます）、定義した語で始まる語（本サービス上）、この文書やその一部を指す語（本条、本項、本書、本契約、本利用規約、本サイト）、どこかでかぎ括弧に入れた語（定義の書き方を chaff が読めなかったもの）、一語の言葉（本人、本日、本社）は見ません。同じ語は最初の一か所だけ指します。英語は、大文字は法令・組織・方針の名前（the Federal Trade Commission Act、Acceptable Use Policies）にも使うので、狭く読みます。"X" means や (the "X") の形の定義が二つ未満の文書は見ません。文の頭や記号の後ろの語、小文字の名詞の前に付けた語（the Premium plan）、名前の一覧（proper-name-word、地名、曜日と月、会社の形、当事者の役割）の語を含むもの、条の参照（Section 4、Schedule A）、前後の語から名前と分かるもの（後ろに番号が付く Proposition 65、長い名前の頭 Post Holdings, Inc. や Canton, Ohio や the Federal Food, Drug, and Cosmetic Act、直後の括弧で定義するもの Certificate of Analysis (“COA”) や the Closing (as defined in the Merger Agreement)、文書が定義した略語の頭文字になるもの “IRS” means the Internal Revenue Service、当事者の立場 Citibank, N.A., as Administrative Agent）、見出し・リンク・太字・HTML の要素・表・箇条書きの見出し・条の頭の見出し（5.8 No Representation or Warranty.）の中、どこかで引用符か太字に入れた語、定義した語を含むもの（大文字小文字を問いません）、文書のどこかで小文字でも書いた語（your Account と your account。普通の語か画面の名前）は見ません。法令・判決・特許は見ません。契約書・規約のジャンルで見ます。
-  en: "A document that defines no term with the prefix is not read. Defined terms and their other-prefix forms (本件業務, which defined-term-form reads), terms that start with a defined term (本サービス上), the document's names for itself and its parts (本条, 本項, 本書, 本契約, 本利用規約, 本サイト), terms set in quotes anywhere (a definition chaff could not read), and single words (本人, 本日, 本社) are not reported. Each term is reported once, at its first use. English is read narrowly, since capitals also name laws, organisations and policies (the Federal Trade Commission Act, Acceptable Use Policies): a document with fewer than two definitions written with a defining word (“X” means, (the “X”)) is not read; and a word at the start of a sentence or after a mark, a modifier of a lower-case noun (the Premium plan), a run holding a word of the name lists (proper-name-word, places, weekdays and months, company forms, party roles), a reference to a part (Section 4, Schedule A), a name shown by the words around it (a number after it: Proposition 65; a longer name it starts: Post Holdings, Inc., Canton, Ohio, the Federal Food, Drug, and Cosmetic Act; brackets right after it that define it: Certificate of Analysis (“COA”), the Closing (as defined in the Merger Agreement); initials that spell a term the document defines: “IRS” means the Internal Revenue Service; a party's capacity: Citibank, N.A., as Administrative Agent), anything inside a heading, a link, bold, an HTML element, a table, a list item's label or a clause's run-in caption (5.8 No Representation or Warranty.), a word set in quotes or bold anywhere, a run holding a defined term in any case, and a word the document also writes in lower case (your Account and your account: an ordinary word or a screen's name) are not reported. Statutes, court decisions and patents are not read; the contract genre runs this rule."
+  ja: 文書が「本」を付けた語を一つも定義していなければ見ません。定義した語とその言い換え（本件業務、defined-term-form が見ます）、定義した語で始まる語（本サービス上）、この文書やその一部を指す語（本条、本項、本書、本契約、本利用規約、本サイト）、どこかでかぎ括弧に入れた語（定義の書き方を chaff が読めなかったもの）、一語の言葉（本人、本日、本社）は見ません。同じ語は最初の一か所だけ指します。英語は、大文字は法令・組織・方針の名前（the Federal Trade Commission Act、Acceptable Use Policies）にも使うので、狭く読みます。"X" means や (the "X") の形の定義が二つ未満の文書は見ません。文の頭や記号の後ろの語、小文字の名詞の前に付けた語（the Premium plan）、名前の一覧（proper-name-word、地名、曜日と月、会社の形、当事者の役割）の語を含むもの、条の参照（Section 4、Schedule A）、前後の語から名前と分かるもの（後ろに番号が付く Proposition 65、長い名前の頭 Post Holdings, Inc. や Canton, Ohio や the Federal Food, Drug, and Cosmetic Act、直後の括弧で定義するもの Certificate of Analysis (“COA”) や the Closing (as defined in the Merger Agreement)、文書が定義した略語の頭文字になるもの “IRS” means the Internal Revenue Service、当事者の立場 Citibank, N.A., as Administrative Agent、すぐ後ろの attached hereto などで添付した書式の題と分かるもの the Termination Certificate attached hereto）、見出し・リンク・太字・HTML の要素・表・箇条書きの見出し・条の頭の見出し（5.8 No Representation or Warranty.）の中、どこかで引用符か太字に入れた語、定義した語を含むもの（大文字小文字を問いません）、文書のどこかで小文字でも書いた語（your Account と your account。普通の語か画面の名前）は見ません。法令・判決・特許は見ません。契約書・規約のジャンルで見ます。
+  en: "A document that defines no term with the prefix is not read. Defined terms and their other-prefix forms (本件業務, which defined-term-form reads), terms that start with a defined term (本サービス上), the document's names for itself and its parts (本条, 本項, 本書, 本契約, 本利用規約, 本サイト), terms set in quotes anywhere (a definition chaff could not read), and single words (本人, 本日, 本社) are not reported. Each term is reported once, at its first use. English is read narrowly, since capitals also name laws, organisations and policies (the Federal Trade Commission Act, Acceptable Use Policies): a document with fewer than two definitions written with a defining word (“X” means, (the “X”)) is not read; and a word at the start of a sentence or after a mark, a modifier of a lower-case noun (the Premium plan), a run holding a word of the name lists (proper-name-word, places, weekdays and months, company forms, party roles), a reference to a part (Section 4, Schedule A), a name shown by the words around it (a number after it: Proposition 65; a longer name it starts: Post Holdings, Inc., Canton, Ohio, the Federal Food, Drug, and Cosmetic Act; brackets right after it that define it: Certificate of Analysis (“COA”), the Closing (as defined in the Merger Agreement); initials that spell a term the document defines: “IRS” means the Internal Revenue Service; a party's capacity: Citibank, N.A., as Administrative Agent; words right after it that make it the title of an attached form: the Termination Certificate attached hereto), anything inside a heading, a link, bold, an HTML element, a table, a list item's label or a clause's run-in caption (5.8 No Representation or Warranty.), a word set in quotes or bold anywhere, a run holding a defined term in any case, and a word the document also writes in lower case (your Account and your account: an ordinary word or a screen's name) are not reported. Statutes, court decisions and patents are not read; the contract genre runs this rule."
 rewrite:
   depth: light
   ja:

package/rules/unfilled-placeholder.yaml

@@ -10,8 +10,8 @@ name:
   en: Unfilled placeholder
 
 why:
-  ja: "「【会社名】」「[Your Name]」「（ここに会社名を書く）」は、雛形や生成した下書きに残る空欄です。値に「TODO: …」「未定」とだけ書いたものも、後で埋めるつもりの空欄です。文体の好みではなく、埋め忘れです。例として置いた「○○」は正しい書き方なので数えません。"
-  en: '"[Your Name]" and "[Insert Date]" are the blanks a template or a generated draft leaves. A value that only says "TODO: …" or "TBD" is a blank too, left to fill in later. This is not a matter of style: the blank was never filled.'
+  ja: "「【会社名】」「[Your Name]」「（ここに会社名を書く）」は、雛形や生成した下書きに残る空欄です。値に「TODO: …」「未定」とだけ書いたものも、後で埋めるつもりの空欄です。英語の雛形の指示の行（OPTIONAL: General conclusions …）が、埋めた報告書に残ったものも同じです。文体の好みではなく、埋め忘れです。例として置いた「○○」は正しい書き方なので数えません。"
+  en: '"[Your Name]" and "[Insert Date]" are the blanks a template or a generated draft leaves. A value that only says "TODO: …" or "TBD" is a blank too, left to fill in later, and so is an instruction line from the template left in a filled report ("OPTIONAL: General conclusions …"). This is not a matter of style: the blank was never filled.'
 
 message:
   ja: 「{matched}」が埋まっていません
@@ -43,5 +43,5 @@ example:
       We can meet on Friday 9 October to go through the quote.
 
 not_flagged:
-  ja: "例として置いた「○○」、Markdown のリンク、脚注の番号、チェック欄とチェックリストの項目（- [ ] TODO: …）、値が続く見出しの札（【氏名】山田）、コードとコードのコメント（// TODO）、文の中の「未定」（日程は未定です）、見出しが雛形と言う節（「## 雛形」「# 記入例」）の中の空欄は指しません。"
-  en: 'Markdown links and reference definitions, footnote numbers, checkboxes and checklist items ("- [ ] TODO: …"), a label its value follows ("[Date]: 2024-04-01"), code and code comments ("// TODO"), "TBD" inside a sentence ("the date is TBD"), and blanks under a heading that names a template ("## Template", "# Sample letter") are not reported.'
+  ja: "例として置いた「○○」、Markdown のリンク、脚注の番号、チェック欄とチェックリストの項目（- [ ] TODO: …）、値が続く見出しの札（【氏名】山田）、大文字でない「Optional:」と行の途中の OPTIONAL、コードとコードのコメント（// TODO）、文の中の「未定」（日程は未定です）、見出しが雛形と言う節（「## 雛形」「# 記入例」）の中の空欄は指しません。"
+  en: 'Markdown links and reference definitions, footnote numbers, checkboxes and checklist items ("- [ ] TODO: …"), a label its value follows ("[Date]: 2024-04-01"), "Optional:" not in capitals and OPTIONAL inside a line, code and code comments ("// TODO"), "TBD" inside a sentence ("the date is TBD"), and blanks under a heading that names a template ("## Template", "# Sample letter") are not reported.'

package/rules/unqualified-superlative.yaml

@@ -46,7 +46,7 @@ example:
     after: Our new product processes orders a fifth faster than the previous model.
 
 not_flagged:
-  ja: 「当社比」「〜の中で」「〜のほうが」のように、比べる相手や範囲が同じ文にあれば指しません。「SES との最大の違い」のように、最上級のすぐ前に相手があるときも同じです。「国内最大」「業界最速」のように名詞がじかに付いた最上級と、「日本で最も」のように名前と「で」が前にある最上級は、範囲を言っているので指しません。「バグを検出できる唯一のルール」のように、動詞で終わる節が最上級のすぐ前にあって範囲を決めているときも同じです。「」や引用符で引いた言葉の中の最上級は、書き手の主張ではないので指しません。
+  ja: 「当社比」「〜の中で」「〜のほうが」のように、比べる相手や範囲が同じ文にあれば指しません。「SES との最大の違い」のように、最上級のすぐ前に相手があるときも同じです。「国内最大」「業界最速」のように名詞がじかに付いた最上級と、「日本で最も」のように名前と「で」が前にある最上級は、範囲を言っているので指しません。「バグを検出できる唯一のルール」のように、動詞で終わる節が最上級のすぐ前にあって範囲を決めているときも同じです。「」や引用符で引いた言葉の中の最上級は、書き手の主張ではないので指しません。「最大化する」のように接尾辞が付いて別の語になったものも指しません。
   en: A superlative with its comparison or scope in the same sentence ("in our range", "than last year", "the fastest in the industry") is not reported, nor is one limited by a clause ("the best we have measured"), nor one inside quotation marks, which are someone else's words.
 level_meaning:
   ja: 比べる相手のない最上級が {limit} 箇所あれば指摘

package/rules/unused-definition.yaml

@@ -48,8 +48,8 @@ example:
       "Service" means the booking website we run. Users may use the Service free of charge.
 
 not_flagged:
-  ja: 定義の書き方（「X」とは、以下「X」という、規約やポリシーの以下「X」といいます）で書いた語だけを見ます。複数形と所有の形（Services、Seller's）と、見出しの中の語も使用に数えます。同じ語の二つ目の定義は duplicate-definition が言います。
-  en: Only terms defined in a recognised form ("X" means, (the "X")) are checked. Plurals and possessives (Services, Seller's) count as uses, and so does the term in a heading. A second definition of the same term is duplicate-definition's to report.
+  ja: 定義の書き方（「X」とは、以下「X」という、規約やポリシーの以下「X」といいます）で書いた語だけを見ます。複数形と所有の形（Services、Seller's）と、見出しの中の語も使用に数えます。英語の動名詞と目的語の句（Exercising your options）は、動詞のほかの形で書いた所（exercise your options）も使用に数えます。同じ語の二つ目の定義は duplicate-definition が言います。
+  en: Only terms defined in a recognised form ("X" means, (the "X")) are checked. Plurals and possessives (Services, Seller's) count as uses, and so does the term in a heading. A phrase of a gerund and its object (Exercising your options) is also used where its verb is written in another form (exercise your options). A second definition of the same term is duplicate-definition's to report.
 rewrite:
   depth: light
   ja:

package/rules/use-before-definition.yaml

@@ -50,8 +50,8 @@ example:
       This agreement is between Harbour Ltd (the "Seller") and Hill Ltd (the "Buyer"). The Seller ships within five days.
 
 not_flagged:
-  ja: 定義の条（「X」とは…をいう）で定義した語は、前で使っても言いません。定義の条は文書の頭にも終わりにも置く書き方があるためです。規約やポリシーの丁寧な形（以下「X」といいます）も、法令の形と同じに読みます。見出しの行（章・節の行、条の前の「（買主の義務）」のような見出し）の語と、漢字で終わる語にさらに漢字が続く長い語（「監査委員会」の「監査委員」）と、定義の括弧の前の長い名前をそのまま書いた所（「…作成の手引き（以下「手引き」という。）」より前の「…作成の手引き」）は、使った所に数えません。最初の一か所だけを指します。別の語を定義する括弧の前の名前の中（This Services Agreement (this "Agreement") の Services、本サービス利用契約（以下「本契約」という。）の本サービス）も、使った所に数えません。
-  en: Terms defined in a definitions clause ("X" means ...) are not checked, since a definitions clause may come first or last. A heading line (a chapter or section line, or the caption above an article) does not count as a use, nor does a longer word that runs on in kanji past a term ending in kanji, nor an earlier copy of the long name written just before the definition's bracket. The polite Japanese form (以下「X」といいます) is read like the statute form. Only the first early use is pointed at. A word inside the name written right before another term's defining bracket (Services in This Services Agreement (this "Agreement")) is not a use either.
+  ja: 定義の条（「X」とは…をいう）で定義した語は、前で使っても言いません。定義の条は文書の頭にも終わりにも置く書き方があるためです。規約やポリシーの丁寧な形（以下「X」といいます）も、法令の形と同じに読みます。見出しの行（章・節の行、条の前の「（買主の義務）」のような見出し）の語と、漢字で終わる語にさらに漢字が続く長い語（「監査委員会」の「監査委員」）と、定義の括弧の前の長い名前をそのまま書いた所（「…作成の手引き（以下「手引き」という。）」より前の「…作成の手引き」）は、使った所に数えません。最初の一か所だけを指します。別の語を定義する括弧の前の名前の中（This Services Agreement (this "Agreement") の Services、本サービス利用契約（以下「本契約」という。）の本サービス）も、使った所に数えません。目次・索引の行（目次の見出しの下の項目、一行に詰めた目次、定義した語と条の番地の一覧）と、条の番号の後ろの題（Section 1.1 Closing.）と、番号と語の終わりに条の番地の括弧を添えただけの札（（1）文化芸術推進基本計画（第7条関係））と、語を含むもっと長い名前（定義の括弧の前の名前を前で写した株式会社みなと、もっと長い定義した語、Navistar Financial Corporation）も数えません。文書自身の名前と定義した語に同じ頭を付けた所（この就業規則（以下「規則」）より前の「この規則」）と、すぐ後ろの括弧に定義の長い名前を書き添えた所は、読み手に分かるので言いません。
+  en: Terms defined in a definitions clause ("X" means ...) are not checked, since a definitions clause may come first or last. A heading line (a chapter or section line, or the caption above an article) does not count as a use, nor does a longer word that runs on in kanji past a term ending in kanji, nor an earlier copy of the long name written just before the definition's bracket. The polite Japanese form (以下「X」といいます) is read like the statute form. Only the first early use is pointed at. A word inside the name written right before another term's defining bracket (Services in This Services Agreement (this "Agreement")) is not a use either. Nor are contents and index lines (the items under a contents heading, a table of contents or a list of defined terms and section numbers packed on one line), a caption after a section number (Section 1.1 Closing.), a label of a number and the term ending in a bracketed section reference ((a) Seller (Section 2)), or a longer name that holds the term, such as an earlier copy of the name before the bracket (Board of Directors before our Board of Directors ("Board")), a longer defined term, a capitalised name ending in it (Navistar Financial Corporation). The document naming itself (this Agreement before (this "Agreement")) and a use followed by the long name in brackets are clear to the reader and not pointed at.
 rewrite:
   depth: structure
   ja:

package/rules/vague-word-density.yaml

@@ -53,8 +53,8 @@ example:
       Report an incident within 30 minutes and notify the affected teams. Record it in the incident log and fix the cause by the next working day.
 
 not_flagged:
-  ja: 文書の長さに対して少ないものは指しません。短すぎる文書も測りません。指すのは語のある文ごとに一度で、長い言い方の中の語（in a timely manner の timely）は一つと数えます。英語の法務の文書では、法律や慣行が意味を決めている言い方（reasonable、best efforts、from time to time）の中の語は数えません。要求の文の中の「可能な限り」「必要に応じて」は、要求の書き方として requirement-smell も見ます。
-  en: 'A few vague words for the document''s length are not reported, and very short documents are not measured. Each sentence is reported once, and a word inside a longer phrase ("timely" in "in a timely manner") counts once. In legal documents, a word inside a term that law and practice define ("reasonable", "best efforts", "from time to time") is not counted. Inside a requirement, requirement-smell also reads "where possible" and "as needed".'
+  ja: 文書の長さに対して少ないものは指しません。短すぎる文書も測りません。指すのは語のある文ごとに一度で、長い言い方の中の語（in a timely manner の timely）は一つと数えます。英語の法務の文書では、法律や慣行が意味を決めている言い方（reasonable、best efforts、from time to time）の中の語は数えません。要求の文の中の「可能な限り」「必要に応じて」は、要求の書き方として requirement-smell も見ます。すぐ後ろの括弧で中身を書いた語（一定の事項（請求書に書く事項））も数えません。括弧が名前を付けるだけ（以下「本措置」という。）なら数えます。
+  en: 'A few vague words for the document''s length are not reported, and very short documents are not measured. Each sentence is reported once, and a word inside a longer phrase ("timely" in "in a timely manner") counts once. In legal documents, a word inside a term that law and practice define ("reasonable", "best efforts", "from time to time") is not counted. Inside a requirement, requirement-smell also reads "where possible" and "as needed". A word that the bracket right after it pins down ("a reasonable fee (USD 50)") is not counted either; a bracket that only names it ("(hereinafter the ""Fee"")") pins nothing down.'
 level_meaning:
   ja: 1000 字あたりあいまいな語 {limit} 個まで
   en: up to {limit} vague words per 1000 words

package/skills/chaff/SKILL.md

@@ -31,7 +31,9 @@ read. A contract checked as a blog post gets wrong findings, so choose the genre
    guessed or default genre shows no guide, and `--no-guide` leaves it out.
 
 A rule the genre turns off is listed under "did not run" with the genre as the reason. That is the preset's
-choice, not a gap; turn it back on (`rules:` in `chaff.yaml`) only when the person asks.
+choice, not a gap; turn it back on (`rules:` in `chaff.yaml`) only when the person asks. Some of these are off
+because chaff measured them to be mostly wrong for that kind of document on real, judged documents
+([isamu/chaff-corpus](https://github.com/isamu/chaff-corpus)); turning one back on brings those false findings back.
 
 ## Run it
 
@@ -75,6 +77,10 @@ calls nothing. Ask the person before a real run; the passages leave the machine.
 `npx chaffjs explain <rule-id>` shows why a rule exists, its levels and the current one. Read it before
 relaxing a rule.
 
+When a finding is wrong for a reason that is not about this team (chaff misread the text), tell the person and offer
+`npx chaffjs feedback <file> --rule <rule-id> --line <n>`: it drafts a report and sends nothing. A document the
+person may share can go to isamu/chaff-corpus, where wrong findings become test cases and rule fixes.
+
 ## When numbers or dates disagree
 
 The group "Facts that disagree" in `npx chaffjs rules` checks what a sum or a calendar can settle. Among them:

package/src/announced-count.ts

@@ -20,6 +20,8 @@ export type CountWords = {
   readonly hedgesBefore: readonly string[];
   /** 数か数える語のすぐ後ろにあると予告でなくなる語（以上、目、or more）。 */
   readonly hedgesAfter: readonly string[];
+  /** 数と合わせて、その一行だけで下の並びの数を言う見出しの語（3行要約、three-line summary）。 */
+  readonly titles: readonly string[];
 };
 
 export type CountMismatch = { readonly offset: number; readonly phrase: string; readonly announced: number; readonly listed: number };
@@ -101,7 +103,17 @@ const numberPattern = (words: CountWords): RegExp => {
   return new RegExp(latin.length === 0 ? digits : `${digits}|(?<![A-Za-z])(?:${alternation(latin)})(?![A-Za-z])`, "iu");
 };
 
-type Patterns = { readonly phrase: RegExp; readonly number: RegExp };
+/**
+ * 予告の塊が一行で、数と見出しの語だけ（3行要約、**Three-line summary:**）。前後でそろった強調の印と終わりのコロンは許す。
+ * 文の中の「3行要約を書いた」は予告でない。
+ */
+const titlePattern = (words: CountWords): RegExp | undefined => {
+  if (words.titles.length === 0) return undefined;
+  const numbers = words.numbers.length === 0 ? "\\p{Nd}+" : `\\p{Nd}+|${alternation(words.numbers)}`;
+  return new RegExp(`^([ \\t]*(\\*\\*|__|\\*|_)?)((${numbers})[ \\t]?(?:${alternation(words.titles)}))\\2[ \\t]*[:：]?[ \\t]*$`, "iu");
+};
+
+type Patterns = { readonly phrase: RegExp; readonly number: RegExp; readonly title: RegExp | undefined };
 
 /**
  * 数える語の無い数は、先を指す語のすぐ後ろでだけ（the following two:）。「under $75:」の金額を数に読まない。
@@ -181,20 +193,35 @@ const matchesList = (announced: number, source: string, list: BulletList): boole
 
 type Context = { readonly source: string; readonly words: CountWords; readonly patterns: Patterns; readonly neighbours: Neighbours };
 
+/** 予告の塊のどこに、何と書いて、いくつと言ったか。 */
+type Announcement = { readonly start: number; readonly phrase: string; readonly announced: number };
+
+/** 最後の一文の予告（以下の3点）か、塊が見出しの語句だけの予告（3行要約）。 */
+const announcementIn = (lead: string, words: CountWords, patterns: Patterns): Announcement | undefined => {
+  const sentenceStart = lastSentenceStart(lead);
+  const sentence = lead.slice(sentenceStart);
+  const phrase = announcedIn(sentence, words, patterns);
+  if (phrase !== undefined)
+    return { start: sentenceStart + phrase.start, phrase: sentence.slice(phrase.start, phrase.end).trim(), announced: phrase.announced };
+  const title = patterns.title?.exec(lead);
+  const written = title?.[3];
+  if (title === null || title === undefined || written === undefined) return undefined;
+  const announced = valueOf(title[4] ?? "", words.numbers);
+  return announced < 1 ? undefined : { start: (title[1] ?? "").length, phrase: written, announced };
+};
+
 const mismatchOf = ({ source, words, patterns, neighbours }: Context, list: BulletList): CountMismatch[] => {
   if (hasNeighbour(source, list.span, neighbours)) return [];
   const lead = leadBefore(source, list.span.start);
   if (lead === undefined) return [];
-  const sentenceStart = lastSentenceStart(lead.text);
-  const sentence = lead.text.slice(sentenceStart);
-  const phrase = announcedIn(sentence, words, patterns);
-  if (phrase === undefined || matchesList(phrase.announced, source, list)) return [];
-  const offset = lead.start + sentenceStart + phrase.start;
-  return [{ offset, phrase: sentence.slice(phrase.start, phrase.end).trim(), announced: phrase.announced, listed: list.items.length }];
+  const announcement = announcementIn(lead.text, words, patterns);
+  if (announcement === undefined || matchesList(announcement.announced, source, list)) return [];
+  return [{ offset: lead.start + announcement.start, phrase: announcement.phrase, announced: announcement.announced, listed: list.items.length }];
 };
 
 export const announcedCountMismatches = (source: string, lists: readonly BulletList[], words: CountWords): CountMismatch[] => {
   if (words.counters.length === 0) return [];
-  const context = { source, words, patterns: { phrase: phrasePattern(words), number: numberPattern(words) }, neighbours: neighboursOf(source, lists) };
+  const patterns = { phrase: phrasePattern(words), number: numberPattern(words), title: titlePattern(words) };
+  const context = { source, words, patterns, neighbours: neighboursOf(source, lists) };
   return lists.flatMap((list) => mismatchOf(context, list));
 };

package/src/chronology-rows.ts

@@ -0,0 +1,86 @@
+import { calendarUnitsOf, type CalendarUnits } from "./calendar-number.ts";
+import type { ProseDocument, Sentence } from "./plugin.ts";
+
+/**
+ * 年表の行（「1950年4月 設立」「2003年４月大阪証券取引所上場廃止。」）。日付で始まり、すぐに出来事を書く。
+ * 行は名詞で止め、文書の文体とも合わせないのが年表の書き方なので、本文の文として数えない。
+ *
+ * 日付で始まる文が 1 つだけなら本文（「2020年4月当社は…」）。続けて MIN_ROWS 以上並んだときだけ年表と読む。
+ * 行の注記（「当時主要製品は…」）が MAX_GAP 文まで挟まっても同じ年表の続きで、注記も年表の中身として数えない。
+ */
+const MIN_ROWS = 3;
+const MAX_GAP = 4;
+
+/** 日付のすぐ後ろにあれば、日付は文の一部で年表の見出しではない（2020年に、2020年4月、当社は）。 */
+const JOINS_DATE = /^[\p{Script=Hiragana}\p{P}\p{Sm}]/u;
+const DIGITS = /^[0-9０-９]+/u;
+const CALENDAR_YEAR_DIGITS = 4;
+
+type Part = { readonly digits: number; readonly rank: number; readonly end: number };
+
+/** 数（全角も）と、その後ろ（空白 1 つまで）の単位。単位が units.chained に無ければ undefined。 */
+const partAt = (text: string, at: number, units: CalendarUnits): Part | undefined => {
+  const digits = DIGITS.exec(text.slice(at))?.[0];
+  if (digits === undefined) return undefined;
+  const unitAt = text[at + digits.length] === " " ? at + digits.length + 1 : at + digits.length;
+  const rank = units.chained.findIndex((unit) => text.startsWith(unit, unitAt));
+  const unit = units.chained[rank];
+  if (unit === undefined) return undefined;
+  // 「2020年度」は年度という別の語で、年表の日付ではない。
+  if ([...units.year].some((word) => word.length > unit.length && text.startsWith(word, unitAt))) return undefined;
+  return { digits: digits.length, rank, end: unitAt + unit.length };
+};
+
+/** 前より小さい単位（年の後ろの月、月の後ろの日）が続く限り延ばした日付の終わり。 */
+const chainEnd = (text: string, last: Part, units: CalendarUnits): number => {
+  const next = partAt(text, last.end, units);
+  return next !== undefined && next.rank > last.rank ? chainEnd(text, next, units) : last.end;
+};
+
+/** 文の頭の見出しの札（「２【沿革】」）。本文に流し込んだ見出しの後ろから、最初の行が始まる。 */
+const LEADING_LABEL = /^\s*(?:[0-9０-９]+\s*)?【[^】\n]*】\s*/u;
+
+/** 文の頭（空白と見出しの札を除く）の、年から始まる日付（1950年4月、昭和56年11月1日）の終わり。年は 4 桁か元号付き。日付で始まらなければ undefined。 */
+const leadingDateEnd = (text: string, units: CalendarUnits): number | undefined => {
+  const lead = LEADING_LABEL.exec(text)?.[0].length ?? text.length - text.trimStart().length;
+  const era = units.era.find((name) => text.startsWith(name, lead));
+  const year = partAt(text, lead + (era?.length ?? 0), units);
+  if (year === undefined || year.rank !== 0 || (era === undefined && year.digits !== CALENDAR_YEAR_DIGITS)) return undefined;
+  return chainEnd(text, year, units);
+};
+
+/** 年から始まる日付で始まり、助詞も句読点も挟まずに出来事が続く文か。units は日付の単位（年月日の順）と元号。 */
+export const opensWithDateStamp = (text: string, units: CalendarUnits): boolean => {
+  const end = leadingDateEnd(text, units);
+  if (end === undefined) return false;
+  const rest = text.slice(end).trimStart();
+  return rest !== "" && !JOINS_DATE.test(rest);
+};
+
+/** heads[i] が日付で始まる文。年表と読む文の番号（MAX_GAP 文までの間を挟んで MIN_ROWS 以上続く行と、行の間の注記）。 */
+export const chronologyRowIndexes = (heads: readonly boolean[]): ReadonlySet<number> => {
+  const dated = heads.flatMap((head, index) => (head ? [index] : []));
+  const clusters = dated.reduce<number[][]>((acc, index) => {
+    const cluster = acc.at(-1);
+    const previous = cluster?.at(-1);
+    if (cluster !== undefined && previous !== undefined && index - previous - 1 <= MAX_GAP) cluster.push(index);
+    else acc.push([index]);
+    return acc;
+  }, []);
+  return new Set(
+    clusters
+      .filter((cluster) => cluster.length >= MIN_ROWS)
+      .flatMap((cluster) => Array.from({ length: (cluster.at(-1) ?? 0) - (cluster[0] ?? 0) + 1 }, (_, offset) => (cluster[0] ?? 0) + offset)),
+  );
+};
+
+/** 主題の「は」。年表の行は出来事だけを書き、主題を立てない。立てた文（2021年売上高は110億円です。）は日付で始まっても本文。 */
+const TOPIC = "は";
+const hasTopic = (sentence: Sentence): boolean => (sentence.tokens ?? []).some((token) => token.surface === TOPIC && token.pos === "ADP");
+
+/** 文書の中の、年表の行の文。 */
+export const chronologyRows = (doc: ProseDocument): ReadonlySet<Sentence> => {
+  const units = calendarUnitsOf(doc);
+  const rows = chronologyRowIndexes(doc.sentences.map((sentence) => opensWithDateStamp(sentence.text, units) && !hasTopic(sentence)));
+  return new Set(doc.sentences.filter((_, index) => rows.has(index)));
+};

package/src/company-name-run.ts

@@ -0,0 +1,37 @@
+import { escapeRegExp } from "./orthography.ts";
+import type { Span } from "./plugin.ts";
+
+/** 会社の名前に使う字（漢字・片仮名・英数字）の続き。かなや句読点で名前は切れる。 */
+const NAME_RUN = /[\p{Script=Han}ァ-ヺーA-Za-zＡ-Ｚａ-ｚ0-9０-９&＆・]+/gu;
+
+/** 漢字か片仮名を含む形（株式会社、㈱、(株)）。英字だけの形は日本語の名前の目印にならない。 */
+const NOT_LATIN = /[^\p{Script=Latin}\p{P}\s]/u;
+
+const formPattern = (forms: readonly string[]): RegExp =>
+  new RegExp(
+    [...forms]
+      .sort((a, b) => b.length - a.length)
+      .map(escapeRegExp)
+      .join("|"),
+    "gu",
+  );
+
+/** at を含むか、at で接する名前の字の続き。 */
+const runAround = (runs: readonly Span[], at: number): Span | undefined => runs.find((run) => run.start <= at && at <= run.end);
+
+/**
+ * text の中の、日本の会社の形（語彙表 company-form）とその隣の名前の範囲（関東珪曹硝子㈱、株式会社ADEKA）。
+ * 名前は書き手が選べない字で書かれるので、表記のゆれを数える語に入れない。形の前は名前の字が続くかぎり、形の後ろも同じ。
+ * 名前の字の続きを一度だけ求め、形の両端をそれに合わせて伸ばす。
+ */
+export const japaneseCompanyNameSpans = (text: string, forms: readonly string[]): Span[] => {
+  const japanese = forms.filter((form) => NOT_LATIN.test(form));
+  if (japanese.length === 0) return [];
+  const found = [...text.matchAll(formPattern(japanese))];
+  if (found.length === 0) return [];
+  const runs = [...text.matchAll(NAME_RUN)].map((match) => ({ start: match.index, end: match.index + match[0].length }));
+  return found.map((match) => {
+    const end = match.index + match[0].length;
+    return { start: runAround(runs, match.index)?.start ?? match.index, end: runAround(runs, end)?.end ?? end };
+  });
+};

package/src/compound-head.ts

@@ -0,0 +1,25 @@
+import type { Token } from "./plugin.ts";
+
+const OPENING = new Set(["（", "("]);
+const CLOSING = new Set(["）", ")"]);
+
+const isTouching = (left: Token | undefined, right: Token | undefined): boolean =>
+  left !== undefined && right !== undefined && left.span.end === right.span.start;
+
+const isNounBefore = (token: Token, next: Token | undefined, suffixes: ReadonlySet<string>): next is Token =>
+  next?.pos === "NOUN" && isTouching(token, next) && !suffixes.has(next.surface);
+
+/** A noun alone in brackets that close onto a noun (卒業（見込）証明書): the brackets mark it optional inside one compound. */
+const isBracketedInCompound = (token: Token, tokens: readonly Token[], at: number, suffixes: ReadonlySet<string>): boolean => {
+  const [opening, closing] = [tokens[at - 1], tokens[at + 1]];
+  if (opening === undefined || closing === undefined) return false;
+  if (!OPENING.has(opening.surface) || !CLOSING.has(closing.surface) || !isTouching(opening, token) || !isTouching(token, closing)) return false;
+  return isNounBefore(closing, tokens[at + 2], suffixes);
+};
+
+/**
+ * Whether `token`, read at `at` in `tokens`, is a noun written onto the noun after it (取扱事業者), so official Japanese may
+ * drop its okurigana. A listed phrase suffix (割当て等) does not make a compound. `token` may be tokens[at] read as a noun.
+ */
+export const isCompoundHead = (token: Token, tokens: readonly Token[], at: number, suffixes: ReadonlySet<string>): boolean =>
+  token.pos === "NOUN" && (isNounBefore(token, tokens[at + 1], suffixes) || isBracketedInCompound(token, tokens, at, suffixes));

package/src/date-format.ts

@@ -115,9 +115,48 @@ const LINE_HEAD = /(?:^|\|)[\s>*_+-]*(?:\d+[.)]\s+)?$/u;
 /** 日付が行の頭（箇条書きの項目や表の升の頭）にあるか。 */
 export const opensLine = (text: string, offset: number): boolean => LINE_HEAD.test(text.slice(text.lastIndexOf("\n", offset - 1) + 1, offset));
 
+/** 刻印のラベルと日付の間に来る字（更新日：、Last updated: ）。 */
+const STAMP_GAP = /[\s:：]/u;
+/** 末尾の、ラベルと日付の間の字を外した文字列。 */
+const withoutGap = (text: string): string => {
+  const chars = text.split("");
+  return chars.slice(0, chars.findLastIndex((char) => !STAMP_GAP.test(char)) + 1).join("");
+};
+
+/** 刻印のラベルの前に来てよい字。行の頭か、ページの部品を区切る空白と縦線（ページID：0014616 更新日：）。 */
+const STAMP_LEAD = /[\s|｜]/u;
+
+/**
+ * text が刻印のラベル word で終わり、ラベルが行の頭か区切りの後ろから始まる。文の中の語（この日付は公開：、The date:、
+ * 1Updated）は刻印のラベルではない。語彙表に書いたとおりの字で照らす。
+ */
+const endsWithLabel = (text: string, word: string): boolean => {
+  const start = text.length - word.length;
+  if (word === "" || start < 0 || !text.endsWith(word)) return false;
+  return start === 0 || STAMP_LEAD.test(text.charAt(start - 1));
+};
+
+/**
+ * 日付のすぐ前が、ページの更新日・公開日の刻印のラベル（更新日：2026年10月13日、Last updated: 2 October 2026）。
+ * 刻印は CMS が付ける付帯情報で、本文の日付の書き方（令和8年…）とは別の書き方をしてよい。
+ */
+export const stampedDate = (text: string, offset: number, stampLabels: readonly string[]): boolean => {
+  const before = withoutGap(text.slice(text.lastIndexOf("\n", offset - 1) + 1, offset));
+  return stampLabels.some((label) => endsWithLabel(before, label));
+};
+
+type DateGroup = "head" | "body" | "stamp";
+
+const groupOf = (text: string, date: WrittenDate, stampLabels: readonly string[]): DateGroup => {
+  if (stampedDate(text, date.offset, stampLabels)) return "stamp";
+  return opensLine(text, date.offset) ? "head" : "body";
+};
+
+const GROUP_ORDER: readonly DateGroup[] = ["head", "body", "stamp"];
+
 /**
- * 行の頭の日付と、文の中の日付を分ける。予定表を 2026-10-16 で並べ、文では 14 October 2026 と書くのは使い分けで、混ざりではない。
- * 書き方はそれぞれの組の中でだけ比べる。
+ * 行の頭の日付と、文の中の日付と、更新日・公開日の刻印の日付を分ける。予定表を 2026-10-16 で並べ、文では 14 October 2026 と
+ * 書くのは使い分けで、混ざりではない。刻印のラベルは言語パッケージの語彙表（date-stamp-label）が渡す。書き方はそれぞれの組の中でだけ比べる。
  */
-export const dateGroups = (text: string, dates: readonly WrittenDate[]): WrittenDate[][] =>
-  [true, false].map((head) => dates.filter((date) => opensLine(text, date.offset) === head)).filter((group) => group.length > 0);
+export const dateGroups = (text: string, dates: readonly WrittenDate[], stampLabels: readonly string[] = []): WrittenDate[][] =>
+  GROUP_ORDER.map((group) => dates.filter((date) => groupOf(text, date, stampLabels) === group)).filter((group) => group.length > 0);

package/src/derived/count-per-period.ts

@@ -0,0 +1,28 @@
+import type { Span } from "../plugin.ts";
+import { overlapsAny, type SpanIndex } from "../compare/spans.ts";
+import type { DurationUnit } from "./date-arithmetic.ts";
+
+/** A word that names a period (週, 毎月, a week), where it is written beside the count, and the period's unit. */
+export type PeriodWord = { readonly word: string; readonly position: "before" | "after"; readonly unit: DurationUnit };
+
+/** The period words, and the named schedules in the document (週休2日制, 4週8休). */
+export type PerPeriodWords = { readonly periods: readonly PeriodWord[]; readonly schedules: SpanIndex };
+
+const UNIT_ORDER: readonly DurationUnit[] = ["day", "week", "month", "year"];
+
+/** A number or a counter just before the period word: 1年3か月 and 3か月10日 are one length written in two units, not a count per year or month. */
+const COUNTED = /[0-9０-９〇一二三四五六七八九十百千かヵヶカケ箇個]$/u;
+
+const endsWithPeriod = (before: string, word: string): boolean => before.endsWith(word) && !COUNTED.test(before.slice(0, before.length - word.length));
+
+const isBeside = (period: PeriodWord, before: string, after: string): boolean =>
+  period.position === "before" ? endsWithPeriod(before, period.word) : after.startsWith(period.word);
+
+/**
+ * A number with a unit of time that is not a length to add to a date: a count in each period (週3日、月10日、3 days a week) or a
+ * number inside the name of a work schedule (週休2日制の2日、4週8休の4週). A count is in a unit smaller than its period: 毎年1年間 is a
+ * year's length. before and after are the text next to the count, lower-cased.
+ */
+export const isCountPerPeriod = (count: Span & { readonly unit: DurationUnit }, before: string, after: string, words: PerPeriodWords): boolean =>
+  overlapsAny(words.schedules, count) ||
+  words.periods.some((period) => UNIT_ORDER.indexOf(count.unit) < UNIT_ORDER.indexOf(period.unit) && isBeside(period, before, after));

package/src/detectors/acronym-context.ts

@@ -6,7 +6,7 @@ import { loneNumeralSpans, nameNumeralSpans } from "./name-numeral.ts";
 import { placeholderSpans } from "./placeholder.ts";
 import { numeralWordSpans } from "./numeral-word.ts";
 import { seriesLabelSpans } from "./series-label.ts";
-import { oneOf } from "./acronym-name.ts";
+import { nameSpansOf, oneOf } from "./acronym-name.ts";
 
 /**
  * 大文字の語が略語ではなく、決まった書き方の一部として読める所（3:30 PM、1pm ET、USD 1,000、Kansas City, MO 64108、Fort Lauderdale FL 33304）。
@@ -114,3 +114,32 @@ export const notAcronymSpansOf = (words: NotationWords): NotAcronymSpans => {
     ...numeralWordSpans(text),
   ];
 };
+
+/**
+ * 略語として数えない範囲（書き方の範囲と、名前の中の範囲）を、言語パッケージの語彙表から組み立てる。wordsOf は語彙表の id から語を返す。
+ */
+export const lexiconNotationOf = (wordsOf: (id: string) => string[]): NotAcronymSpans => {
+  const notation = notAcronymSpansOf({
+    meridiem: wordsOf("meridiem"),
+    timeZones: wordsOf("time-zone"),
+    currencies: wordsOf("currency-code"),
+    usStates: wordsOf("us-state-code"),
+    emphasis: wordsOf("emphasis-word"),
+    divisions: wordsOf("numbered-division"),
+    abbreviatedLabels: wordsOf("abbreviated-label"),
+    honorifics: wordsOf("honorific"),
+    titles: wordsOf("name-title"),
+    dateTimeUnits: wordsOf("date-time-unit"),
+  });
+  const names = nameSpansOf({
+    legalForms: wordsOf("legal-form"),
+    companyForms: wordsOf("company-form"),
+    determiners: wordsOf("name-determiner"),
+    citationSeries: wordsOf("citation-series"),
+    carriers: wordsOf("carrier-name"),
+    namePrefixes: wordsOf("name-prefix"),
+    streetSuffixes: wordsOf("street-suffix"),
+    capitalPhrases: wordsOf("capital-phrase"),
+  });
+  return (text) => [...notation(text), ...names(text)];
+};