CLI reference
Initialize projects, validate configuration and rules, diagnose local logs, inspect reports, confirm resolutions, search memory, and inspect plugins.
Commands
| Command | Purpose |
|---|---|
| lumis init | Create a minimal Project and rule set without overwriting existing files. |
| lumis doctor | Validate config, rules, paths, and safe defaults without writing state. |
| lumis diagnose | Diagnose a bounded local log; write a report and incident memory. |
| lumis report | Print a stored report and any human-confirmed resolution. |
| lumis resolve | Store a human-confirmed resolution and change truth state. |
| lumis memory search | Search local incident memory with transparent keyword scoring. |
| lumis rules validate | Validate rules and show stable IDs, versions, and priorities (supports --json). |
| lumis rules test | Evaluate one rule against a JSON fixture and emit CI-friendly JSON. |
| lumis plugins list | Show discovered plugin metadata without importing plugin code (supports --json). |
| lumis plugins doctor | Check plugin manifests and compatibility without loading anything (supports --json). |
| lumis config migrate | Validate an alpha document and emit its stable lumis.dev/v1 equivalent, never overwriting output by default. |
Command safety and stability
doctor, rules validate, rules test, config migrate, and the plugins commands make no network calls and write no incident state. diagnose writes only to explicitly configured local report and memory paths. Model assistance remains inactive unless application code supplies both an enabled policy and a gateway adapter—no CLI flag can turn a model on.
Command names, exit-code classes, and the documented machine-readable JSON output of rules validate, rules test, plugins list, and plugins doctor are part of the stable 1.x surface; human-oriented prose may improve without a major release.