chaffjs 0.30.0 → 0.32.0

package/rules/unknown-word.yaml

@@ -37,7 +37,7 @@ off_for:
 
 group: slips
 summary:
-  en: An English word that is not in the dictionary and is one letter away from one that is, such as "attched"
+  en: An English word not in the dictionary but one letter from one ("attched")
   ja: 辞書に無く、一字違いの辞書の語がある英語の語（attched）
 example:
   en:

package/rules/unlisted-item-used.yaml

@@ -0,0 +1,90 @@
+id: unlisted-item-used
+layer: L3
+status: stable
+how_to_find: unlisted-item-used
+# The list headings are item-list-heading's; the use frames item-use's; item-amount is taken off a thing's name and
+# item-at-hand is never reported; enumeration-joiner joins the things of one step.
+requires: [pos]
+languages: [ja, en]
+severity: warning
+
+name:
+  ja: 一覧に無い材料や道具を手順で使っている
+  en: A step uses something the list of what you need leaves out
+
+why:
+  ja: 「材料」「用意するもの」の一覧を見て揃えた読み手は、手順の途中で一覧に無い物（こしょう、バケツ）が出てくると、そこで手が止まります。一覧に足し忘れたか、手順のほうを書き間違えています。番号を振った手順のうち、物を使う形の名詞だけを読みます。「〜を入れる」「〜を加える」「add」「put」の物と、道具も入る一覧（用意するもの、What you need）がある文書では「〜で磨く」「〜に沈める」「with the …」「in a …」の物です。その物を、文書が手順より前に（一覧、題、前の手順で）書いていれば言いません。名前の最後の語だけ書いてあっても同じです。水・湯・手・空気のように、いつも手元にあって一覧に書かない物も言いません。
+  en: 'A reader who gathered everything on the "Ingredients" or "What you need" list stops halfway when a step calls for something the list does not have (pepper, a bucket). Either the list left it out or the step is wrong. Only a noun a numbered step uses is read: the object of a use verb ("add", "put", "stir in"), and, in a document whose list includes tools ("What you need", "Tools"), the thing after "with the" or "in a". It is not reported when the document has written it before the step (in the list, the title or an earlier step), whole or by its last word, nor when it is always at hand and never listed (water, hands, air).'
+
+message:
+  ja: 「{item}」は、{list}に書いてありません
+  en: '"{item}" is not in {list}'
+
+how_to_fix:
+  ja: 一覧に足すか、手順を一覧にある物で書き直してください。
+  en: Add it to the list, or rewrite the step with what the list has.
+
+# chaff explain と規則の一覧には指摘が無いので、{item} と {list} をこう読ませる。
+placeholders:
+  item:
+    ja: 〇〇
+    en: the item
+  list:
+    ja: 材料の一覧
+    en: the list
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: structure
+summary:
+  ja: 手順で使う材料や道具が、材料・用意するものの一覧に無い所
+  en: A step that uses an ingredient or a tool missing from the document's own list
+example:
+  ja:
+    before: |
+      ## 材料
+
+      - 卵 2個
+      - 塩 少々
+
+      ## 作り方
+
+      1. 卵を割りほぐし、塩、こしょうを加えます。
+    after: |
+      ## 材料
+
+      - 卵 2個
+      - 塩 少々
+      - こしょう 少々
+
+      ## 作り方
+
+      1. 卵を割りほぐし、塩、こしょうを加えます。
+  en:
+    before: |
+      ## Ingredients
+
+      - 2 eggs
+      - A pinch of salt
+
+      ## Method
+
+      1. Beat the eggs and add the salt and pepper.
+    after: |
+      ## Ingredients
+
+      - 2 eggs
+      - A pinch of salt
+      - A pinch of pepper
+
+      ## Method
+
+      1. Beat the eggs and add the salt and pepper.
+
+not_flagged:
+  ja: 一覧の見出しが無い文書、番号の無い手順、物を使う形でない名詞（オーブンで焼く、は道具も入る一覧がある文書だけ）、手順より前に書いた物、いつも手元にある物（水、湯、手、空気、皿）、「使わずに」と打ち消した物は言いません。
+  en: 'A document with no list heading, steps without numbers, a noun not in a use frame ("with the", "in a" only in a document that lists tools), anything written before the step, what is always at hand (water, hands, air, plates), and a use that is denied ("do not add") are not reported.'

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」という）で書いた語だけを見ます。複数形と所有の形（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. A second definition of the same term is duplicate-definition's to report.
+  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.
 rewrite:
   depth: light
   ja:

