Repository navigation
v0.3.0
A tiered task dispatcher: a packet goes to the cheapest tier that fits, runs in an isolated worktree, is judged by its verifier, escalates with the verifier's own words, and lands unstaged when it passes.
- Packets, verified worktree runs, the escalation ladder, a SQLite run log and an HTTP daemon.
- Claude Code headless as a tier worker, beside the other runners.
- Fail-over inside a tier when a provider never starts or produces nothing, with error lines picked as the reason; infrastructure errors stay out of the stats; a clean exit with no changes counts as a failure.
serve.enventries are exported to workers so the daemon can reach cloud tiers.- The capabilities say what each class decides (tier, ceiling, verify, attempts) and what conserve and rush do to the ladder.
- The daemon trusts the tailnet the way the bridges do: a peer on the tailnet or loopback needs no password, everyone else still does, and the capabilities say which mode is on.