Plan a large scan

mori plan is available in Mori v0.34.0 or later.

Use mori plan before a large scan to understand its comparison workload:

mori plan --profile review --fragment-selection production .
mori plan --profile review --fragment-selection production packages/api

Planning discovers and parses the selected source, then counts eligible candidate pairs without calculating similarity scores. It uses the same language, token, size, ignore and fragment-selection rules as a scan. It succeeds when the count exceeds --max-pairs and reports that condition so you can narrow the scope. It still takes time to parse source and enumerate candidates.

The output groups selected files by apps/<name>, packages/<name>, or their first directory. Per-root pair counts are upper bounds before language, size and overlap filtering. They are not the results of independent package scans. Separate package scans omit cross-package matches. A named scope pointing at . does not narrow the workload. Use concrete roots in a named scope or command when that tradeoff fits your review.

The plan shows effective configuration, coverage, warning and parse-diagnostic counts. Coverage policies still apply. No similarity findings are produced, baselines are not loaded, and finding-based exit policies are not evaluated. A successful plan never certifies a clean review. It cannot be used to accept baseline identities or issue a review receipt. Source changes require a new plan.

Machine-readable plans

mori plan --format json --redact-paths --scope product

The separate mori-scan-plan artifact uses schema 1, published in mori-scan-plan-v1.schema.json. analysis_performed is always false, meaning no similarity analysis was run. candidate_pairs is the eligible whole-selection count, and exceeds_pair_limit compares it with the effective configured cap.

Only text and JSON formats are supported. Planning does not support staged or focused input, diagnostic exports, receipts or report-output files. Without --parse-cache it writes only to standard output and standard error. Managed project compatibility checks still apply. Ordinary output includes source/configuration paths, so use --redact-paths when appropriate and inspect output before sharing.

Reuse parsing between commands

Explicitly enable local parsing reuse on both commands:

mori plan --parse-cache --profile review --fragment-selection production .
mori scan --parse-cache --profile review --fragment-selection production .

Mori still discovers files and reads current source bytes on every invocation. Cached extraction is bound to those bytes, paths, language, extraction settings, and the exact executable. Scoring, ranking, candidate limits, coverage policies and baseline validation run normally. A plan is never reused as acceptance or proof of a clean scan. Changes to ignores or roots are applied by fresh source discovery before any cached extraction is considered.

The opt-in cache stores normalized features, fragment locations, literal hashes and diagnostics under the platform user cache directory at mori/parse-cache-v1. It does not store source text or upload anything. Treat this local metadata as private. Entries are authenticated and stored with private permissions outside the current working directory and selected source roots. Each of 1,024 slots holds at most 256 KiB, with one bounded pending file per slot during writes. Collisions, oversized entries, corruption, unavailable storage and concurrent writes can cause cache misses. A miss falls back to normal parsing and does not alter policy.

The flag is off by default and does not persist in project configuration. Omit it to stop using the cache. Delete that Mori cache subdirectory to remove its local entries. This is separate from staged review's --cache, which reuses an authenticated complete report for an unchanged immutable index snapshot.