package/rules/url-run-on.yaml

@@ -27,7 +27,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: slips
 summary:
   ja: 「https://example.jp/をご覧ください」のように、URL のすぐ後ろに字が続き、リンクがそこまで伸びる所
-  en: A URL followed straight away by a character outside ASCII, which the link swallows
+  en: A URL followed straight away by text that the link swallows
 example:
   ja:
     before: |

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」とは…をいう）で定義した語は、前で使っても言いません。定義の条は文書の頭にも終わりにも置く書き方があるためです。見出しの行（章・節の行、条の前の「（買主の義務）」のような見出し）の語と、漢字で終わる語にさらに漢字が続く長い語（「監査委員会」の「監査委員」）は、使った所に数えません。最初の一か所だけを指します。
-  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. Only the first early use is pointed at.
+  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.
 rewrite:
   depth: structure
   ja:

package/rules/vague-deadline.yaml

@@ -35,7 +35,7 @@ off_for:
 group: wording
 summary:
   ja: ほかの期限を日数で書いた契約で、一部の期限だけを「速やかに」「遅滞なく」と書いた所
-  en: A deadline written as "promptly" or "without undue delay" in a contract that gives its other deadlines in days
+  en: A deadline written as "promptly" where other deadlines are in days
 example:
   ja:
     config: { genre: legal/contract }

package/rules/vague-figure-reference.yaml

@@ -42,7 +42,7 @@ sources: [jis-z8301-2019]
 group: structure
 summary:
   ja: 図や表、条に番号を付けた文書で、「上記の図」「下の表」「以下の箇条」のように置き場所で指している所
-  en: '"The figure above", "the table below" or "the clause below" in a document that numbers its figures, tables or clauses'
+  en: '"The table below" in a document that numbers its tables and figures'
 example:
   ja:
     before: |

package/rules/vague-word-density.yaml

@@ -36,8 +36,8 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
 group: wording
 summary:
-  ja: 「適宜」「適切に」「必要に応じて」のように、どこまで・いつまでを読み手に決めさせる語が、文書の長さに対して多い所
-  en: Vague words ("as appropriate", "as needed", "in a timely manner"), many for the document's length
+  ja: 「適宜」「必要に応じて」のように、どこまでを読み手に決めさせる語が多い所
+  en: Too many vague words ("as appropriate", "as needed") for the length
 example:
   ja:
     pad: true

package/rules/variance-mismatch.yaml

