asciidoc-pubkit 0.1.1 → 0.6.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b5e89872635e44464421539669ea3fb4a76c886a3adae9f5ca1df98fd864d05c
-  data.tar.gz: bf081702caf7eca34423eea571fd23ad9dfffc89ed11c9b1d013dd84fb25d57c
+  metadata.gz: 40d5596e5b8145d6e367ec2301955cfed5997a79732eaaecf7fcd69509e9c12a
+  data.tar.gz: 9bfedb0f4c451c6c175f04721935281c37394f17c10b8c08c9eb836e83340a86
 SHA512:
-  metadata.gz: 93bae7f5ef964afa60b0d6eee95b332270907df107dedae820c09fbbc1829d0d88077df96c20eaff8d9654f31ff6e47390517d1922b6486186dfa04ff17d107a
-  data.tar.gz: 5ab456dedf2c322836c827e00a0e2443b3bb9709202d88a0e82203561af98c6953debc601c799355f4df45b744d645f7c4cb670b812c0d7240c374973de09f7c
+  metadata.gz: 0416faaaddc07dc7ac062c0c06393165d88c4e95e8bab97e62e775f4ae78c08817354c69119c4e96ac0f65d8db17576bd254825babe848f10e07917ac45c9a38
+  data.tar.gz: df1a01d62c8a625921347536303ea7dbba2659e56ecbb546e7abcffcf9f3c57b005e5add24460702ac9413ad18192b130aeb4a092c7ba6d52927cad84b4a81cf

data/CHANGELOG.md

@@ -1,5 +1,39 @@
 # Changelog
 
+## Unreleased
+
+## 0.6.0 — 2026-09-30
+
+- Add `writing criteria` and `writing prompt` commands backed by one packaged
+  Japanese technical prose guide. Include that guide in saved review prompts.
+- Organize the CLI into `writing` and `review` groups and accept `--lang ja` on
+  both. Reject unsupported languages explicitly, including document attributes.
+- Save the shared criteria and language with each review session, and update the
+  book writing and review skills to use the generated prompts.
+- Refine Japanese review questions for redundant qualifications and generic
+  recaps, and document the editorial sources and contextual limits.
+
+## 0.1.3 — 2026-09-29
+
+- Consolidate Japanese review candidates for terminology, compressed noun
+  relationships, operations, and negative qualifications in the packaged rules.
+- Suppress literal candidates contained in longer matched terms, preserving
+  allow-list handling, and recognize sahen potential forms before noun rules.
+- Reduce single-file review prompts by emitting each paragraph once, sharing
+  context metadata, and compacting JSON; retain all candidates and review settings.
+- Confirm replacement of existing review sessions in interactive scans.
+- Add `review scan --yes` (`-y`) and `--no-input` for batch execution.
+- Preserve previous sessions until replacement scan artifacts are ready.
+
+## 0.1.2 — Released
+
+- Package default Japanese review rules as a validated UTF-8 YAML file.
+- Support custom rule files through `review scan --rules` and `review.rules`.
+- Save resolved rules in sessions for reproducible prompts and verification.
+- Add concept, distinction, and negative meaning review candidates.
+- Add a Make target for running a local checkout with arbitrary CLI arguments.
+- Require a new review session when upgrading from earlier tool versions.
+
 ## 0.1.1 — Released
 
 - Add contextual phrases, compound nouns, and potential and causative verb forms.

data/README.md

