chaffjs 0.33.0 → 0.35.0

package/rules/reference-number-variant.yaml

@@ -34,7 +34,7 @@ levels: { strict: error, normal: warning, relaxed: warning }
 options:
   listed_kinds:
     kind: words
-    default: [item]
+    default: [item, model]
     about:
       ja: 文書が多くを並べる番号の種類（reference-label の group）。この種類の、語の後ろや表にある番号どうしは比べず、語の無い番号だけを比べる
       en: Kinds of number a document lists many of (reference-label groups). Two labelled or tabled numbers of such a kind are never compared; only one with no label is
@@ -77,5 +77,5 @@ example:
       When you call, please give your booking number, MN-48215.
 
 not_flagged:
-  ja: 「予約番号」「受付番号」「予約確認番号」「お問い合わせ番号」「社員番号」「学籍番号」「発注番号」「見積番号」「請求書番号」「患者番号」「契約番号」「登録番号」「口座番号」「証券番号」のような語のすぐ後ろ（間は空白と「：」「、」や開き括弧だけ）にある、数字を4つ以上含む英数字の並びだけを番号と見ます。発注番号は取引先の番号を書き写すこともありますが、同じ種類の語の番号どうしで隣り合う二文字だけが入れ違ったものしか指さないので、別の注文の番号は指しません。「原契約番号」「基本契約番号」「旧契約番号」「変更契約番号」「親契約番号」は別の契約の番号を引く語なので、文書自身の「契約番号」とは比べません。「登録番号」「受講番号」は参加者の登録の番号、「申込番号」は申込みの番号として、互いに比べません。「振込先口座番号」「振込元口座番号」は振込の相手の口座の番号を書く語なので、口座自身の「口座番号」とは比べません。「契約者番号」は契約者その人の番号で、証券番号とは見ません。語の無い番号（下に書く品番の形のものを除く）、種類の違う番号（学籍番号と社員番号、予約番号と受付番号、請求書番号と注文番号、見積番号と注文番号や請求書番号、登録番号と申込番号）、一文字だけ違う番号、離れた文字の入れ違い、二か所以上入れ違った番号は指しません。自動車のナンバー（ひばり野 330 ね 48-15）の形に合う並びは、語が「登録番号」でも自動車のナンバーとして読みます。ナンバーだけは、文書が一台の車のことを書いているとき（その車のナンバーを「登録番号：」のような語と番号だけの行に一つだけ書き、ほかのナンバーは一つだけで、その語が文の初めにあるとき。「代車の登録番号」のように語の前に語があれば別の車と見ます）に限って、地名・分類番号・かなが同じで一連番号が一文字だけ違うものも指します。「ナンバー」だけの語や英語の「Registration」だけの語は、ナンバーの語として読みません。「品番」「商品コード」「品目コード」は商品の番号の語です。表の行や列の見出しにこの語を書いた升の品番も、語の後ろの品番と同じに読みます。語の無い品番（「GP-0521の替芯」）は、英字と「-」と数字4つ以上の形（GP-0521）のときだけ、語の後ろか表にある品番のちょうど一つと隣り合う二文字だけが入れ違っていれば指します。その書き方の品番が文書のどこかで語の後ろか表にあれば、別の商品の品番と見て指しません（カタログの表に並ぶ AB-1234 と AB-1243 は二つの商品です）。語の後ろや表にある品番どうしも、別の商品の品番として比べません（この扱いをする種類は listed_kinds で決めます）。二つ以上の品番のどれとも読めるもの、英字や「-」の無い番号（48251）も指しません。「会員番号」「会員ID」の会員の番号と、「お客様番号」の番号は、別の番号になり得るので比べません。語のすぐ後ろの番号を「HM 5520 8137」のように空白一つずつで区切って書いたときは、続く並びがどれも4文字以上の大文字と数字で数字を含む間を一つの番号と読み、行の終わりや、語（「の方」「2名」）の前で止めます。
-  en: "Only letters and digits right after a label (booking number, reservation number, confirmation number, reference number, employee number, student number, PO number, quote or estimate number, invoice number, patient number, contract or agreement number, registration number, account number, policy number), with nothing but spaces, a colon, a comma or an opening bracket between, are read, and only when they hold four digits or more. A PO number may be the buyer's, copied from another document, but only two numbers of one kind that differ by two neighbours swapped are reported, so a different order's number is not. An original, master, former, amended or parent contract number (and an amendment number) cites another contract, so it is never compared with the document's own contract number. A registration number labels an attendee's registration and an application number an application, so the two are never compared. A payee's, beneficiary's, payer's or sender's account number labels the other side of a transfer, so it is never compared with the account's own account number; a policyholder number is not read as a policy number. Unlabelled codes (but for item codes, below), numbers of different kinds (a student number and an employee number, a booking number and an order number, an invoice number and an order number, a quote number and an order or invoice number, a registration number and an application number), numbers that differ in one character, swaps of characters that are not neighbours and numbers with more than one swap are not reported. A bare quote is not read as a label, since it is also a verb (quote your PO number). A plate number, number plate or licence plate is a vehicle's and is never compared with a registration number; a bare Registration label is not read as a plate, since an attendee's registration is written so too. An item code, item no., SKU or product code labels an item; a code in a table under such a label, in its row or its column, is read as if written after it. A code with no label (Refills for GP-0521) is reported only in the shape letters, a hyphen and four digits or more, and only when it is exactly one labelled or tabled code with two neighbours swapped. When the document labels or tables that writing itself anywhere, it is another item and is not reported (a catalog's AB-1234 and AB-1243 are two items), and two labelled or tabled item codes are never compared with each other (listed_kinds names the kinds read so); nor is a code two labelled codes swap to, or a number with no letters or hyphen (48251). A member number or member ID and a customer number may be different numbers, so they are never compared. A number written in groups one space apart (HM 5520 8137) is read as one while each further group is four or more capitals and digits holding a digit, stopping at the line's end or before a word or a short count (expires, 100 copies)."
+  ja: 「予約番号」「受付番号」「予約確認番号」「お問い合わせ番号」「社員番号」「学籍番号」「発注番号」「見積番号」「請求書番号」「患者番号」「契約番号」「登録番号」「口座番号」「証券番号」のような語のすぐ後ろ（間は空白と「：」「、」や開き括弧だけ）にある、数字を4つ以上含む英数字の並びだけを番号と見ます。発注番号は取引先の番号を書き写すこともありますが、同じ種類の語の番号どうしで隣り合う二文字だけが入れ違ったものしか指さないので、別の注文の番号は指しません。「原契約番号」「基本契約番号」「旧契約番号」「変更契約番号」「親契約番号」は別の契約の番号を引く語なので、文書自身の「契約番号」とは比べません。「登録番号」「受講番号」は参加者の登録の番号、「申込番号」は申込みの番号として、互いに比べません。「振込先口座番号」「振込元口座番号」は振込の相手の口座の番号を書く語なので、口座自身の「口座番号」とは比べません。「契約者番号」は契約者その人の番号で、証券番号とは見ません。語の無い番号（下に書く品番の形のものを除く）、種類の違う番号（学籍番号と社員番号、予約番号と受付番号、請求書番号と注文番号、見積番号と注文番号や請求書番号、登録番号と申込番号）、一文字だけ違う番号、離れた文字の入れ違い、二か所以上入れ違った番号は指しません。自動車のナンバー（ひばり野 330 ね 48-15）の形に合う並びは、語が「登録番号」でも自動車のナンバーとして読みます。ナンバーだけは、文書が一台の車のことを書いているとき（その車のナンバーを「登録番号：」のような語と番号だけの行に一つだけ書き、ほかのナンバーは一つだけで、その語が文の初めにあるとき。「代車の登録番号」のように語の前に語があれば別の車と見ます）に限って、地名・分類番号・かなが同じで一連番号が一文字だけ違うものも指します。「ナンバー」だけの語や英語の「Registration」だけの語は、ナンバーの語として読みません。「品番」「商品コード」「品目コード」は商品の番号の語です。表の行や列の見出しにこの語を書いた升の品番も、語の後ろの品番と同じに読みます。語の無い品番（「GP-0521の替芯」）は、英字と「-」と数字4つ以上の形（GP-0521）のときだけ、語の後ろか表にある品番のちょうど一つと隣り合う二文字だけが入れ違っていれば指します。その書き方の品番が文書のどこかで語の後ろか表にあれば、別の商品の品番と見て指しません（カタログの表に並ぶ AB-1234 と AB-1243 は二つの商品です）。語の後ろや表にある品番どうしも、別の商品の品番として比べません（この扱いをする種類は listed_kinds で決めます）。二つ以上の品番のどれとも読めるもの、英字や「-」の無い番号（48251）も指しません。「会員番号」「会員ID」の会員の番号と、「お客様番号」の番号は、別の番号になり得るので比べません。語のすぐ後ろの番号を「HM 5520 8137」のように空白一つずつで区切って書いたときは、続く並びがどれも4文字以上の大文字と数字で数字を含む間を一つの番号と読み、行の終わりや、語（「の方」「2名」）の前で止めます。「型番」は製品の型番の語で、品番と同じく、語の後ろや表にある型番どうしは比べません。製品の文書（回収のお知らせや保証書）が自分の製品として名指す番号（題名にある番号、「型番：」「商品コード：」のような語と番号だけの行の番号、表で型番や品番の語を書いた升の番号）がちょうど一つのときに限り、「-」の前に英字が二つ以上あり、数字が二つ以上の短い番号（NH-805、FT-38）も読み、文書に一度だけ書いた、その番号の隣り合う二文字が入れ違った番号（NH-850）を指します。そう名指す番号が二つ以上ある文書（カタログ）、表にある番号、二度以上書いた番号、その番号と同じ行にある番号（「NH-805 と NH-850」）、「予約番号」のような別の種類の語の後ろの番号、英字一つの番号（A-12）は指しません。
+  en: "Only letters and digits right after a label (booking number, reservation number, confirmation number, reference number, employee number, student number, PO number, quote or estimate number, invoice number, patient number, contract or agreement number, registration number, account number, policy number), with nothing but spaces, a colon, a comma or an opening bracket between, are read, and only when they hold four digits or more. A PO number may be the buyer's, copied from another document, but only two numbers of one kind that differ by two neighbours swapped are reported, so a different order's number is not. An original, master, former, amended or parent contract number (and an amendment number) cites another contract, so it is never compared with the document's own contract number. A registration number labels an attendee's registration and an application number an application, so the two are never compared. A payee's, beneficiary's, payer's or sender's account number labels the other side of a transfer, so it is never compared with the account's own account number; a policyholder number is not read as a policy number. Unlabelled codes (but for item codes, below), numbers of different kinds (a student number and an employee number, a booking number and an order number, an invoice number and an order number, a quote number and an order or invoice number, a registration number and an application number), numbers that differ in one character, swaps of characters that are not neighbours and numbers with more than one swap are not reported. A bare quote is not read as a label, since it is also a verb (quote your PO number). A plate number, number plate or licence plate is a vehicle's and is never compared with a registration number; a bare Registration label is not read as a plate, since an attendee's registration is written so too. An item code, item no., SKU or product code labels an item; a code in a table under such a label, in its row or its column, is read as if written after it. A code with no label (Refills for GP-0521) is reported only in the shape letters, a hyphen and four digits or more, and only when it is exactly one labelled or tabled code with two neighbours swapped. When the document labels or tables that writing itself anywhere, it is another item and is not reported (a catalog's AB-1234 and AB-1243 are two items), and two labelled or tabled item codes are never compared with each other (listed_kinds names the kinds read so); nor is a code two labelled codes swap to, or a number with no letters or hyphen (48251). A member number or member ID and a customer number may be different numbers, so they are never compared. A number written in groups one space apart (HM 5520 8137) is read as one while each further group is four or more capitals and digits holding a digit, stopping at the line's end or before a word or a short count (expires, 100 copies). A model, model number or model no. labels a product's model, and, as with item codes, two labelled or tabled models are never compared. When a product document (a recall, a warranty) names exactly one code as its own (in its title, on a line holding only a model or item label and the code, as Model: SH-710, or in a table under such a label), a shorter code is read too (two letters or more before a hyphen, and two digits or more: SH-710, FT-38), and a code written once that is that code with two neighbours swapped (SH-701) is reported. Not when the document names two codes so (a catalog), nor a code in a table, one written twice or more, one on a line that also names the document's code (the SH-710 replaces the SH-701), one after a label of another kind (booking number), or one with a single letter (A-12)."