@@ -0,0 +1,67 @@
+id: variance-mismatch
+layer: L3
+status: stable
+how_to_find: variance-mismatch
+# The column headings are lexicon variance-column (groups budget, actual, variance, rate); words of magnitude are amount-multiplier.
+severity: warning
+
+name:
+  ja: 予算と決算の差が、増減の列と合わない
+  en: A variance that is not the difference of the budget and the actual
+
+why:
+  ja: 予算額・決算額・増減を並べた表では、読み手は増減の列だけを見て、予算をどれだけ超えたか、どれだけ残ったかを判断します。決算額を直したのに増減を直し忘れたとき、桁を写し間違えたときに、増減だけが食い違います。見出しの語で予算の列（予算額、予算）、決算の列（決算額、実績）、増減の列（増減、差異、差額、予算比）が一つずつ分かる表では、行ごとに決算額から予算額を引いた額と、書いた増減を比べます。△・▲・−・- の付いた額と括弧に入れた額は負の数と読みます。増減を「予算額から決算額を引いた額」で書く表もあるので、どちらの向きかは表のほかの行（どの行も向きを言わない表では文書のほかの表）が多く従うほうに決め、決まらなければ言いません。
+  en: In a table of budget, actual and variance, readers look at the variance column alone to see how far over or under budget each line went. When an actual figure is corrected and its variance is not, or a digit is copied wrong, the variance alone is off. When the headings name one budget column (Budget), one actual column (Actual) and one variance column (Variance, Difference, Over (under)), each row's actual less its budget is compared with the variance written. An amount marked -, −, ▲ or △, or written in brackets, is negative. Some tables write the variance the other way, as the budget less the actual, so the direction is the one most of the table's other rows follow (or, when no row of the table tells, the document's other tables); when the rows split evenly, nothing is said.
+
+message:
+  ja: 「{item}」の増減は「{written}」ですが、予算と決算の差からは「{expected}」です
+  en: '"{item}" shows a variance of "{written}", but its budget and actual give "{expected}"'
+
+how_to_fix:
+  ja: 予算額・決算額・増減のどれが正しいかを確かめて、ほかを直してください。
+  en: Check which of the budget, the actual and the variance is right, and correct the others.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 予算額と決算額の差が、書いた増減と合わない行
+  en: A table row whose variance is not the difference of its budget and actual
+example:
+  ja:
+    before: |
+      | 項目 | 予算額 | 決算額 | 増減 |
+      | --- | --- | --- | --- |
+      | 会費 | 510,000円 | 504,000円 | △6,000円 |
+      | 防災用品の購入費 | 80,000円 | 86,900円 | 6,090円 |
+      | 会議・事務費 | 40,000円 | 35,280円 | △4,720円 |
+    after: |
+      | 項目 | 予算額 | 決算額 | 増減 |
+      | --- | --- | --- | --- |
+      | 会費 | 510,000円 | 504,000円 | △6,000円 |
+      | 防災用品の購入費 | 80,000円 | 86,900円 | 6,900円 |
+      | 会議・事務費 | 40,000円 | 35,280円 | △4,720円 |
+  en:
+    before: |
+      | Item | Budget | Actual | Variance |
+      | --- | --- | --- | --- |
+      | Street lighting | $480.00 | $469.20 | ($10.80) |
+      | Emergency supplies | $400.00 | $434.50 | $43.50 |
+      | Seniors' lunch | $600.00 | $590.00 | ($10.00) |
+    after: |
+      | Item | Budget | Actual | Variance |
+      | --- | --- | --- | --- |
+      | Street lighting | $480.00 | $469.20 | ($10.80) |
+      | Emergency supplies | $400.00 | $434.50 | $34.50 |
+      | Seniors' lunch | $600.00 | $590.00 | ($10.00) |
+
+not_flagged:
+  ja: 見出しから予算・決算・増減の列が一つずつ決まらない表（当初予算と補正予算が並ぶ表など）、率の列（増減率、執行率、% を書いた列）、升が金額でない行（—、98.8%）、予算額と決算額の単位の書き方が違う行は比べません。増減の向きが、表の行で同じ数ずつに分かれる表は言いません。もう一方の向きに従う行が二つ以上ある表では、それらを書き手が選んだ向きと読み、向きの違いだけでは言いません。千円・百万円や単位の無い数は丸めた額と読み、一桁の差は言いません。
+  en: "A table whose headings do not name one budget, one actual and one variance column (an original and a revised budget side by side), a column of rates (Variance %, Rate, Ratio), a row whose cells are not amounts (—, 98.8%), and a row whose budget and actual are written in different units are not compared. A table whose rows split evenly between the two directions is not reported, and when two or more rows follow the other direction, the difference in direction alone is not reported. Amounts in thousands or millions, and bare numbers, are read as rounded, so a difference of one in the last digit is not reported."
+level_meaning:
+  ja: 予算と決算の差が増減の列と合わない行を指摘
+  en: reported when a row's variance is not its actual less its budget (or the reverse, as the table's rows do)

