Draft
Task card
Draft plan
The task is prepared but has not started yet.
Use this state before a run is accepted or queued.
Task card
Every supported run-card state in one place.
Task cards are presentational summaries that stay attached to the message that created them.
Supported statuses
Draft, queued, running, ready, success, failed, and stopped all use the same data shape.
Queued
Task card
Workspace bootstrap
The run is accepted and waiting to begin.
Queued cards keep the created request and its progress in the transcript.
Started 2 minutes ago
Waiting for an execution slot
Queue
Position 2
Files
1 brief
Running
Task card
Brief synthesis
The run is collecting evidence before it writes the note.
Running cards can show age, progress, stats, and actions.
Started 7 minutes ago
Stage 2 of 4 complete
Files
3 attached
Next
Draft summary
Ready
Task card
Handoff bundle
The output is ready to review or publish.
Ready is useful when a downstream human action is now required.
Artifacts
4 items
Owner
Ops
Complete
Task card
Launch checklist
The run finished successfully with a clean summary.
Success can stay in-thread as a durable status artifact.
Checks
8 passed
Follow-ups
2
Failed
Task card
Attachment import
The task stopped before it could produce a result.
Failure cards should keep the user near the source request and error.
The PDF could not be parsed because the upload expired.
Stopped
Task card
Draft follow-up
The run was intentionally stopped before completion.
Stopped is distinct from failed when cancellation is user-driven.
Progress
2 of 4
Reason
User cancelled