ghola
A starter kit for agentic systems on iii: a spec goes in, a pull request comes out, nothing merges itself. The stage-graph factory, the constraint ladder and the append-only audit log, wired as registry workers, with the operator profile and skills to run them.
# With the iii engine running
iii trigger directory::download-kit kit=tacoda/ghola@0.1.0Exact versions are immutable. Every profile and skill is stored by its SHA-256, so updates show exactly what changed.
- Skill ID
tacoda/ghola/index- Used by
- ghola
Skill
2,082 bytesghola
ghola
A starter kit for agentic systems on iii. A spec goes in, a pull request comes out, nothing merges itself.
Two halves, and the split is the point:
- The harness constrains one turn: six phases, four callbacks around the turn, the constraint ladder deciding what a rule refuses, in the rule's own words.
- The factory runs many turns to a diff: a stage graph where every transition is a durable queue message, a worktree per job, a delivery gate over the finished diff, then a pull request.
It works before you configure anything: a fresh clone runs the whole lifecycle
on built-in defaults with an empty settings/. Changing it is a key in a YAML
file, or a Python file dropped into a named directory and found by its filename.
The three steps
1. clone the repo git clone … && cd ghola && make setup
2. add config and scripts edit settings/, drop files in actions/ (optional)
3. tell it to do work make submit SPEC=specs/x.md REPO=../repoOperator commands
| command | what it is |
|---|---|
make setup / make doctor |
toolchain, credentials, target repos |
make up / make down / make status / make logs |
the whole project: engine, registry workers, ghola's own |
make submit SPEC=… REPO=… |
one job from one spec |
make turn PHASE=… PROMPT=… |
one phase as a turn, no factory |
make jobs / make pipeline |
the jobs, and the stage graph before you pay for one |
make audit |
the append-only record: intact? and what it says |
make improve / make proposals / make accept |
what went wrong, what would have helped, staged proposals |
make test |
the pure and worker tests. Seconds, no engine, no money |
make call FN=… [JSON=…] |
any function on the running engine |
make config |
every effective setting, tagged with where it came from |
make console |
the console URL |
---title: gholadescription: Overview of ghola — what the factory is, the three-step usage, and the operator commands. The skill agents load first.--- # ghola A starter kit for agentic systems on [iii](https://iii.dev). A spec goes in, apull request comes out, nothing merges itself. Two halves, and the split is the point: - **The harness** constrains one turn: six phases, four callbacks around the turn, the constraint ladder deciding what a rule refuses, in the rule's own words.- **The factory** runs many turns to a diff: a stage graph where every transition is a durable queue message, a worktree per job, a delivery gate over the finished diff, then a pull request. It works before you configure anything: a fresh clone runs the whole lifecycleon built-in defaults with an empty `settings/`. Changing it is a key in a YAMLfile, or a Python file dropped into a named directory and found by its filename. ## The three steps ```1. clone the repo git clone … && cd ghola && make setup2. add config and scripts edit settings/, drop files in actions/ (optional)3. tell it to do work make submit SPEC=specs/x.md REPO=../repo``` ## Operator commands | command | what it is ||---|---|| `make setup` / `make doctor` | toolchain, credentials, target repos || `make up` / `make down` / `make status` / `make logs` | the whole project: engine, registry workers, ghola's own || `make submit SPEC=… REPO=…` | one job from one spec || `make turn PHASE=… PROMPT=…` | one phase as a turn, no factory || `make jobs` / `make pipeline` | the jobs, and the stage graph before you pay for one || `make audit` | the append-only record: intact? and what it says || `make improve` / `make proposals` / `make accept` | what went wrong, what would have helped, staged proposals || `make test` | the pure and worker tests. Seconds, no engine, no money || `make call FN=… [JSON=…]` | any function on the running engine || `make config` | every effective setting, tagged with where it came from || `make console` | the console URL |