package/rules/very-adjective.yaml

@@ -34,7 +34,7 @@ off_for:
 group: wording
 summary:
   ja: 「とても便利」「非常に危険」（very important）のような強め + 形容詞が、文書の長さのわりに多い所
-  en: '"Very" + adjective, such as "very important" (とても便利), dense for the document''s length'
+  en: '"Very" + adjective, such as "very important", used too often'
 example:
   ja:
     pad: true

package/rules/walk-time-distance-mismatch.yaml

@@ -0,0 +1,55 @@
+id: walk-time-distance-mismatch
+layer: L3
+status: stable
+how_to_find: walk-time-distance-mismatch
+severity: warning
+
+name:
+  ja: 距離と合わない徒歩の分数
+  en: A walking time that does not match the stated distance
+
+why:
+  ja: 「駅 徒歩3分（約600m）」のように、徒歩の分数と距離が合わないと、どちらかを書き間違えています。不動産の広告では、道路距離80mを1分とし、1分未満の端数を切り上げて分数を出すと決められていて（不動産の表示に関する公正競争規約施行規則）、600mなら8分です。徒歩の語の付いた分数と、そのすぐ前か後ろの括弧などに書いた距離だけを組にして比べます。速さは文書に書いたもの（道路距離80mを1分、分速80m）を使います。書いていなければ、物件広告（profile listing。物件概要の項目の並ぶ文書は設定なしでもそう読みます）だけ80mで1分、端数は切り上げとして比べ、ほかの文書は比べません。約の付いた距離は、書いた桁の幅を持たせます（約1.2kmは1.15〜1.25km）。
+  en: 'When a listing says "a 3-minute walk (600 m)" while it states that walking times assume 80 m per minute, the time or the distance is wrong: 600 m is 8 minutes at that rate. A number of minutes with a word of walking ("walk", "on foot") is compared only with a distance written right before or after it, and only at a rate the document states itself ("80 m per minute", "5 km/h"); without a stated rate, only a Japanese property listing (profile listing, chosen by its shape when no profile is set) uses the advertising standard of 80 m a minute, rounded up, and nothing else is compared. Part minutes may be rounded either way, or only up when the rate line says so. An approximate distance ("about 1.2 km") is read with the width of its last digit.'
+
+message:
+  ja: 「{minutes}」は「{distance}」と合いません（分速{rate}mで{expected}分）
+  en: '"{minutes}" does not match "{distance}" ({expected} minutes at {rate} m per minute)'
+
+how_to_fix:
+  ja: 距離と分数を確かめて、書き間違えたほうを直してください。物件広告の分数は、道路距離を80mで割り、端数を切り上げて出します。
+  en: Check the distance and the walking time, and correct the wrong one, using the rate the document states.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 「徒歩3分（約600m）」のように、徒歩の分数が書いた距離と合わない所
+  en: A walking time that does not match the distance beside it
+example:
+  ja:
+    before: |
+      | 交通 | あおば線「青葉台」駅 徒歩3分（約600m） |
+      | 賃料 | 98,000円 |
+      | 敷金 | 1か月 |
+    after: |
+      | 交通 | あおば線「青葉台」駅 徒歩8分（約600m） |
+      | 賃料 | 98,000円 |
+      | 敷金 | 1か月 |
+  en:
+    before: |
+      | Access | Ashford Station, a 3-minute walk (600 m) |
+
+      Walking times assume 80 m per minute along the road, rounded up to the next minute.
+    after: |
+      | Access | Ashford Station, an 8-minute walk (600 m) |
+
+      Walking times assume 80 m per minute along the road, rounded up to the next minute.
+
+not_flagged:
+  ja: 距離の無い分数、徒歩の語の無い分数（バスで10分、駅から5分）、分数と離れて書いた距離、範囲（徒歩5〜7分、400〜600m）、上限や目安の分数（徒歩10分以内、徒歩10分程度）、約の付いた分数（徒歩約5分）、速さを書いていない物件広告でない文書（観光案内の「徒歩10分（約500m）」）、速さを二つ以上書いた文書は比べません。
+  en: 'Minutes with no distance, minutes without a word of walking ("10 minutes by bus"), a distance written apart from the minutes, ranges ("5-7 minutes", "400-600 m"), limits ("within a 10-minute walk"), approximate minutes ("about 5 minutes on foot"), a document stating no rate, and a document stating two rates are not compared.'