package/rules/reference-title-mismatch.yaml

@@ -74,8 +74,8 @@ example:
       The fee is monthly.
 
 not_flagged:
-  ja: 参照先が見出しを持たないとき、参照先が一つに決まらないとき、他の文書の条（民法第709条）、括弧の中が数字を含むか「前述」「参照」のような語のときは見ません。
-  en: References whose target has no heading or cannot be told apart, references to another document, and brackets holding a number or a word like "above" or "see" are left alone.
+  ja: 参照先が見出しを持たないとき、参照先が一つに決まらないとき、他の文書の条（民法第709条）、括弧の中が数字を含むか「前述」「参照」のような語のとき、句点で終わる断り（「第七項を除く。」）のときは見ません。
+  en: References whose target has no heading or cannot be told apart, references to another document, brackets holding a number or a word like "above" or "see", and brackets closed by a Japanese full stop (a note on the scope, 「第七項を除く。」) are left alone.
 rewrite:
   depth: light
   ja:

package/rules/repeated-sentence-ending.yaml

@@ -2,6 +2,7 @@ id: repeated-sentence-ending
 layer: L3
 status: stable
 how_to_find: ending-run
+word_list: parallel-definition
 requires: [pos]
 languages: [ja]
 severity: info
@@ -40,8 +41,8 @@ example:
       この機能は必要で、設定も簡単です。費用はかかりません。
 
 not_flagged:
-  ja: 段落をまたいだ文は続きと見ません。助動詞で終わらない文（体言止め、言い切りの動詞）は比べず、そこで続きが切れます。動詞が違えば（読みました、書きました）同じ文末とは見ません。
-  en: Sentences in different paragraphs are not a run. A sentence that does not end with an auxiliary (a noun, a bare verb) is not compared and breaks the run. Different verbs (読みました, 書きました) are different endings.
+  ja: 段落をまたいだ文は続きと見ません。助動詞で終わらない文（体言止め、言い切りの動詞）は比べず、そこで続きが切れます。動詞が違えば（読みました、書きました）同じ文末とは見ません。違う語を同じ型で定義する文の並び（台風は〜を指します。ハリケーンは〜を指します。）は、型をそろえたものなので指しません。
+  en: Sentences in different paragraphs are not a run. A sentence that does not end with an auxiliary (a noun, a bare verb) is not compared and breaks the run. Different verbs (読みました, 書きました) are different endings. Sentences that each define a different term in the same frame (台風は〜を指します。ハリケーンは〜を指します。) share their ending on purpose and are not reported.
 level_meaning:
   ja: 同じ文末の文が {limit} 文続くまで
   en: up to {limit} sentences in a row with the same ending

package/rules/request-without-deadline.yaml

@@ -60,8 +60,8 @@ example:
       I have no other questions.
 
 not_flagged:
-  ja: 確認・返信・提出のように、済んだかどうかが後で分かる動作を頼む文だけを見ます。「ご了承ください」のような心構えの依頼と、「ご不明な点があれば、ご連絡ください」のような条件付きの申し出と、「ご質問はメールでお送りください」のような質問を受け付ける申し出は見ません。期限か担当が、その文か次の文にあれば指しません。ビジネスの文書でだけ動きます。
-  en: Only requests for an action whose completion can be checked (review, reply, send) are read. Courtesy requests, conditional offers ("If you have questions, let me know") and open offers ("Please send any questions to me") are not. A deadline or owner in the same or the next sentence is enough. Business documents only.
+  ja: 確認・返信・提出のように、済んだかどうかが後で分かる動作を頼む文だけを見ます。「ご了承ください」のような心構えの依頼、「ご不明な点があれば、ご連絡ください」のような条件付きの申し出、「ご質問はメールでお送りください」のような質問を受け付ける申し出、「ご相談ください」「お越しください」のような誘い、連絡先の行（「電話：」）と同じ文の依頼は見ません。期限か担当が、その文か次の文にあれば指しません。「ご提出いただく前に」「送信後、」のように、いつするかを依頼の文が言っていれば期限と読みます。見出しが期限を言っていれば（「見積提出期限：…」「【随時受付】」）、その下の依頼はその期限を受け継ぎます。ビジネスの文書でだけ動きます。
+  en: Only requests for an action whose completion can be checked (review, reply, send) are read. Courtesy requests, conditional offers ("If you have questions, let me know"), open offers ("Please send any questions to me"), invitations ("Please come and register") and a request on a contact line (a "Fax" or "Phone" label and its number) are not. A deadline or owner in the same or the next sentence is enough; so is a timing in the request itself ("after you pay"), or a heading above it that names the deadline. Business documents only.
 rewrite:
   depth: light
   ja:

package/rules/requirement-smell.yaml

@@ -74,5 +74,5 @@ example:
     config: { genre: technical/spec }
 
 not_flagged:
-  ja: 要求の文でない文（説明や背景）、法令、ブログやビジネス文書は見ません。語彙表にない言い方は指しません。文書が定めた名前の「等」（以下「委託先等」という、銀行等（…をいう。）、定義の号の頭の語）と、監査等委員会のように後ろへ語が続く「等」は、列挙を閉じているので指しません。
-  en: Sentences that state no requirement (background, explanation), statutes, and blogs and business documents are not checked. Phrases not on chaff's lists are not reported. An open-ended word inside a name the document defines (a quoted term, or one defined in the brackets after it) is not reported.
+  ja: 要求の文でない文（説明や背景）、法令、ブログやビジネス文書は見ません。語彙表にない言い方は指しません。文書が定めた名前の「等」（以下「委託先等」という、銀行等（…をいう。）、定義の号の頭の語）と、監査等委員会のように後ろへ語が続く「等」は、列挙を閉じているので指しません。英語の as soon as possible は、同じ文に日数の期限（no later than two days after）があれば、期限が決まっているので指しません。
+  en: Sentences that state no requirement (background, explanation), statutes, and blogs and business documents are not checked. Phrases not on chaff's lists are not reported. An open-ended word inside a name the document defines (a quoted term, or one defined in the brackets after it) is not reported. "As soon as possible" followed in the same sentence by a limit in numbers ("but in any event no later than two days after") is bounded, and not reported.

package/rules/sentence-rhythm.yaml

@@ -55,8 +55,8 @@ example:
       Today we look at the new tool. Open the settings. The gear icon at the top right opens a list of everything you can change, so pick the option you want there and switch it on. Then save. That is the first part done. Next, invite the rest of the team from the page on the left.
 
 not_flagged:
-  ja: 文が 8 文より少ない文書は、ばらつきが当てにならないので測りません。
-  en: A document with fewer than 8 sentences is not measured, because the spread means little.
+  ja: 箇条書きの項目は数えません（揃えて書くのが正しい形です）。地の文が 8 文より少ない文書は、ばらつきが当てにならないので測りません。
+  en: List items are not counted, since a list is written alike on purpose. Prose of fewer than 8 sentences is not measured, because the spread means little.
 level_meaning:
   ja: 文の長さのばらつきが {limit}% 未満なら指摘
   en: reported when sentence length varies by less than {limit}%

package/rules/title-case-consistency.yaml

@@ -10,8 +10,8 @@ name:
   en: Heading capitalisation is inconsistent
 
 why:
-  ja: Title Case と sentence case のどちらが正しいかは決めません。1 つの文書で混ざっていると、見出しの階層が変わったように見えます。文書の題名（先頭にある深さ 1 の見出しが 1 つだけのとき）は名前なので比べません。節の見出しが同数に割れたときだけ、題名の流儀に合わせます。頭の番号の札（Section 3. / Day 1:）と、曜日・月の名（どちらの流儀でも大文字）は、どちらの流儀の証拠にも数えません。
-  en: Neither Title Case nor sentence case is wrong. Mixed within one document, the headings look like they change level. The document's title (a single top-level heading that opens it) is a name and is not compared; when the section headings split evenly, the title's style decides. A leading label (Section 3., Day 1:) and the names of weekdays and months, capitalised in either style, count as evidence for neither.
+  ja: Title Case と sentence case のどちらが正しいかは決めません。1 つの文書で混ざっていると、見出しの階層が変わったように見えます。文書の題名（先頭にある深さ 1 の見出しが 1 つだけのとき）は名前なので比べません。節の見出しが同数に割れたときだけ、題名の流儀に合わせます。頭の番号の札（Section 3. / Day 1:）と、曜日・月の名と、本文が文の途中で大文字で書く名前（どれもどちらの流儀でも大文字）は、どちらの流儀の証拠にも数えません。
+  en: Neither Title Case nor sentence case is wrong. Mixed within one document, the headings look like they change level. The document's title (a single top-level heading that opens it) is a name and is not compared; when the section headings split evenly, the title's style decides. A leading label (Section 3., Day 1:), the names of weekdays and months, and the names the body itself capitalises mid-sentence, all capitalised in either style, count as evidence for neither.
 
 message:
   ja: この見出しだけ他と大文字化の流儀が違います（文書の中で {count} 個）

package/rules/toki-as-condition.yaml

