Finish, fail, give back, hand on, withdraw, flag or remove a task
Record what happened to a task: finish it with its result, say it failed, give it back, hand it on to someone else, say what blocks it, take back one I gave, or remove it
Record what happened to a task: finish it with its result, say it failed, give it back, hand it on to someone else, say what blocks it, take back one I gave, or remove it
Reads the task id and makes the move action names, by the rules in task-moves.json: finish (the taker; needs result, may add summary and check) and fail (the taker; needs result: why) end it as Done or Broken; release gives it back to To do (the taker, or anyone once it is held longer than the stale-take time; because says why); hand-on replaces the assignees (required) and gives the task back to To do with no taker (the taker, or the giver while it waits); stuck says what blocks it (anyone, so a watcher can flag it; needs words) and unstuck clears that; withdraw takes back a task still waiting (its giver; because); wait keeps recoverable work blocked on this same task with continuation {owner, action, after, reason}; resume returns it to waiting when due (its taker, giver or continuation owner); plan saves the acceptance a finish checks (the taker); edit changes a waiting task's words, assignees or acceptance (its giver); remove deletes the record (its giver, or anyone once it is finished). The move is one write of the whole task conditioned on the value just read: when the task changed meanwhile nothing is written and the answer is moved false with reason changed and the task as it now is. A move the rules do not allow is refused, saying why. A finish also needs check: the exact saved outcome, checked_at during this take, consumer evidence ({ref, observation}), and one matching check per saved obligation. This records accountable observation and does not itself prove its truth. The caller hands in every record it reads as input.records; this tool reads no store and names no store method. Each write it makes comes back as keep, for the caller to keep in the person's own store.
Nothing: your AI starts it with your words.
Connect the AI you already use to Trillion once. Then ask in your own words; your AI finds this tool by what it does and runs it.
Say to your AI: “Use Trillion to record what happened to a task: finish it with its result, say it failed, give it back, hand it on to someone else, say what blocks it, take back one I gave, or remove it”