package/rules/warning-without-action.yaml

@@ -36,7 +36,7 @@ off_for:
 group: wording
 summary:
   ja: 「注意」「警告」で始まる段落で、危険だけを書き、読み手のすること（〜してください、〜しないこと）が無いもの
-  en: A paragraph opening with Warning or Caution that names a risk and no action for the reader
+  en: A Warning that names a risk but not what the reader should do
 example:
   ja:
     config: { genre: docs/manual }

package/rules/weasel-word.yaml

@@ -33,8 +33,8 @@ off_for:
 
 group: wording
 summary:
-  ja: 「〜と言われています」「ある研究によると」（many experts say, studies show）のように、主張を名前の無い誰かに預ける言い回し
-  en: Phrases such as "many experts say" and "studies show" (と言われています, ある研究によると) that credit a claim to no one in particular
+  ja: 「〜と言われています」「ある研究によると」のように、主張を名前の無い誰かに預ける言い方
+  en: Phrases like "many experts say" or "studies show" that credit no one
 example:
   ja:
     before: |

package/rules/wordy-phrase.yaml

@@ -34,8 +34,8 @@ off_for:
 
 group: wording
 summary:
-  ja: 「することが可能」「現時点において」（in order to、due to the fact that）のように、一語で言えることを何語もかけて言う所
-  en: Phrases such as "in order to" and "due to the fact that" (することが可能, 現時点において) that take several words to say what one says
+  ja: 「することが可能」「現時点において」のように、一語で言えることに何語もかける所
+  en: Phrases like "in order to" or "due to the fact that" where one word does
 example:
   ja:
     before: |

package/rules/yori-as-from.yaml

@@ -35,7 +35,7 @@ sources: [koyobun-2022]
 group: wording
 summary:
   ja: 「4月1日より開始」のように、起点を「から」でなく「より」で書いた所
-  en: より written for a starting point (4月1日より開始) where Japanese official style writes から
+  en: より written for a starting point (4月1日より) where official style writes から
 example:
   ja:
     before: |

package/skills/chaff/SKILL.md

@@ -1,12 +1,14 @@
 ---
 name: chaff
-description: "Check prose with chaff (npx chaffjs): pick the genre preset for the kind of document (contract, statute, manual, FAQ, paper, fiction, transcript…), run it on Markdown or text, read each finding, fix the text or record why not, and tune chaff.yaml with rules --json and relax --why. Use when asked to lint, proofread or tighten documents, or to set up a team's writing rules. Also use when asked to make text sound less AI-generated (「AIっぽさをなくして」「AI臭さを消して」「人間らしく書き直して」, 'make this sound human'): Light, Bold or Full mode, with Full (全面書き直し) when the request says 「全面的に」 or 'from scratch'."
+description: "Check prose with chaff (npx chaffjs): pick the genre preset for the kind of document (contract, statute, manual, FAQ, paper, fiction, transcript…), run it on Markdown or text, read each finding, fix the text or record why not, and tune chaff.yaml with rules --json and relax --why. Use when asked to lint, proofread or tighten documents, to check that a document's totals, dates and references agree, or to set up a team's writing rules. Also use when asked to make text sound less AI-generated (「AIっぽさをなくして」「AI臭さを消して」「人間らしく書き直して」, 'make this sound human'): Light, Bold or Full mode, with Full (全面書き直し) when the request says 「全面的に」 or 'from scratch'."
 ---
 
 # Checking writing with chaff
 
 chaff finds what makes writing hard to read — long sentences, padding, mixed styles, broken references in a
