Standalone Client
The primary execution environment for azuma nori is the Standalone Client—a desktop application that bundles the execution engine, orchestrator, and an interactive UI.
Bundled Engine Architecture
When you run an analysis through the Standalone Client, the desktop app acts as the front-end interface, but it natively bundles the full azuma nori execution engine.
- Orchestration: The client spawns the internal orchestrator, which manages the sub-agents and the final summarization step locally on your machine's CPU.
- UI Context: The UI handles the complexity of generating the execution payload automatically, removing the need for manual JSON scaffolding.
- Data Sovereignty: Despite the rich interface, no source code is ever uploaded. The bundled engine reads files directly from your workstation's disk.
Workspace Layout
The Standalone Client relies on a clear separation of data on your local filesystem:
- Root Directory: The folder containing your proprietary source code. The engine reads this directory but never writes to it.
- Data Directory (
.nori): The secure, isolated storage path where nori keeps its state.
Inside the .nori Directory
Your chosen .nori workspace contains several critical artifacts:
config.json: The active configuration snapshot mapping your project settings, policies, and LLM providers.cache/: Stores the intermediate LLM outputs and JSON findings from the latest run, enabling the "Skip Existing" resumability feature.wiki/: Contains the generated Markdown indices of your codebase, heavily optimizing the prompt tokens sent to the LLM during evaluation.exports/: The default output directory for generated PDF and HTML reports.
Segregation Required
Always ensure your .nori directory is kept completely separate from your codebase's Root Directory. Placing .nori inside your source tree may cause the engine to recursively scan its own caches and outputs.