@@ -0,0 +1,71 @@
+id: toki-as-condition
+layer: L3
+status: stable
+how_to_find: condition-toki
+word_list: condition-toki
+extra_word_lists: [condition-follower]
+requires: [pos]
+languages: [ja]
+severity: info
+
+name:
+  ja: 条件を言う「時」
+  en: 時 written for a condition (法令用語の「とき」)
+
+why:
+  ja: 法令の文では、「時」は時点（相続開始の時から）、「とき」は条件（認定を受けたときは）を言います。「認定を受けた時は」と書くと、読み手は「受けた時点で」の意味か「受けた場合に」の意味かを考えます。契約書や規程は法令の書き方にそろえるので、同じ使い分けをします。動詞や助動詞で終わる節の後ろの「時」に、「は」「には」「も」が続くときだけ指します。
+  en: Japanese legal drafting writes 時 for a point in time (相続開始の時から, "from the time the succession opens") and とき for a condition (認定を受けたときは, "if the approval is given"). With 認定を受けた時は the reader has to decide whether a moment or a condition is meant. Contracts and internal rules follow the statutes' usage. chaff reports 時 only after a clause that ends in a verb or an auxiliary and before は, には or も.
+
+message:
+  ja: 条件を言うなら「{matched}」は「{preferred}」と書きます
+  en: 'For a condition, legal Japanese writes "{matched}" as "{preferred}"'
+
+how_to_fix:
+  ja: 条件なら「とき」にしてください（認定を受けた時は → 認定を受けたときは）。時点を言うなら「時から」「時に」のように書けば、時点と読めます。
+  en: For a condition, write とき (認定を受けた時は → 認定を受けたときは). For a point in time, write 時から or 時に so that it reads as one.
+
+placeholders:
+  matched:
+    ja: 見つけた語
+    en: the word found
+  preferred:
+    ja: 条件を言う書き方
+    en: the word for a condition
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [legal, docs, academic, literature, speech]
+off_for:
+  docs: "The 時 / とき split is a convention of legal drafting: outside it, 時は for a condition is not a slip."
+  academic: "The 時 / とき split is a convention of legal drafting: outside it, 時は for a condition is not a slip."
+  literature: "The 時 / とき split is a convention of legal drafting: outside it, 時は for a condition is not a slip."
+  speech: "The 時 / とき split is a convention of legal drafting: outside it, 時は for a condition is not a slip."
+
+group: wording
+summary:
+  ja: 「認定を受けた時は」のように、条件を「とき」でなく「時」で書いた所
+  en: 時 written for a condition (受けた時は) where legal Japanese writes とき
+example:
+  ja:
+    config: { genre: legal/contract }
+    before: |
+      第5条　乙は、許可の取消しを受けた時は、直ちに甲に通知しなければならない。
+    after: |
+      第5条　乙は、許可の取消しを受けたときは、直ちに甲に通知しなければならない。
+
+not_flagged:
+  ja: 時点を言う「時」（相続開始の時から、死亡した時に、契約の終了の時まで）、名詞や「その」「ある」の後ろの「時」（事故の時は、その時は）、「時効」「時間」「同時」「随時」「臨時」「当時」「時点」「時期」のような語、鉤括弧で引いた中は指しません。法務のジャンルだけで動きます。
+  en: 時 for a point in time (相続開始の時から, 死亡した時に, 契約の終了の時まで), 時 after a noun or after その and ある (事故の時は, その時は), words such as 時効, 時間, 同時, 随時, 臨時, 当時, 時点 and 時期, and anything quoted in 「」 are not reported. Only the legal genres run this rule.
+rewrite:
+  depth: light
+  ja:
+    direction: 条件を言う「時」を「とき」に替えてください。替えるのはその一語だけです。
+    pairs:
+      - before: 乙は、許可の取消しを受けた時は、直ちに甲に通知しなければならない。
+        after: 乙は、許可の取消しを受けたときは、直ちに甲に通知しなければならない。
+      - before: 支払期日を過ぎる時には、年三パーセントの遅延損害金を支払う。
+        after: 支払期日を過ぎるときには、年三パーセントの遅延損害金を支払う。
+    keep:
+      - 条の番号と中身
+    avoid:
+      - 時点を言う「時」（時から、時まで、時に）まで替える

package/rules/total-mismatch.yaml

@@ -10,8 +10,8 @@ name:
   en: A total that is not the sum of its items
 
 why:
