Give Artie work that spans days or weeks

Set milestones, decisions and evidence for a longer responsibility.

Longer work needs a clear outcome and a way to tell whether progress is real. Artie can retain the work's context, waits and next actions across attempts; a finished attempt is not automatically a finished responsibility.

On this page

Define the finish and checkpoints

Name the final deliverable, its due date and evidence that will count as completion. Add milestones for work that has several stages.

Prepare our customer launch plan by the 24th. First gather the current scope and customer list, then draft the plan, then ask me to review the customer messages before they go out.

Name dependencies and decisions

Explain which work relies on a person, app or earlier result. Give the decision owner and useful checkpoint. In Slack or web chat, if Artie says it will check back at a stated time, that promise becomes due work: Artie checks then and reports what it found or why it couldn't keep the promise. An offer that needs your yes is a question, not a commitment; answer it if you want the work to proceed. Artie won't create another commitment for a follow-up that's already scheduled. Avoid asking several Artisans to own the same end-to-end job; let one lead coordinate contributions.

Review the actual work record

Use the task's progress, next action and linked outputs. Waiting on a decision, retrying a failed step and completing a draft are distinct states. When a promised check comes due, look for evidence of what Artie did or an explanation of why it couldn't keep the promise and what happens next. For a promise Artie made in a meeting, look in the owner's recap chat for the report. Quiet hours or the daily attention budget can defer delivery, and actions that need approval still wait for it. If a deadline slips, ask for the cause, revised next step and remaining dependencies.

Change priorities without losing the obligation

Tell the lead what changed and what still needs delivering. Stop or transfer work explicitly when it is no longer wanted. Do not infer that an ended chat run, an idle indicator or a dismissed notification ended the underlying responsibility.