-contract — and never rewrites anything. Reading the findings and changing the text is your part. Japanese and
+contract. It also finds where a document's own numbers and dates disagree: a total that is not the sum of its
+items, a date and its weekday that do not match, an end date before the start. It never rewrites anything, and the
+same text gives the same result every time. Reading the findings and changing the text is your part. Japanese and
 English documents both work; the language is detected per file.
 
 ## Pick the genre first
@@ -26,7 +28,7 @@ read. A contract checked as a blog post gets wrong findings, so choose the genre
 5. With the genre set, the report opens with the genre's guide: what a good document of that kind does, and the
    rules that matter most for it. Read it first, before any finding, and hold the draft (or your rewrite) to each
    line; most of it is what no rule can check. The team may have changed it with `guide:` in `chaff.yaml`. A
-   guessed or default genre shows no guide.
+   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.
@@ -43,11 +45,25 @@ A run exits 1 when a finding is an `error`. It also exits 1 when it could not ch
 check, an unknown `--genre`, no package for the language. So a clean exit means the files were checked.
 
 After the findings comes the list of rules that did not run, and why. Only the default output shows it;
-`--compact` gives just their number. Read it before saying a document is clean.
+`--compact` gives just their number. Read it before saying a document is clean. Two reasons there are not about
+the genre: a rule that compares documents runs only when chaff is given two or more files or a folder, and a rule
+that reads meaning runs only under `npx chaffjs test` (below).
 
 A run over several files prints only the files that have findings. To call one file clean, run chaff on that
 file alone and read its list.
 
+The default output ends each file with an `AI-likeness:` line (low, medium or high, or why it was not scored).
+`npx chaffjs ai-score <file>` gives the same on its own. It counts signs common in generated text against human
+documents of the genre; it does not say who wrote the text.
+
+## Checks that read meaning
+
+A few checks need a reader: does the proposal state its risks, does the conclusion only restate the body, does a
+number claiming an effect have a source. chaff never runs a model in a plain check. `npx chaffjs test <file|dir>`
+narrows the candidates by machine and sends only those passages to an AI (Anthropic or OpenAI, set by
+`ai_backend` in `chaff.yaml`; it needs an API key). Run it with `--dry-run` first: it shows what would be sent and
+calls nothing. Ask the person before a real run; the passages leave the machine.
+
 ## For each finding, choose one of three
 
 | | When | How |
@@ -59,6 +75,18 @@ file alone and read its list.
 `npx chaffjs explain <rule-id>` shows why a rule exists, its levels and the current one. Read it before
 relaxing a rule.
 