-  ja: 見積や請求の「合計」が、上に並べた金額の和と合わないと、読み手はどちらが正しいのかを計算し直すことになります。行を足したり消したりしたあとに、合計だけ直し忘れると起きます。箇条書きか表で、合計の語（合計・小計）で始まる行を、同じ単位で同じ列の金額の和と比べます。表の最初の列の見出しか、合計の行が数を書いた列の見出しが名指す語を付けた合計（見出しが「控除項目」の表の「控除合計」、「単位数」の列の「修得単位合計」）も合計の行と読みます。合計が足す期間を頭に付けた合計（年間合計、年計、通年合計）も合計の行と読みます。見出しが「項目」の表でも、最後の行の差引合計・控除合計は、上に合計のような行が無く金額の列が一つなら合計の行と読みます。契約書のように一つの文に書いた合計（「保守費60,000円、運用費30,000円とし、合計100,000円とする」「月額150,000円（内訳：…）」）も、その文に並べた同じ単位の金額の和と比べます。小計のあとの総計のように、足し方が何通りかあるときは、どの足し方でも合わないときだけ指します。
-  en: When the total of a quote or an invoice is not the sum of the amounts listed above it, the reader has to add them up again to find out which is right. It happens when a line is added or removed and the total is not updated. In a list or a table, a line starting with a total word (Total, Subtotal) is compared with the sum of the amounts in the same unit and column above it. A total with a word that the header of the table's first column, or of the column the total holds its number in, names ("Total deductions" under "Deduction", "Total credits earned" in the "Credits" column) is read as a total line too, and so is a total naming the span it covers ("Total for the year", "Year total", "Annual total"). Under a header that names nothing ("Item"), a "Total deductions" on the table's last row is read too, when no row above it is a total or a gross or net amount and the table has one column of amounts. A total written in a sentence, as contracts do ("$6,000 for hosting and $3,000 for support, for a total of $9,000", "$8 per month, made up of …"), is compared with the amounts in the same unit listed in that sentence. When there is more than one way to add them up, such as a grand total after a subtotal and tax, it is pointed out only when none of them matches.
+  ja: 見積や請求の「合計」が、上に並べた金額の和と合わないと、読み手はどちらが正しいのかを計算し直すことになります。行を足したり消したりしたあとに、合計だけ直し忘れると起きます。箇条書きか表で、合計の語（合計・小計）で始まる行を、同じ単位で同じ列の金額の和と比べます。表の最初の列の見出しか、合計の行が数を書いた列の見出しが名指す語を付けた合計（見出しが「控除項目」の表の「控除合計」、「単位数」の列の「修得単位合計」）も合計の行と読みます。合計が足す期間を頭に付けた合計（年間合計、年計、通年合計）も合計の行と読みます。見出しが「項目」の表でも、最後の行の差引合計・控除合計は、上に合計のような行が無く金額の列が一つなら合計の行と読みます。契約書のように一つの文に書いた合計（「保守費60,000円、運用費30,000円とし、合計100,000円とする」「月額150,000円（内訳：…）」「総額12,000円：設計5,000円、開発6,000円」）も、その文に並べた同じ単位の金額の和と比べます。合計で終わる文の次の文が「内訳は」で始まるときは、その文の金額と比べます。小計のあとの総計のように、足し方が何通りかあるときは、どの足し方でも合わないときだけ指します。
+  en: When the total of a quote or an invoice is not the sum of the amounts listed above it, the reader has to add them up again to find out which is right. It happens when a line is added or removed and the total is not updated. In a list or a table, a line starting with a total word (Total, Subtotal) is compared with the sum of the amounts in the same unit and column above it. A total with a word that the header of the table's first column, or of the column the total holds its number in, names ("Total deductions" under "Deduction", "Total credits earned" in the "Credits" column) is read as a total line too, and so is a total naming the span it covers ("Total for the year", "Year total", "Annual total"). Under a header that names nothing ("Item"), a "Total deductions" on the table's last row is read too, when no row above it is a total or a gross or net amount and the table has one column of amounts. A total written in a sentence, as contracts do ("$6,000 for hosting and $3,000 for support, for a total of $9,000", "$8 per month, made up of …", "a total of $12,000 — $5,000 for design and $6,000 for development"), is compared with the amounts in the same unit listed in that sentence, and with the amounts of the next sentence when it opens with a breakdown phrase ("This consists of …"). When there is more than one way to add them up, such as a grand total after a subtotal and tax, it is pointed out only when none of them matches.
 
 message:
   ja: 合計「{written}」が、内訳の金額の和（{sum}）と合いません
@@ -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).
+  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.

package/rules/unbalanced-bracket.yaml

@@ -52,5 +52,5 @@ example:
       The plan (see below) is ready.
 
 not_flagged:
-  ja: 行の頭や空白の後ろの「1)」「a)」「事例）」のような三文字までの番号の印、数の後ろの「）」、行の頭でも使う番号の印を括弧の中に書いたもの（「以下、事例5）まで同じ。」）、コードと URL は数えません。段落をまたいで閉じる括弧と、次の段落を同じ引用符で始める台詞も指しません。
-  en: Labels of up to three characters such as "1)" or "a)" at the start of a line or after a space, a ")" right after a number, a numbered label also used at the start of a line, written inside an aside ("(see the notes; A3) and more)"), code and URLs are not counted. A bracket closed in a later paragraph, and a quotation carried into a paragraph that opens with the same mark, are not reported.
+  ja: 行の頭や空白の後ろの「1)」「a)」「事例）」のような三文字までの番号の印、数の後ろの「）」、行の頭でも使う番号の印を括弧の中に書いたもの（「以下、事例5）まで同じ。」）、コードと URL は数えません。段落をまたいで閉じる括弧と、次の段落を同じ引用符で始める台詞も指しません。小数と単位の間の引用符はインチの印（.015 “Hg）として数えません。
+  en: Labels of up to three characters such as "1)" or "a)" at the start of a line or after a space, a ")" right after a number, a numbered label also used at the start of a line, written inside an aside ("(see the notes; A3) and more)"), code and URLs are not counted. A bracket closed in a later paragraph, and a quotation carried into a paragraph that opens with the same mark, are not reported. A curly quote between a decimal number and a unit is an inch mark (".015 “Hg") and is not counted.

package/rules/undefined-acronym.yaml

@@ -7,6 +7,7 @@ extra_word_lists:
   [
     definition-marker,
     definition-verb,
+    definition-statement,
     meridiem,
     time-zone,
     currency-code,
@@ -19,6 +20,14 @@ extra_word_lists:
     date-time-unit,
     http-method,
     reference-list-heading,
+    legal-form,
+    citation-series,
+    carrier-name,
+    name-prefix,
+    street-suffix,
+    tax-code,
+    capital-phrase,
+    name-determiner,
   ]
 uses: [pos]
 severity: info
@@ -70,5 +79,5 @@ not_flagged:
   ja: 誰でも知っている略語（URL、PDF など）と、前後の括弧で説明した略語は指しません。
   en: Common acronyms (URL, PDF) and acronyms spelled out in brackets next to them are not reported.
 level_meaning:
