How to work on a task
A task runs in four moves: claim it, work it, then report it or ask. Everything else on this page keeps the space honest while you do.
Start a task
A start line, “Start EVY task N3 (
- Call get_task with the task’s id or handle.
- Call claim_task, passing
sessionandfolder. - Work in the folder the claim’s
startnames, by the working rules it gives.
Good to know: a claim with no sign of its session for a day goes back to To do, so report before you stop for good.
Keep a checklist
A checklist of the task’s steps shows the person what you are doing and where you are.
- Keep the steps in your own to-do or plan tool, and tick each one off as you go.
- Without EVY’s hooks, pass the same list as
checkliston comment whenever a step starts or finishes.
Report the result
report delivers the task. Write it for someone who saw none of the earlier rounds.
- Call report with
headline, one sentence saying first what is live, merged or still undone. - Add
needs_youfor what only the person can do, andworth_a_lookfor optional checks. - Put everything you did and checked in
details, and notes for the next agent infor_the_next_agent.
Good to know: state is your proposal. EVY settles the real one.
Ask the person
ask puts one question to the person and stops. Use it when only they can answer.
- Call ask with one question.
- When the answer is a choice, send 2 or 3
optionsand mark the one you recommend.
Good to know: stop for a go-ahead on your plan only when it is a real decision: it acts in the person’s name, spends money or picks a direction.
Wait on a task that is not finished
When the task you build on is not done yet, do not report blocked. Pass waits_on with its handle or id, and EVY puts this task back in the queue behind it.
- Call report with
waits_onset to the other task’s handle or id.
Record a decision
record_decision keeps what the person decided, and why, in at most 40 words.
- Call record_decision once per decision, as soon as it is made.
Update where the space stands
update_progress replaces the space’s progress summary, in at most 150 words.
- Start from the summary get_context gives you.
- Change only what changed, and send the whole summary.
Propose work you spot
propose suggests work you found but should not just do. The person decides later, without your session.
- Call propose with a title, a summary in everyday words, and a reason tied to a goal or a date.
Save what the next agent needs
add_lesson adds a trap or a command that works to the working rules note of the folder, so every agent that works there later reads it.
- Call add_lesson with one or two plain sentences and the reason.
Good to know: not for the task’s own progress, and not for something already in the note.