+## 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:
+totals and their items, quantity times price, tax and net amounts, and percentages that should add up to 100%.
+Also a date and its weekday, dates and periods out of order, a reference number written two ways, and one fee or
+deadline given two values. Most of these are an `error`.
+
+Such a finding says two places in the document disagree. It does not say which one is wrong. Check the source
+(the quote, the ledger, the calendar, the booking, or the person) before changing anything, then fix the wrong one.
+Never "fix" it by changing the figure that was right, and never adjust both so they merely agree. If you cannot
+tell which is right, leave both and ask.
+
 ## Tune chaff.yaml
 
 - `npx chaffjs init --genre <genre>` writes a commented `chaff.yaml` for that genre when there is none (an
@@ -67,7 +95,8 @@ relaxing a rule.
   the genre's preset included) and why a rule is off. Read it instead of guessing rule names or limits.
   `npx chaffjs rules` shows the same as a table, grouped, with the level each rule runs at now.
 - A level is `strict` / `normal` / `relaxed` / `off`; when even `relaxed` is too tight, a positive number is the
-  limit itself (`max-sentence-length: 260`).
+  limit itself (`max-sentence-length: 260`). A rule with nothing to count takes fewer levels, and no number;
+  `levels_you_can_set` in `rules --json` lists them.
 - `prefer:` maps spellings to the team's (`e-mail: email`); `preferred-term: normal` turns the rule on.
 - Unknown rule names and unreadable values are reported on stderr — read stderr after editing `chaff.yaml`.
 - `genre:` sets the kind of document. `by_path` sets it per path, as a list of `files` globs, each with `genre`,
@@ -82,6 +111,10 @@ relaxing a rule.
   A file's front matter `genre:` (or `type:`) sets that one file, when neither `genre:` nor a matching `by_path`
   entry does. Strongest first: `--genre` for one run, then `by_path`, `genre:`, front matter, the path, the content,
   and `blog/tech`. `rules:` wins over the genre's preset.
+- `profile:` names a bundled kind of document with fixed conventions (`statute`). Leave it out: the genre or the
+  content chooses it, and the first line of `npx chaffjs tree` shows the choice. `none` stops the choice.
+- `names:` lists the team's names (organisations, products), each read as one name. `include:` adds files besides
+  Markdown when a folder is checked (`include: ["*.yaml"]`).
 
 ## Turn a team's style note into chaff.yaml
 
@@ -109,7 +142,7 @@ Pick the easiest way that can say the requirement:
 | A fixed phrase or pattern, with the team's own message | `custom_rules` of type `words` or `pattern` |
 | Decided by part of speech or inflection | `custom_rules` of type `tokens` |
 | Counting or comparing that the above cannot express | a Node function, `type: module` |
-| The same rules shared across repositories | a rule pack of YAML files: `npx chaffjs init --plugin <name>`, then `plugins:` in `chaff.yaml` |
+| The same rules shared across repositories | a rule pack of YAML files: `npx chaffjs init --plugin <name>`, `npx chaffjs plugin-test` in its folder, then `plugins:` in `chaff.yaml` |
 
 A `words` rule names the words, the team's text for each field `explain` shows, and one example:
 
@@ -137,11 +170,13 @@ Use this section when asked to make a text sound less generated: 「AIっぽさ
 
 chaff marks the shapes common in generated text (group "Signs of generated text" in `npx chaffjs rules`: `ai-tell`,
 `contrast-framing`, `stock-transition`, `announcing-opener`, `colon-lead-in` (Japanese only), `assistant-residue`, and the signals
-`ai-generated-composite` reads). They run by default outside legal, manual, literary and spoken genres. None of them says the text was
-generated. chaff never rewrites; the rewriting is yours.
+`ai-generated-composite` reads, among others). Most of them do not run in `technical/spec` or in the legal, docs, literature and
+speech genres; `assistant-residue` (words left from a pasted chat reply) runs in almost every genre. `npx chaffjs rules --json`
+says per rule and genre. None of them says the text was generated. chaff never rewrites; the rewriting is yours.
 
 **Start with the plan.** Run `npx chaffjs fix-plan <file>` (with the genre's `--genre`; `--json` to
-read it as data). It prints, in the document's language:
+read it as data; `--depth light|structure|register` when how deep the rewrite may go is already decided). It
+prints, in the document's language:
 
 - the genre's guide first, when the genre is set: what a good document of the kind does, the lines your rewrite
   is held to;
@@ -167,6 +202,11 @@ Pick one of three modes and say which.
 | **Bold** | each section's prose, keeping the outline | the outline is fixed (a report template, a manual, required sections) |
 | **Full** | the whole document, from scratch | the request says 「全面的に」「一から」「全部書き直して」 / "from scratch" / "rewrite the whole thing"; or the genre is `blog/*` or an essay (`literature/essay`); or `ai-generated-composite` fires; or the plan's structure score reaches its limit |
 
+The plan also names a fourth way, Register: a Full rewrite that also converts the style (polite to plain endings,
+です/ます to だ/である, and so on). chaff never recommends it; use it only when the person asks for the style to change
+(`--depth register`). With `--depth light`, a rule whose direction needs a deeper rewrite is listed by name and
+spot count only.
+
 For a blog or an essay, and whenever `ai-generated-composite` fires, recommend Full. A Light or Bold pass leaves the
 skeleton of generated text: a heading every few paragraphs, bold lead-ins, symmetric sections, a closing まとめ that
 repeats the body. The writer usually wants the structure changed, not only the sentences.
