Deliveries

Start and follow deliveries.

• Waiting on you: at the top, any human steps you own or back up, with controls to act.
• Start a task on a workflow (anyone in the workspace): the delivery form (see How-tos).
• Resume on a blocked delivery's card (anyone): picks it back up at the step it stopped on, with an optional note for whoever runs it.
• Delegate an epic: give the Engineering Lead a larger brief ("Epic brief" and optional repository) to break into tasks for specialists. Needs an active Engineering Lead.
• Tasks: every delivery with its status, title, "Stage 4 of 9 · Implement", repos, PRs with merge and CI state, and Jira key. Each has:
  • Timeline: every stage so far and the stages ahead, who did each, how long it took, split into engineering time, waiting time and "stalled" (no sign of life for over 15 minutes, not counted as engineering). Stages sent back show as "2nd time round".
  • Activity: the narration feed (handoffs, messages, notes), plus a live activity line while it runs.
  • Files: files the engineers made for this delivery.
  • When it's WAITING_HUMAN: Release, Send back (with notes for the engineer) and Hand to someone else for the step's owner, backup or an admin. Others see "Waiting on {person} for {step}".
  • Call off (managers, until it's done): confirm with Yes, call it off or Keep going. It also stops any sub-tasks and tells you how many.
  • Sub-tasks listed underneath with their status and engineer.

Statuses:

• OPEN: created, not started.
• IN_PROGRESS: an engineer is working on a step.
• WAITING_HUMAN: waiting on a person (a human step, a step whose role isn't hired, or work that went quiet).
• WAITING_CI: parked at the CI/quality gate until checks finish.
• AWAITING_CHILDREN: split into sub-tasks; waiting for them to finish.
• BLOCKED: stopped (a failure with no fallback route, waiting for credit or a plan, or queued because the engineer is at capacity). See Troubleshooting.
• DONE and CANCELLED.