-  ja: 説明のない略語が {limit} 種類あれば指摘
-  en: reported once {limit} different acronyms go unexplained
+  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）、見出し・リンク・太字・HTML の要素・表・箇条書きの見出しの中、どこかで引用符か太字に入れた語、定義した語を含むもの（大文字小文字を問いません）、文書のどこかで小文字でも書いた語（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), anything inside a heading, a link, bold, an HTML element, a table or a list item's label, 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）、見出し・リンク・太字・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."
 rewrite:
   depth: light
   ja:

package/rules/unfilled-placeholder.yaml

@@ -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"), and "TBD" inside a sentence ("the date is TBD") are not reported.'
+  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.'

package/rules/unknown-word.yaml

@@ -47,8 +47,8 @@ example:
       The report is attached to this email.
 
 not_flagged:
-  ja: 大文字を含む語、四字より短い語、コード・URL・メールアドレスの中の語、強調や角括弧で頭の字を分けた語の残り（**G**lobally の lobally、[e]xpressions の xpressions）、文書で二度以上使う語、一字違いの辞書の語が無い語、chaff.yaml の names に並べた語、語彙表 known-misspelling が別に言う語は指しません。
-  en: Words with a capital letter, words shorter than four letters, words in code, URLs and email addresses, the rest of a word whose first letter is set apart by emphasis or brackets (lobally in **G**lobally, xpressions in [e]xpressions), words used twice or more in the document, words with no dictionary word one letter away, words listed under names in chaff.yaml, and the misspellings known-misspelling reports are not reported.
+  ja: 大文字を含む語、四字より短い語、コード・URL・メールアドレスの中の語、強調や角括弧で頭の字を分けた語の残り（**G**lobally の lobally、[e]xpressions の xpressions）、文書で二度以上使う語、一字違いの辞書の語が無い語、chaff.yaml の names に並べた語、語彙表 known-misspelling が別に言う語は指しません。同じ文書がコード（`tidyq check` やコードの区画）にも書いた語も、その文書の名前なので指しません。
+  en: Words with a capital letter, words shorter than four letters, words in code, URLs and email addresses, the rest of a word whose first letter is set apart by emphasis or brackets (lobally in **G**lobally, xpressions in [e]xpressions), words used twice or more in the document, words with no dictionary word one letter away, words listed under names in chaff.yaml, and the misspellings known-misspelling reports are not reported. Nor is a word the document also writes in code (`tidyq check`, a code block), since it is a name the document uses.
 rewrite:
   depth: light
   en:

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」といいます）も、法令の形と同じに読みます。見出しの行（章・節の行、条の前の「（買主の義務）」のような見出し）の語と、漢字で終わる語にさらに漢字が続く長い語（「監査委員会」の「監査委員」）と、定義の括弧の前の長い名前をそのまま書いた所（「…作成の手引き（以下「手引き」という。）」より前の「…作成の手引き」）は、使った所に数えません。最初の一か所だけを指します。
-  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.
+  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.
 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: 文書の長さに対して少ないものは指しません。短すぎる文書も測りません。要求の文の中の「可能な限り」「必要に応じて」は、要求の書き方として requirement-smell も見ます。
-  en: A few vague words for the document's length are not reported, and very short documents are not measured. 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".'
 level_meaning:
   ja: 1000 字あたりあいまいな語 {limit} 個まで
   en: up to {limit} vague words per 1000 words

package/src/api.ts

