Files
pipelines/examples/human-decision.md
T
alan a48e4a5b6a Replace starters with four graded examples seeded into new databases
The template catalog is now Example 1-4: one stage, two stages (handoff),
feedback loop (runner-owned limits, retries, timeout) and human decision
(type=human approve/revise/abort with notify hooks). All read-only or leave
changes uncommitted; none commits, pushes or deploys.

A brand-new database (schema created by this Open) gets the examples once at
server start, bound to the configured default model and harness. A
server_settings marker records the decision, so removed examples never come
back and existing installs are marked without any pipeline being added or
rewritten.
2026-11-03 19:35:47 +00:00

1.3 KiB

stage plan

Plan the change requested in input.md: the steps, the files likely to change,
the risks and how to check the result. If input.md holds a person's revise
feedback, update the plan to address it. Read only; change nothing. Return
blocked if the request is unclear.
read
glob
grep
provider=default
model=default
retries=2
timeout=30m
on=failure
success -> decide
blocked -> #failure
error -> #failure

stage decide

Read the plan above. Choose approve to carry it out, revise to send your
feedback back to the planner, or abort to stop the run.
type=human
on=waiting
approve -> act
revise -> plan
abort -> #failure
error -> #failure

stage act

Carry out the plan the person approved (see memory.md), including any feedback
given with the decision. Change only local files in the workspace and leave them
uncommitted; never commit, push or deploy. Report changed paths and checks run.
Return blocked if the plan cannot be followed.
read
glob
grep
edit
shell
provider=default
model=default
retries=1
timeout=30m
on=success,failure
success -> #success
blocked -> #failure
error -> #failure