What success looks like
A finished first run leaves a local commit on the factory branch and a SUMMARY.md.
A finished first run leaves a local commit on the factory branch and a SUMMARY.md. Kusaw never pushes or merges; merging is yours.
Run states
A successful run moves through these states, in order:
queued— the task is on the factory queue.running— a worker has the run and is executing pipeline steps.waiting_for_human— a gate is waiting for approve or reject. The default pipeline has no gate, so a first run may skip this state.succeeded— the pipeline finished and the local commit is in your repo.
Other endings:
failed— a pipeline step did not pass. See Rerun, requeue, resume or steer and Find your message.needs_attention— the run stopped in a state a person has to look at, for example a loop that gave up. See Rerun, requeue, resume or steer and needs_attention after the loop limit.stopped— a person or the watchdog halted the run. You can requeue, restart, or dismiss it. See Rerun, requeue, resume or steer.rejected— a step or a person rejected the work. A rejected run can't be requeued; add the task again withkusaw add.
Where the result is
The delivered commit is on the factory branch in your repo, not on main. Look at it with git log and git show. SUMMARY.md is the delivery note for that run.
The factory never pushes or merges. You merge when you are ready.
Logs and artifacts
Logs and artifacts are on the run page in the Dashboard and in kusaw runs show <run>. On disk, each attempt keeps stdout.jsonl and stderr.log under <data_dir>/runs/<run>/attempts/.
The logs of kusaw serve, kusaw ui, and kusaw up themselves are under <user config dir>/kusaw/logs (~/.config/kusaw/logs on Linux). Print them with kusaw logs serve, and add -f to follow.
Next steps
- Concepts — factories, tasks, steps, pipelines, and runs.
- Write a good task — scope, repos, and Verification commands.
- Review and approve a run — add a gate and decide on the result.
- Custom steps — add your own pipeline steps or replace a built-in.