Issue hydration
| Name | issue-hydration |
| Enabled by default | Yes |
| Steps | 2 |
| Runs at once | up to 5 |
| Catalog | v0.2.0 |
What it does
Turns a new issue into one an agent or a human can pick up cold. The architect-issue-hydration AgentRole adds acceptance criteria, design notes, affected components, a verification plan and an estimate, and moves the issue to Arch reviewed. A human then triages it to Todo (human) or Todo (agent); only Todo (agent) starts the change AgentWorkflow.
When it runs
- On the event
issue.opened. Runs when an issue is opened on a Product repo. - On the event
issue.labeled. Runs again when someone adds the needs-hydration label, for example after the issue changed. Only for labelsneeds-hydration.
Steps
Rounded steps are human gates, slanted steps are promotions, and double-edged steps run automatically.
| # | Step | Type | Runs | Required | On failure | Attempts |
|---|---|---|---|---|---|---|
| 1 | hydrate | AgentRole | Issue hydration | Yes | Dead-letter to a human | 2 |
| 2 | triage | Human gate | Human gate | Yes | Fail the run | 1 |
1. hydrate
Hydrates the issue and moves it to Arch reviewed.
Skipped when its AgentRole is switched off.
2. triage
A human confirms the hydration and assigns the issue to Todo (human) or Todo (agent).
When it hands off to a human
Human gates: triage. Required steps cannot be switched off for a Release.
Work an agent cannot finish is dead-lettered to @platform/architects. The AgentWorkflowRun shows the step as DeadLettered until a human picks it up.