@@ -286,6 +326,16 @@ output before and after.
   terms defined twice.
 - `npx chaffjs cite <source> <quotes.json>` checks that quotations (`[{ "address", "quote" }]`) are really in
   the source; exit 1 if any is not. Use it to back every quotation you put in an answer or a summary.
+  `cite --url <URL> <quotes.json>` checks against a web page; `cite --scaffold <file>` prints the quotations in a
+  file that give no source, as JSON to fill in and pass to `cite`.
+- `tree --format json` and `cite --format json` give the same as data.
+
+## Grading model outputs
+
+`npx chaffjs grade <items.jsonl>` grades a file of model outputs, one JSON object per line (`id`, `output`, and
+`reference`, `sources` and `citations` when there are any): findings, dropped or added facts, quotations, pass or
+fail. It exits 1 when an output fails (with `--baseline`, when the run got worse) and sends nothing.
+`chaffjs/grade` does the same in code. The guide page "Using chaff for AI evals" covers baselines and variants.
 
 ## When chaff is wrong
 

package/src/announced-count.ts

@@ -14,6 +14,8 @@ export type CountWords = {
   readonly numbers: readonly string[];
   /** 数のすぐ後ろで並べるものを数える語。点、つ、steps。 */
   readonly counters: readonly string[];
+  /** 数える語と、それが何の種類かを言う語までの枠（kinds of、つの種類）。枠の中の of は「two of the following」の of ではない。 */
+  readonly frames: readonly string[];
   /** 数のすぐ前にあると予告でなくなる語（約、第、at least）。 */
   readonly hedgesBefore: readonly string[];
   /** 数か数える語のすぐ後ろにあると予告でなくなる語（以上、目、or more）。 */
@@ -51,16 +53,17 @@ export const alternation = (words: readonly string[]): string =>
     .join("|");
 
 /**
- * 数と、それが数えるもの。数の前が数字・英字・数の字なら数の途中（十三、23、eleven の中）。
+ * 数と、それが数えるもの。数の前が数字・英字・数の字なら数の途中（十三、23、eleven の中）。数字と点のすぐ後ろの数字は、
+ * 条の番号や小数の続き（7.1、3.5）で、それだけでは数ではない。
  * 英語は数と数える語の間に語を二つまで置ける（three key steps）。数える語が無くても、文がコロンで終わる直前の数（the following two:）と、
  * その後ろに語が一つだけある数（the following three documents:）は数に読む。どちらも先を指す語のすぐ後ろでだけ予告になる（pointsAhead）。
  */
 const phrasePattern = (words: CountWords): RegExp => {
   const numberChars = escapeRegExp([...new Set(words.numbers.join(""))].join(""));
   const numbers = words.numbers.length === 0 ? "\\p{Nd}+" : `\\p{Nd}+|${alternation(words.numbers)}`;
-  const counted = `[ \\t\\u00a0]?(?:\\p{Ll}[\\p{Ll}-]*[ \\t]){0,2}(${alternation(words.counters)})(?![A-Za-z])`;
+  const counted = `[ \\t\\u00a0]?(?:\\p{Ll}[\\p{Ll}-]*[ \\t]){0,2}(${alternation([...words.frames, ...words.counters])})(?![A-Za-z])`;
   const uncounted = String.raw`(?:[ \t]\p{Ll}[\p{Ll}-]*)?(?=[ \t]?[:：][ \t]*$)`;
-  return new RegExp(`(?<![\\p{N}A-Za-z${numberChars}])(${numbers})(?:${counted}|${uncounted})`, "giu");
+  return new RegExp(`(?<![\\p{N}A-Za-z${numberChars}])(?<!\\p{Nd}[.．])(${numbers})(?:${counted}|${uncounted})`, "giu");
 };
 
 export const valueOf = (written: string, numbers: readonly string[]): number => {