@@ -1,19 +1,20 @@
 ![](https://img.shields.io/badge/status-Work%20In%20Progress-8A2BE2)
 ![GitHub tag (latest SemVer)](https://img.shields.io/github/v/tag/cybergarage/asciidoc-pubkit)
 [![Gem Version](https://img.shields.io/gem/v/asciidoc-pubkit.svg)](https://rubygems.org/gems/asciidoc-pubkit)
+[![Build Status](https://github.com/cybergarage/asciidoc-pubkit/actions/workflows/test.yml/badge.svg)](https://github.com/cybergarage/asciidoc-pubkit/actions/workflows/test.yml)
 
 # asciidoc-pubkit
 
-A toolkit for authoring, reviewing, and publishing AsciiDoc books.
+A toolkit for authoring and reviewing AsciiDoc books.
 
-The initial release reviews Japanese running prose, generates contextual review
-prompts for coding agents, and checks edited manuscripts against a saved baseline.
+Version 0.6.0 provides shared Japanese technical writing criteria, an authoring
+prompt, contextual review prompts, and baseline verification for edited manuscripts.
 The CLI, diagnostics, documentation, and generated instructions are in English.
 Japanese text is retained in manuscript excerpts, rule dictionaries, and fixtures.
 
 ## Status
 
-This is an initial implementation. It does not invoke an AI service, automatically
+This release does not invoke an AI service, automatically
 rewrite manuscripts, or publish books. EPUB, image, and book scaffolding commands
 are planned extensions, not available features.
 
@@ -22,7 +23,15 @@ Starting with version 0.1.1, the default review backend requires the external Me
 command and a UTF-8 IPADIC dictionary. Node.js and textlint are not required.
 Explicit `--tokenizer literal` mode provides limited phrase matching without MeCab.
 
-Version 0.1.1 includes morphological analysis. Version 0.1.0 uses literal matching.
+Version 0.1.1 added morphological analysis. Version 0.1.0 used literal matching.
+
+The CLI has `writing` and `review` command groups. Both default to `--lang ja`.
+Language-specific criteria live under `data/writing/<language>/`; review rules
+use `data/review-rules.<language>.yml`. Writing and review have separate lists
+of supported languages, so a future writing language need not imply review
+support. Other languages are reserved for future implementations and now
+return an explicit error. A review session saves its language and the criteria
+used to generate its prompt.
 
 ## Install from RubyGems
 
@@ -38,6 +47,13 @@ Ruby 3.2 or later is required. RubyGems installs the required Ruby dependencies;
 no repository clone or Node.js installation is needed. MeCab and IPADIC must be
 installed separately when using version 0.1.1 or later in the default mode.
 
+Generate a writing prompt without an existing manuscript:
+
+```sh
+asciidoc-pubkit writing criteria --lang ja
+asciidoc-pubkit writing prompt --lang ja --output writing-prompt.md
+```
+
 Run the review workflow from your manuscript directory:
 
 ```sh
@@ -59,7 +75,7 @@ Add the gem to your project's `Gemfile` to manage its version with Bundler:
 
 ```ruby
 source 'https://rubygems.org'
-gem 'asciidoc-pubkit', '~> 0.1.1'
+gem 'asciidoc-pubkit', '~> 0.6.0'
 ```
 
 Then install dependencies and run the CLI through Bundler:
@@ -81,17 +97,64 @@ git clone https://github.com/cybergarage/asciidoc-pubkit.git
 cd asciidoc-pubkit
 bundle install
 gem build asciidoc-pubkit.gemspec
-gem install ./asciidoc-pubkit-0.1.1.gem
+gem install ./asciidoc-pubkit-0.6.0.gem
 asciidoc-pubkit --version
 ```
 
 The gem name and CLI name are `asciidoc-pubkit`; the Ruby require path is
 `asciidoc_pubkit`, and the namespace is `AsciidocPubkit`.
 
+## Writing commands
+
+`writing criteria` prints the packaged common criteria. `writing prompt` adds
+task instructions around those same criteria. Neither command needs an AsciiDoc
+file, a review session, MeCab, or network access. Both accept `--lang ja` and
+`--output FILE`; output defaults to stdout, and an existing output file is never
+overwritten. The prompt asks the agent to read project instructions and evidence;
+it does not supply source facts or authorize edits. Book-specific voice and
+format still come from the book. The OSS-only prose style profile remains with
+the book workflow, not the shared default.
+
+```sh
+asciidoc-pubkit writing criteria --lang ja
+asciidoc-pubkit writing prompt --lang ja --output writing-prompt.md
+```
+
+For example, `--lang en` exits with an unsupported-language error. No English
+review or writing criteria are shipped in 0.6.0.
+
 For a small trial, use `examples/book.adoc` as the scan input. Its Japanese
 paragraphs deliberately contain review candidates; its code block must remain
 unchanged.
 
+## Run from a local checkout
+
+Use the `run` Make target to execute the checkout without installing the
+asciidoc-pubkit gem. Ruby dependencies and, for the default tokenizer, MeCab and
+UTF-8 IPADIC must already be installed.
+
+```sh
+make run ARGS="--version"
+make run ARGS="review scan examples/book.adoc"
+make run ARGS='review scan "manuscripts/my book.adoc"'
+```
+
+With no `ARGS`, `make run` displays CLI help. Set `RUBY` to choose another Ruby
+executable. `ARGS` is shell command-line text; quote paths containing spaces and
+use only trusted arguments.
+
+To run from a manuscript directory, select the checkout's Makefile with `-f`.
+Relative manuscript paths and output paths remain relative to your current
+working directory:
+
+```sh
+make -f "$HOME/Src/asciidoc-pubkit/Makefile" run ARGS="review scan book.adoc"
+```
+
+Use `ARGS` instead of `make review scan book.adoc`: Make interprets positional
+words as build targets, not CLI arguments. Avoid `make -C` when manuscript paths
+should remain relative to the current directory, because it changes directories.
+
 ## Install the morphological analyzer (0.1.1 and later)
 
 On macOS with Homebrew:
@@ -134,7 +197,7 @@ asciidoc-pubkit review verify .pubkit/review --output verification.json
 ```
 
 All three commands leave manuscript files unchanged. Only the agent edits them.
-Output paths must not already exist. Use a new session directory for a new pass.
+`prompt` and `verify` output files must not already exist.
 Without `--output`, `prompt` writes Markdown and `verify` writes JSON to stdout.
 `scan` defaults to `.pubkit/review` and prints a short summary.
 
@@ -146,6 +209,27 @@ asciidoc-pubkit review scan chapter.adoc --style desu-masu
 asciidoc-pubkit review scan book.adoc --attribute edition=print --base-dir .
 ```
 
+If the session directory already exists, an interactive terminal asks
+`Replace it? [y/N]`. Only `y` or `yes` (case-insensitive) replaces it; any other
+answer or end of input cancels with exit status 2. Replacement resets the review
+baseline and removes old session contents. Use a different `--output` path to
+keep the previous review pass. The old session remains intact if scanning fails
+before the replacement is installed.
+
+For batch execution:
+
+```sh
+# Answer yes automatically and replace an existing review session.
+asciidoc-pubkit review scan book.adoc --yes  # short form: -y
+# Never ask; exit with status 2 if the output already exists.
+asciidoc-pubkit review scan book.adoc --no-input
+```
+
+Non-terminal stdin also disables prompting. `--yes --no-input` permits
+replacement without reading stdin. These options apply to `scan` only;
+regular files, symlinks, directories without a review session layout, and
+sessions containing the current manuscript sources cannot be replaced.
+
 An entrypoint or a standalone chapter can be scanned. Includes and conditionals
 are processed by Asciidoctor. Match the publishing build's attributes and base
  directory to review the intended edition. `--only` selects one included source
@@ -184,13 +268,24 @@ asciidoc-pubkit review prompt .pubkit/review --mode diagnose
 for findings and proposed revisions without editing. Both modes require the agent
 to distinguish **revise**, **keep**, and **needs-evidence** decisions.
 
-The Markdown includes every selected paragraph, neighboring selected paragraphs,
-heading context, candidates, saved settings, and preservation instructions. It
-also asks for contextual review of paragraphs with no machine matches. Initial
+The single Markdown output includes every selected paragraph once, in document
+order, with the shared criteria saved at scan time, candidates, saved settings,
+and preservation instructions. Paragraph
+text uses fenced text blocks; metadata uses compact JSON. File and heading context
+is shared by consecutive paragraphs, and candidates inherit their file and
+paragraph ID. Adjacent entries provide neighboring context without repeating text.
+The prompt asks the agent to read manageable ranges with neighboring paragraphs
+at boundaries and track completed paragraph IDs and candidate decisions. It also
+requires review of paragraphs with no machine matches. Large manuscripts can
+still exceed a context window if the entire prompt is loaded at once. Initial
 support is for local prose correction, not chapter reorganization.
 
 Source hashes are checked before generating a prompt. Modified sources, modified
 session artifacts, and incompatible session versions require a fresh scan.
+`review scan`, `review prompt`, and `review verify` accept `--lang ja`; prompt and
+verify check the value against the session language. A non-Japanese language in
+`--lang`, `review.language`, or an explicit AsciiDoc `:lang:` attribute is rejected.
+An omitted `:lang:` attribute uses the selected review language.
 
 ### Verify
 
@@ -268,16 +363,17 @@ use an absolute path for an explicit executable override.
 | --- | --- | --- |
 | `abstract-reference` | hint | Ask what an abstract noun refers to |
 | `weak-predicate` | hint | Ask whether an operation's purpose or result is clear |
-| `contextual-phrase` | hint | Review referents, assumptions, and qualifications while preserving negation |
-| `generic-framing` | hint | Review generic introductions and emphasis |
+| `contextual-phrase` | hint | Check whether a qualification changes interpretation or action; preserve necessary negation |
+| `generic-framing` | hint | Check whether an introduction or recap adds a claim, scope, or consequence |
 | `vague-degree` | hint | Ask what depth, level, scope, or comparison is intended |
 | `repeated-ending` | info | Identify three consecutive sentences with the same detected ending |
 | `glossary-variant` | warning | Identify project-specific terminology variants |
 | `style-candidate` | hint | Check selected polite/plain endings against an explicit style |
 
 MeCab mode matches noun and adjective tokens and dictionary forms of verbs.
-Sahen predicates are matched as a noun followed by the verb for "do"; standalone
-sahen nouns are not treated as verbal predicates. Auxiliary sequences retain
+Sahen predicates are matched as a noun followed by `する` or the potential
+`できる`; standalone sahen nouns are not treated as verbal predicates. A configured
+sahen predicate takes precedence over a matching standalone noun rule. Auxiliary sequences retain
 negation, past tense, passive forms, and progressive forms in the reported surface.
 The added reach predicate is negative-only; the existing handling predicate is
 reviewed in both affirmative and negative forms. Glossary variants and generic
@@ -286,6 +382,37 @@ literal matching and suppress overlapping morphological candidates. Compound
 nouns are matched across adjacent noun tokens. Selection and narrowing verbs
 include potential forms; predicate surfaces also preserve causative auxiliaries.
 
+Default terms group components, actors, relationships, and resources under
+`abstract-reference`; operations under `weak-predicate`; and compressed noun
+relationships, referents, sufficiency, and negative qualifications under
+`contextual-phrase`. `木` and `余白` invite a context-dependent katakana terminology
+review, not mandatory replacement. `明示選択` and `欠落理由` invite checking whether
+`明示的選択` and `欠落した理由` clarify the intended relationship. Shared phrases such
+as `ではありません` cover longer qualifications without listing every sentence.
+`generic-framing` also flags `このように` and `要するに` as possible recaps.
+These are candidates for contextual review, not banned expressions. A necessary
+condition, uncertainty, or distinction must survive a revision; a redundant
+disclaimer can instead be removed or folded into a more precise main claim.
+
+### Editorial sources for the shared criteria and default candidates
+
+The shared criteria and default questions draw on [natural-japanese](https://github.com/coji/natural-japanese)
+for separating mechanical detection from contextual judgment and for spotting
+repetitive framing; [日本語技術文書の文章規範](https://gist.github.com/k16shikano/fd287c3133457c4fd8f5601d34aa817d)
+for paragraph logic, evidence scope, and preserving meaningful uncertainty; and
+[AI臭い文章とは何なのか](https://speakerdeck.com/nasuvitz/ai-kusai-bunshou-toha-nanina-no-ka)
+for the examples of unnecessary contrast, abstract referents, and paired short
+sentences. These sources differ on stylistic choices such as whether a heading
+should state its conclusion. The packaged rules therefore report candidate
+phrases and leave document structure, genre conventions, and final edits to the
+reviewer.
+
+Literal term matching suppresses matches strictly contained in a longer matched
+term, across categories. The longer term also suppresses contained matches when
+it is allowed; separate occurrences remain candidates. Glossary and style checks
+are independent. In MeCab mode, predicates outside a contextual phrase can still
+be reported separately.
+
 Morphological candidates include `lemma`, `part_of_speech`, `negative`, and
 `detector` alongside the original `match`, line, and column. Negation detection
 covers common IPADIC negative auxiliaries; it is not full semantic analysis of
@@ -298,12 +425,12 @@ reports analyzer changes instead of treating results from different dictionaries
 as directly comparable. Prompt generation uses saved evidence and does not need
 MeCab. Changed rules or dictionary settings require a new scan.
 
-Sessions from 0.1.0 are not compatible with 0.1.1. Keep the original baseline for
+Sessions from earlier tool versions are not compatible with 0.6.0. Keep the original baseline for
 an ongoing review and finish it with the original version, or start a new review
 pass in a different directory:
 
 ```sh
-asciidoc-pubkit review scan book.adoc --output .pubkit/review-0.1.1
+asciidoc-pubkit review scan book.adoc --output .pubkit/review-0.6.0
 ```
 
 Severity describes review priority, not proof of an error. There is no AI-authorship
@@ -341,3 +468,69 @@ GitHub Actions is configured for Ruby 3.2, 3.3, 3.4, and 4.0 on Linux.
 Copyright 2026 CyberGarage.
 
 Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE).
+
+## Customize review rules
+
+The UTF-8 YAML file [`data/review-rules.ja.yml`](data/review-rules.ja.yml) is
+included in the gem and loaded by default. Edit that file when running a local
+checkout, or copy it to a project-owned file for custom rules. No Ruby changes
+are required to update candidate terms.
+
+```sh
+asciidoc-pubkit review scan book.adoc --rules ./review-rules.yml
+make run ARGS="review scan book.adoc --rules ./review-rules.yml"
+```
+
+For an installed gem, copy the default file with:
+
+```sh
+ruby -rasciidoc_pubkit -e 'puts File.read(AsciidocPubkit::RuleSet::DEFAULT_PATH)' > review-rules.yml
+```
+
+Alternatively, configure a path in `.asciidoc-pubkit.yml`:
+
+```yaml
+review:
+  rules: review-rules.yml
+```
+
+Precedence is `--rules`, then `review.rules`, then the packaged default.
+CLI paths are relative to the current working directory; configuration paths
+are relative to the configuration file. A custom file replaces the entire rule
+set; it is not merged with defaults. Start by copying the standard file.
+
+### Rule file format (schema version 1)
+
+All top-level fields below are required. Unknown keys and invalid types are
+rejected. YAML aliases and object tags are not supported.
+
+| Field | Format and behavior |
+| --- | --- |
+| `schema_version` | Integer `1` |
+| `terms` | Mapping containing all five categories listed below |
+| `verbs` | Mapping from canonical verb forms to nonempty arrays of MeCab/IPADIC dictionary forms; each dictionary form belongs to only one canonical form |
+| `sahen` | Array of nouns matched with a following `する` or potential `できる` verb |
+| `negative_only` | Array of canonical predicates restricted to negative forms; use the noun plus `する` for sahen predicates |
+| `compound_nouns` | Array of terms matched across contiguous noun tokens; each must also appear in `abstract-reference.terms` |
+
+Each `terms` category must contain `terms` (an array of unique nonempty strings)
+and `question` (a nonempty review instruction string). The required categories
+are `abstract-reference`, `weak-predicate`, `vague-degree`, `contextual-phrase`,
+and `generic-framing`. Empty term arrays disable that category's literal
+candidates. Empty `verbs`, `sahen`, and `compound_nouns` collections disable their
+respective morphological matchers. Keep `negative_only` consistent with the
+configured predicates.
+
+In literal mode, all category term lists use exact phrase matching. In MeCab
+mode, abstract nouns and degree adjectives use dictionary forms, while predicates
+use `verbs` and `sahen`; add a predicate's desired literal surface to
+`weak-predicate.terms` as well if literal mode should detect it. Contextual and
+generic framing phrases use literal matching in both modes. Questions apply to
+both detectors. Glossary, style, repeated-ending checks, inline exclusions, and
+morphological suffix handling remain implemented in Ruby.
+
+A scan saves the resolved rule contents and source path in `manifest.json`.
+Prompt generation and verification use the saved contents, even if the original
+YAML file is subsequently edited or removed. Start a new session to apply rule
+changes. Older sessions without a rule snapshot fall back to the currently
+installed default file; start a new session for reproducible custom-rule reviews.

data/data/review-rules.ja.yml

@@ -0,0 +1,271 @@
+---
+schema_version: 1
+terms:
+  abstract-reference:
+    terms:
+    # Concepts, evidence, and explanatory frames.
+    - 契約
+    - 観点
+    - 意図
+    - 役割
+    - 根拠
+    - 概念
+    - 記述
+    # Components, actors, and hierarchical relationships.
+    - 構成要素
+    - 部品
+    - 開発者
+    - 祖先
+    - 子孫
+    # Scope, separation, and organization.
+    - 境界
+    - 土台
+    - 橋渡し
+    - 入口
+    - 場所
+    - 一続き
+    - 区別
+    - 単発
+    - 別枠
+    # Resources and preparation.
+    - コスト
+    - 予算
+    - 準備
+    # Review context before choosing a katakana technical term.
+    - 木
+    - 余白
+    question: Identify the concrete referent, components, or measurable work. Keep
+      established technical meanings. For 木 and 余白, consider a context-appropriate
+      katakana term (such as ツリー or マージン) only when it names the intended concept.
+  weak-predicate:
+    terms:
+    # Use, interpretation, and understanding (literal-mode surfaces).
+    - 利用します
+    - 扱います
+    - 扱いません
+    - 意味しません
+    - 把握します
+    - 捉えます
+    # Writing, representation, and inspection.
+    - 記述します
+    - 記述できます
+    - 書きます
+    - 示します
+    - 表します
+    - 表しません
+    - 読みます
+    - 調べます
+    - 調べられます
+    - 確かめます
+    - 探します
+    - 追えます
+    # Construction, preparation, and combination.
+    - 用意します
+    - 作ります
+    - 組み立てられます
+    - 組み合わせます
+    - 成り立たせています
+    # Organization, comparison, and selection.
+    - 整理します
+    - 分ける
+    - 分けて
+    - 分けています
+    - 分けません
+    - 分けられます
+    - 区別します
+    - 区別できます
+    - 混同しません
+    - 混ぜません
+    - そろえます
+    - そろいます
+    - まとまっています
+    - 選びます
+    - 選べます
+    - 絞れます
+    - 決まります
+    # Change, transfer, and retention.
+    - 変わります
+    - 書き換える
+    - 置き換えます
+    - 加えます
+    - 加わります
+    - 付けます
+    - 返す
+    - 返します
+    - 渡します
+    - 送れます
+    - 残します
+    - 持ちます
+    - 消しません
+    # Existence, sufficiency, requirements, and completion.
+    - あります
+    - 足りません
+    - 求めます
+    - 到達しません
+    - 避けられます
+    - 終えられます
+    - 抜けられます
+    - 解消する
+    question: Check whether the purpose, operation, or result is clear from the surrounding
+      paragraph. Preserve negation and conditions.
+  vague-degree:
+    terms:
+    - 浅い
+    - 深い
+    question: Identify the concrete depth, level, scope, or comparison. Keep literal
+      measurements and established technical meanings.
+  contextual-phrase:
+    terms:
+    - これらを
+    - であることだけでは
+    - あるものとします
+    # Retain this specific phrase for existing allow lists and fuller evidence.
+    - わけではありません
+    - 別です
+    # Compressed noun relationships; suggestions are not automatic replacements.
+    - 明示選択
+    - 欠落理由
+    # Referents, separation, evaluation, and sufficiency.
+    - よいこと
+    - おそれ
+    - 別の
+    - 別に
+    - 空の
+    - 別々に
+    - ことだけで
+    - 目安です
+    - 必要がありません
+    # Shared qualifications cover longer expressions without enumerating them.
+    - ではありません
+    - にはなりません
+    - にはできません
+    - にはしません
+    - ことはしません
+    - 代用にしません
+    - でもありません
+    - してはいけません
+    - 表してはいません
+    question: Check whether the phrase adds a condition that changes the reader's
+      interpretation or action. If it only denies an overbroad reading already
+      excluded by the main claim, revise that claim or remove the qualification.
+      Preserve necessary negation, uncertainty, and technical boundaries. For
+      明示選択 and 欠落理由, consider making the relationship explicit (明示的選択 and
+      欠落した理由) if that preserves the meaning.
+  generic-framing:
+    terms:
+    - 重要なのは
+    - ポイントは
+    - 本章では
+    - ここでは
+    - まとめると
+    - このように
+    - 要するに
+    question: Check whether this opening or recap adds a claim, scope, or consequence
+      beyond the surrounding prose. Keep useful framing; otherwise state the
+      substantive claim directly. Do not force a uniform sentence pattern.
+verbs:
+  扱う:
+  - 扱う
+  示す:
+  - 示す
+  変わる:
+  - 変わる
+  分ける:
+  - 分ける
+  そろえる:
+  - そろえる
+  - 揃える
+  まとまる:
+  - まとまる
+  - 纏まる
+  加える:
+  - 加える
+  探す:
+  - 探す
+  そろう:
+  - そろう
+  - 揃う
+  選ぶ:
+  - 選ぶ
+  - 選べる
+  成り立つ:
+  - 成り立つ
+  確かめる:
+  - 確かめる
+  書き換える:
+  - 書き換える
+  絞る:
+  - 絞る
+  - 絞れる
+  渡す:
+  - 渡す
+  決まる:
+  - 決まる
+  組み立てる:
+  - 組み立てる
+  組み合わせる:
+  - 組み合わせる
+  足りる:
+  - 足りる
+  置き換える:
+  - 置き換える
+  加わる:
+  - 加わる
+  返す:
+  - 返す
+  避ける:
+  - 避ける
+  求める:
+  - 求める
+  送る:
+  - 送る
+  - 送れる
+  読む:
+  - 読む
+  付ける:
+  - 付ける
+  残す:
+  - 残す
+  持つ:
+  - 持つ
+  表す:
+  - 表す
+  終える:
+  - 終える
+  消す:
+  - 消す
+  調べる:
+  - 調べる
+  作る:
+  - 作る
+  抜ける:
+  - 抜ける
+  捉える:
+  - 捉える
+  書く:
+  - 書く
+  混ぜる:
+  - 混ぜる
+  追う:
+  - 追う
+  - 追える
+  ある:
+  - ある
+sahen:
+- 利用
+- 整理
+- 把握
+- 到達
+- 意味
+- 記述
+- 用意
+- 区別
+- 解消
+- 混同
+negative_only:
+- 到達する
+- 意味する
+compound_nouns:
+- 一続き
+- 開発者
+- 構成要素