Gated workflow
A story or task moves through a lifecycle of steps. Each forward transition is judged by an isolated reviewer before it is enacted, so quality is managed at the boundary rather than asserted by the executor.
satelle.
Local-first substrate for agent-driven work.
satelle governs the authored process — stories, tasks, an evidence ledger, and authored markdown (documents, workflows, principles, skills) — backed by a per-repo SQLite database. Work moves through a gated workflow: the agent executes; isolated reviewers gate every status change.
Runs 100% locally · a single static binary · no server · no cgo
How it works
Executor & reviewer
Two actors. The executor does the work and mutates the repository. The reviewer is an isolated, read-only judge that returns one verdict — accept or reject with notes — and never mutates the tree.
Status is the proof of done
A status advances only through a reviewer’s accept, and always
through it. done is the terminal success state, reached only
when every gate on the path has accepted.
Evidence ledger
Every transition writes to an append-only ledger — the verdict, the
actor, the step — so the history of how work reached done
stays auditable.
Authored substrate
Process lives in markdown committed to git: workflows (the lifecycle graph), skills (reviewer rubrics or functional checks), principles (the guardrails the agent reads), and documents. The binary runs the process; it never contains it.
Local-first
A single static binary backed by a per-repo SQLite database. No server, no cgo. The OSS tier runs 100% locally.