@@ -31,8 +31,17 @@ export type Section = { readonly depth: number; readonly heading: string; readon
 /** One bulleted or numbered list, with the length of each item in characters. */
 export type List = { readonly span: Span; readonly itemLengths: readonly number[] };
 
-/** One entry of a word list. instead_of is another way to write the same thing, for rules that check a document is consistent. */
-export type LexiconEntry = { readonly pattern: string; readonly instead_of?: string };
+/**
+ * One entry of a word list. instead_of is another way to write the same thing, for rules that check a document is
+ * consistent; rewrite, how to rewrite this phrase. genres: the genres or groups it holds in (legal, blog/tech); without
+ * them, every genre. options.lexicon and doc.lexicons hold only the entries for the document's genre.
+ */
+export type LexiconEntry = {
+  readonly pattern: string;
+  readonly instead_of?: string;
+  readonly rewrite?: string;
+  readonly genres?: readonly string[];
+};
 
 export type Lexicon = readonly LexiconEntry[];
 

package/src/capitals-passage.ts

@@ -0,0 +1,31 @@
+// A word set in capitals because the passage around it is (a disclaimer, a heading or a running header in capitals): eGAIN in
+// "eGAIN AND ITS SUPPLIERS MAKE NO WARRANTY" is the passage's capitals, not another spelling of eGain.
+
+/** Words read on each side of the span, in its sentence and on its line. */
+const NEIGHBOURS = 3;
+/** Words, the span's own included, that make a passage rather than one word in capitals. */
+const MIN_PASSAGE_WORDS = 3;
+/** How far to look on each side (UTF-16 units): three words, however long, fit. */
+const WINDOW = 200;
+const WORD = /\p{Script=Latin}[\p{Script=Latin}\p{N}'’]*/gu;
+const LOWER = /\p{Ll}/u;
+/** The end of a sentence or a line: the passage does not run across it ("7. Warranty. THE SYSTEMS ARE …"). */
+const STOP = /[.!?;:]\s|\n/gu;
+
+/** A word in capitals after its first letter (WARRANTY, eGAIN, eGAIN'S). */
+const isCapitalsWord = (word: string): boolean => !LOWER.test([...word].slice(1).join(""));
+
+/** The Latin words of two letters or more: a one-letter word (a, I) says nothing about the passage. */
+const wordsIn = (text: string): string[] => [...text.matchAll(WORD)].map((match) => match[0]).filter((word) => [...word].length >= 2);
+
+const afterLastStop = (text: string): string => text.slice(Math.max(0, ...[...text.matchAll(STOP)].map((match) => match.index + match[0].length)));
+
+const beforeFirstStop = (text: string): string => text.slice(0, [...text.matchAll(STOP)][0]?.index ?? text.length);
+
+/** Whether the words of text[start, end) and up to three words on each side of it, in its sentence, are all in capitals, three or more of them. */
+export const isInCapitalsPassage = (text: string, start: number, end: number): boolean => {
+  const before = wordsIn(afterLastStop(text.slice(Math.max(0, start - WINDOW), start))).slice(-NEIGHBOURS);
+  const after = wordsIn(beforeFirstStop(text.slice(end, end + WINDOW))).slice(0, NEIGHBOURS);
+  const words = [...before, ...wordsIn(text.slice(start, end)), ...after];
+  return words.length >= MIN_PASSAGE_WORDS && words.every(isCapitalsWord);
+};

package/src/cli-text.ts

@@ -49,9 +49,10 @@ const USAGE_JA = `chaff — 文章の読みにくいところを見つけます
   chaff ai-score <file>... [--format text|json] [--json] [--compact]
                                  AI らしさの簡易判定（低・中・高）。生成文に多い目印を、同じジャンルの人の文書と比べる（書いたのが AI かは判定しない）
                                  --json は --format json と同じ。--compact はファイルごとに 1 行
-  chaff grade <items.jsonl> [--out <results.jsonl>] [--baseline <前の results.jsonl>] [--allow-stamp-mismatch]
+  chaff grade <items.jsonl> [--rubric <rubric.yaml|.json>] [--out <results.jsonl>] [--baseline <前の results.jsonl>] [--allow-stamp-mismatch]
               [--variant-key <欄>] [--format text|json|markdown] [--json] [--compact]
                                  AI の出力を JSONL でまとめて採点する（指摘の率・事実・引用・合否。何も送らない）
+                                 --rubric はその回だけ chaff.yaml の grade: の代わりにそのファイル（grade: と同じ形の YAML か JSON）で採点する
                                  --allow-stamp-mismatch はルールか設定が前の回と違っても比べる（そのことを先に出す）
                                  --variant-key は variant の欄の代わりにその欄で出力を分けて並べる。--json は --format json と同じ。markdown は PR のコメント向け
   chaff fix-plan <file> [--depth light|structure|register] [--json]
@@ -108,9 +109,10 @@ const USAGE_EN = `chaff — finds what makes writing hard to read. It never rewr
   chaff ai-score <file>... [--format text|json] [--json] [--compact]
                                  quick AI-likeness score (low, medium, high): signs common in generated text against human documents of the genre (not a verdict on who wrote it)
                                  --json is --format json; --compact prints one line per file
-  chaff grade <items.jsonl> [--out <results.jsonl>] [--baseline <earlier results.jsonl>] [--allow-stamp-mismatch]
+  chaff grade <items.jsonl> [--rubric <rubric.yaml|.json>] [--out <results.jsonl>] [--baseline <earlier results.jsonl>] [--allow-stamp-mismatch]
               [--variant-key <field>] [--format text|json|markdown] [--json] [--compact]
                                  grade a JSONL file of model outputs (finding rates, facts, quotations, pass or fail; sends nothing)
+                                 --rubric grades by that file (YAML or JSON, shaped like grade:) instead of chaff.yaml's grade: for this run
                                  --allow-stamp-mismatch compares with the baseline even when its rules or settings differ, saying so first
                                  --variant-key splits the outputs by that field instead of variant; --json is --format json; markdown is for a PR comment
   chaff fix-plan <file> [--depth light|structure|register] [--json]

package/src/coined-hyphen-name.ts

@@ -0,0 +1,27 @@
+// A name coined from pieces joined by hyphens (Medi-Cal, the name of a programme): the pieces after the first are capitalised
+// and one of them is not a word. Closed up, its letters spell an ordinary word (medical), which is another word and not another
+// spelling of the name.
+
+const CAPITALISED = /^\p{Lu}\p{Ll}+$/u;
+
+/** Whether a hyphenated word is a coined name. isWord says whether a lower-case word is in the language's dictionary. */
+export const isCoinedName = (word: string, isWord: (word: string) => boolean): boolean => {
+  const later = word.split("-").slice(1);
+  return later.length > 0 && later.every((part) => CAPITALISED.test(part)) && later.some((part) => !isWord(part.toLowerCase()));
+};
+
+const UPPER = /\p{Lu}/u;
+
+/**
+ * The words without the coined names whose key the document otherwise writes only in small letters (Medi-Cal beside medical).
+ * Beside a spelling with capitals of its own (Wi-Fi beside WiFi) the coined name is still a spelling of that name. spelling is the
+ * word with the first letter of each part in small letters.
+ */
+export const withoutCoinedNames = <Word extends { readonly key: string; readonly spelling: string; readonly shown?: string }>(
+  words: readonly Word[],
+  isWord: (word: string) => boolean,
+): Word[] => {
+  const isCoined = (word: Word): boolean => isCoinedName(word.shown ?? word.spelling, isWord);
+  const capitalKeys = new Set(words.filter((word) => !isCoined(word) && UPPER.test(word.spelling)).map((word) => word.key));
+  return words.filter((word) => !isCoined(word) || capitalKeys.has(word.key));
+};