56 lines
2.7 KiB
Markdown
56 lines
2.7 KiB
Markdown
---
|
|
name: Pipelines
|
|
description: Use and author Pipelines workflows, inspect runs, and recover or deliver project work directly when that is the simpler route.
|
|
---
|
|
|
|
# Pipelines
|
|
|
|
Pipelines are optional execution tools. The manager may also implement, test,
|
|
review, resolve conflicts, merge and deliver directly. Do not turn a failed
|
|
workflow into repeated whole-run retries or another pipeline's landing job.
|
|
|
|
## Work
|
|
|
|
Read the task and relevant project map before asking questions. Split changes
|
|
into small verifiable items, each with one goal and short acceptance checks.
|
|
Run independent items concurrently; use separate worktrees and the agreed model.
|
|
Preserve partial work and inspect real diffs and command results. A failed item
|
|
does not freeze unrelated work. Continue at the necessary stage or recover directly.
|
|
|
|
## Definitions
|
|
|
|
Edit a retained draft, not immutable history. Give each stage one simple job and
|
|
only the input it needs. Preserve review gates, runtime limits, permissions,
|
|
resource declarations and the user's constraints unless asked to change them.
|
|
Use `pipelines validate DRAFT --json` before publication. Publish or execute when
|
|
the user requests it; do not ask again for routine steps already authorized.
|
|
Keep version guards. `--yes` is not a conflict policy; never silently force an
|
|
update over somebody else's version. A draft-only request does not authorize a run.
|
|
|
|
For delivery-enabled stages, the committer prepares a clean checked candidate and
|
|
returns success; the server lands afterward. Check ancestry after landing, not as
|
|
a precondition that prevents the gate running. Direct recovery may merge reviewed
|
|
work itself, while preserving unrelated changes and checking the result.
|
|
|
|
## References
|
|
|
|
Do not preload references. Read only the reference needed for the current task:
|
|
|
|
| Need | Reference |
|
|
| --- | --- |
|
|
| Small tasks and stage roles | `references/orchestration.md` |
|
|
| Queue and parallel work | `references/work.md`, `references/queue.md` |
|
|
| Failures and recovery | `references/debugging.md` |
|
|
| Delivery and installation | `references/delivery.md` |
|
|
| Definition syntax and handoffs | `references/format.md`, `references/control.md` |
|
|
| Harnesses and models | `references/harnesses.md` |
|
|
| Notifications | `references/notifications.md` |
|
|
| CLI, storage and retained evidence | `references/operations.md` |
|
|
| Transfer and version conflicts | `references/transfer.md` |
|
|
| Verification and accounting | `references/verification.md` |
|
|
|
|
Use command-specific `pipelines help COMMAND` rather than guessing flags.
|
|
Distinguish validation, executed tests, landed source and deployed behavior.
|
|
Preserve history, branches and user data. Do not disrupt active services or device
|
|
users. Ask before destructive or out-of-scope actions, not ordinary implementation.
|