Deliveries

Three pages: the list (Deliveries, where you follow work), New delivery (where you start it) and a page for each delivery. Deliveries stays the one entry in the sidebar; New delivery is a button on the list, not a menu item.

The Deliveries list (/dashboard/tasks)

• A New delivery button at the top right.
• Waiting on you: at the top, anything waiting on you, with controls to act: human steps you own or back up, and engineer steps that paused for a person (passed with concerns, couldn't verify, a question, repeated failures, or went quiet). A paused engineer step with no named owner shows for every owner and admin, and for whoever started the delivery, with the reason and the step's summary (collapsed). It can be a sub-task's. Each item links to that delivery's page.
• Two tabs, each with a count: Ongoing (the default) and Past. The tab is kept in the address (?view=past), so a reload or a shared link opens the same tab. Past is every delivery that is DONE, CANCELLED or FAILED; Ongoing is everything else (in progress, waiting on a person, waiting for children, blocked…).
• Search by title filters the tab you're on as you type.
• Each delivery is one compact row (it works on a phone): the title (opens its page), its status, the current step and who is on it ("Stage 4 of 9 · Implement · Ada" or "waiting on Ada"), repos and PRs with merge and CI state, the Jira key, how many sub-tasks are done ("2/5 sub-tasks done"), and when it started (and finished, on Past). The times are the real calendar time from the timeline: for a delivery split into sub-tasks, from when the first part started to when the last ended, not when the parent was created.
• What you can do right now stays on the row: the waiting reason with Release / Send back / Hand to someone else for a delivery waiting on a person, Resume on a blocked one, and Call off for managers. A delivery split into sub-tasks also lists, on its row, each sub-task that is waiting on a person or blocked ("Sub-task waiting on Ada: Code review"), with the same controls and a link to that sub-task's page. Everything else (timeline, activity, files, the full sub-task list) is on the delivery's page.
• Old links keep working: Deliveries?engineer=… opens New delivery with that engineer named.

New delivery (/dashboard/tasks/new; anyone in the workspace) A focused page with the delivery form (see How-tos): a title and brief, repos, engineers, Jira, the workflow and people for the human steps. Start task opens the new delivery's page. For big work, the lead plans and splits it in the workflow's Plan step.

• From a dashboard card, Give them a delivery opens New delivery with that engineer already chosen.

One delivery (/dashboard/tasks/<id>) Opened from the list, from Waiting on you, from a sub-task, or from the link in a Slack or email reminder. It works for sub-tasks too: a sub-task's page has a link back to its parent. A task that doesn't exist, or belongs to another workspace, shows "not found". It shows:

• The title, status, who started it (and in what channel), the current step and engineer, repos, PRs with merge and CI state, and the Jira key.
• Waiting on you (or "Waiting on a person") when it's WAITING_HUMAN: the reason, then Release, Send back (with notes for the engineer) and Hand to someone else for the step's owner, backup or an admin (and, when an engineer step paused with no owner, whoever started the delivery). Others see "Waiting on {person} for {step}". A BLOCKED delivery shows why it stopped (on demand) and Resume (anyone): it picks the delivery back up at the step it stopped on, with an optional note for whoever runs it. Call off (managers, until it's finished): confirm with Yes, call it off or Keep going. It also stops any sub-tasks and tells you how many.
• 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". Step notes: under each stage that has them, click Notes · {engineer} to read what that engineer wrote when the step closed (a reviewer's findings, QA's report), formatted like chat. Notes start collapsed, and a step with no notes (still running, or a person's step) shows nothing. Very long notes are cut at about 8,000 characters and say so. On a split delivery, the Integration review is a stage of its own, with the reviewer, how long it took and its notes. A stage that ran more than once has notes per attempt. For a split delivery, click a sub-task in the timeline's sub-task list to load its notes; they aren't fetched until you do. It refreshes itself while the delivery runs.
• Activity: the narration feed (handoffs, messages, notes), plus a live activity line while it runs.
• Files: files the engineers made for this delivery.
• Sub-tasks: each with its status, engineer and repos or PRs, linking to its own page. A sub-task that is waiting or blocked can be released, sent back, handed on or resumed right there, with the same permissions as on the delivery itself.

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. The delivery follows its sub-tasks: while any is running it shows this, and when a blocked or paused sub-task is resumed or released it goes back to this (it doesn't stay on WAITING_HUMAN or BLOCKED).
• 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, CANCELLED and FAILED are finished: they are the Past tab. Every other status is Ongoing.