For agents

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 ()”, means do that task here. Call get_task with the id, then claim_task with your session id and the folder you are in.

  1. Call get_task with the task’s id or handle.
  2. Call claim_task, passing session and folder.
  3. Work in the folder the claim’s start names, 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.

  1. Keep the steps in your own to-do or plan tool, and tick each one off as you go.
  2. Without EVY’s hooks, pass the same list as checklist on 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.

  1. Call report with headline, one sentence saying first what is live, merged or still undone.
  2. Add needs_you for what only the person can do, and worth_a_look for optional checks.
  3. Put everything you did and checked in details, and notes for the next agent in for_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.

  1. Call ask with one question.
  2. When the answer is a choice, send 2 or 3 options and 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.

  1. Call report with waits_on set 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.

  1. 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.

  1. Start from the summary get_context gives you.
  2. 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.

  1. 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.

  1. 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.