Parties listed in the reverse of the document's usual order
party-orderon by default (info)Japanese
乙及び甲 in a contract that otherwise writes 甲及び乙
Example
How to fix
List the parties in the same order as elsewhere. If the order is meant (the second party first on purpose), leave it.
Why it matters
A Japanese contract lists its parties in a fixed order (甲及び乙, 甲又は乙, 甲乙, 甲・乙・丙). In a contract that writes 甲及び乙 everywhere else, a single 乙及び甲 makes the reader look for a reason to put 乙 first. It comes from pasted or rewritten clauses. Only names joined by a listing word (及び, 又は, と, ・) are counted, and a listing is reported when its order is written at most half as often as the reverse.
What it does not flag
A direction (乙から甲への通知, 甲に対し乙は, 甲が乙に) is not a listing and is not counted. A comma joins names only in a listing that goes on to a listing word (甲、乙及び丙). A name that starts a longer word (the 甲 of 甲種株式) is not read. When the two orders are written about as often (the reverse more than half as often), neither is the usual order and nothing is reported. The names are 甲, 乙, 丙 and 丁 and the short names the document gives its parties in brackets. Contracts only, in Japanese documents only.
Turning it off or relaxing it
Technical details
- Layer
- L3
- Status
- stable
- Severity
- info
- Languages
- ja
- Suited to
- legal, docs, academic, literature, speech
- Reads from the document
- structure
Levels
Set a level for this rule under rules in chaff.yaml. With nothing set, it runs at the level its genre gives it (see By genre below).
| strict | warning |
|---|---|
| normal | info |
| relaxed | info |
This rule has no limit to count to. A level sets how a finding is marked: relaxed keeps the finding and marks it a step lower.
By genre
- Runs by default in
- legal/contract
- Turned off by the genre in
- legal/statute, legal/judgment, legal/patent, docs/manual, docs/faq, docs/glossary, academic/paper, literature/fiction, literature/essay, literature/poetry, literature/play, speech/address, speech/transcript
- Not suited to, and not run in
- technical/spec, technical/readme, blog/tech, blog/essay, blog/owned-media, business/proposal, business/report, business/email, business/press-release, business/meeting-notes
Message
"{written}" lists the parties in the reverse of the order this document uses elsewhere ("{usual}")
Rewrite depth (chaff fix-plan --depth): light — words and sentences; the structure and the voice stay
This page is built from the rule's definition file:packages/chaff/rules/party-order.yaml