Audit Artifacts

Understanding the generated artifacts, patches, and metrics in .niki/.

Task output is organized under .niki/tasks/<task-id>/. A typical completed run contains:

.niki/tasks/6d281d6d-3184-482a-89aa-403332152861/
├── artifacts/
│   ├── planner.json          # TaskSpec
│   ├── coder.json            # CodeDiff and rationale
│   ├── tester.json           # Analytical TestReport
│   ├── reviewer.json         # Review verdict
│   └── test_execution.json   # Only when a test command resolves
├── changes.patch             # Published unified diff
├── dashboard.html            # Static review dashboard
├── manifest.json             # Provenance when snapshots are enabled
├── report.md                 # Human-readable run report
├── safety_proof.json         # Git invariants; only for an eligible non-empty branch
├── task.json                 # Persisted task record
└── trace.jsonl               # Derived run spans

Repeated role attempts are retained as coder-2.json, coder-3.json, and so on. safety_proof.json is Git-only and is not a sandbox proof. plan.md is present for dry-run/plan output, which creates no branch.

All files under the task directory are excluded from the published diff. Snapshot retention defaults to 14 days, then prunes old task directories.

Inspecting Artifacts

You can inspect the generated files with any standard JSON tool, or use the built-in NIKI commands:

# Print formatted report
niki report <task-id>

# Generate the static dashboard and print its path
niki dashboard --task <task-id>