Pipelines
What this is for. A pipeline is an orchestrated multi-step job. The product surface today is ticket-to-code: take a Board ticket (or a manual id), run it through ingest → PM clarify → architect design → implement → review → open PR → deploy, with a human gate when a stage waits. It is not a generic workflow editor — you start a run, watch stages, approve or cancel.
Route: /pipelines. Subtitle: Ticket-to-code pipeline runs — ingest, clarify, design, implement, review, PR, deploy.
When to use it
Section titled “When to use it”- A Board ticket is ready to become a code change and you want a staged run, not a single chat.
- You need a review or deploy gate before the next stage starts.
- A run failed or was cancelled and you want to Resume from where it stopped.
- You want a history of ticket → stage → finished time without opening each conversation.
Typical workflow
Section titled “Typical workflow”- Open Pipelines in the sidebar (
/pipelines). - Under Start a run, pick source board or manual, enter the Ticket id, press Start.
- EYAS opens the run page (
/pipelines/<runId>). Stages light up in order. - When a stage is Awaiting approval, press Approve. Cancel stops a live run; Resume restarts a failed or cancelled one.
- Refresh reloads status (the page does not poll). Done when the run badge is Completed.
Features
Section titled “Features”Ticket sources are the internal EYAS board and manual entry — there is no third built-in ticket system.
| Concept | Meaning |
|---|---|
| Pipeline definition | Named flow template (ticket-to-code) |
| Run | One execution instance |
| Ticket source | board or manual |
| Stage | One step in the fixed chain |
| Gate / approval | Human checkpoint mid-flow |
| Artifact | Output of a stage (linked when present) |
Fields and controls
Section titled “Fields and controls”Start a run
| Control | Meaning |
|---|---|
| Source board / manual | Where the ticket id comes from |
| Ticket id | Id to ingest |
| Start | Create the run and open it |
| Refresh | Reload the run list |
List columns: Status, Ticket, Stage, Started, Finished, View. Empty: No pipeline runs yet.
Run status
| Status | Meaning |
|---|---|
| Running | A stage is in progress |
| Waiting for approval | Blocked on a human gate |
| Completed | All stages finished |
| Failed | A stage failed — Resume is offered |
| Cancelled | Stopped — Resume is offered |
Stages
| Stage | Meaning |
|---|---|
| Ingest | Load the ticket |
| PM Clarify | Clarify scope |
| Architect Design | Design the change |
| Dev Implement | Write the code |
| Review | Review the change |
| Open PR | Open a pull request |
| Deploy | Deploy |
Stage status
| Status | Meaning |
|---|---|
| Pending | Not started |
| Running | In progress |
| Succeeded | Done |
| Failed | Error on the stage |
| Skipped | Not run |
| Awaiting approval | Press Approve to continue |
Run page actions: Refresh, Cancel (while not completed/cancelled), Resume (failed or cancelled), Approve on a waiting stage.