Mori documentation

Start with the guide that matches what you are trying to do.

Learn Mori

Choose a useful first review: library scopes, test noise, and checking that useful matches remain.
Getting started — install, first scan, profiles, and coverage checks.
Reviewing results — selection, focus, prioritization, statement blocks, and source inspection.
How scoring works — normalization, feature bags, similarity, identities, and explanatory evidence.

Support reports: capture, inspect and voluntarily share diagnostics without including source.
Project configuration — every .mori.json field and ignore-file behavior.
SQL and embedded SQL — generic SQL, PostgreSQL, and opt-in embedded queries.
Automation and baselines — coverage policy, changed-file focus, CI exits, and reviewed suppression.
Editors and coding agents — SARIF, unsaved-buffer overlays, VS Code, and the bundled Agent Skill.
Project contract and upgrades — managed-asset compatibility, safe migration, and the stable pre-commit adapter.

Mori's results are structural review evidence. They do not prove semantic or behavioral equivalence, defects, or that a refactor is safe.