Skip to content

.pipeline/config.yml

.pipeline/config.yml is checked into your repo and read on every run. This page documents the user-facing blocks and what each knob does. The file is scaffolded with documented defaults the first time you run Pipemason in a repo.

domains

Lists the domains present in the repo. A domain is enabled only if it appears here and has a matching entry under commands. The enabled domains determine which kinds of work Pipemason does, so an api-only repo never ships mobile, cloud, or game work.

domains:
  - api
  # - web
  # - mobile
  # - db
  # - cloud

commands

Per-domain commands Pipemason invokes for that domain's gates. Each domain accepts test, lint, typecheck, run, build (and domain-specific keys such as e2e, coverage, or migrate). A missing key disables the corresponding gate for that domain — for example, omit lint and no lint gate runs.

commands:
  api:
    test: "npm test"
    lint: "npm run lint"
    typecheck: "npm run typecheck"
    run: "npm run dev"
    coverage: "npm run test:coverage"

For monorepos that put several stacks under one domain, a services: map lets each service declare its own path and commands; Pipemason then runs each service's commands separately.

branch

Controls how Pipemason names the branches it creates. pattern is a template rendered from placeholders: {type}, {description}, {ticket}, {story}, {epic}, {program}, and {user}. Empty placeholders collapse, dangling separators are cleaned up, and the result is sanitized to a valid git ref. types defines the available branch types: the first entry is the default, and a later entry whose keyword appears in the run input (word-boundary, case-insensitive) wins. base selects the base branch (auto probes the repo's default), and max_slug_length caps the generated description fragment.

branch:
  base: auto
  pattern: "{type}/{description}"
  types:
    - name: feature        # first entry is the default
      keywords: []
    - name: bug
      keywords: [bug, fix, hotfix, regression]
  max_slug_length: 60

Note

Program and stacked runs append the story id automatically when {story} is absent from the pattern, so stacked branches never collide.

cost_controls

On by default. Guardrails that bound what any single step of a run can spend:

  • max_budget_usd_per_spawn — a step that would exceed this dollar amount fails fast.
  • max_turns_per_spawn — caps how many turns a single step may take, so a runaway step can't spin forever.
cost_controls:
  enabled: true
  max_budget_usd_per_spawn: 8
  max_turns_per_spawn: 100

Note

The program-wide spend ceiling is separate — pass --max-cost / --max-daily-cost to pipemason program start.

accessibility

On by default. Shifts accessibility checks left across the pipeline. enabled is the single source of truth: when true, per-story accessibility criteria and the verify-time conformance gate both block on failures; when false, they revert to advisory. standards selects the target standards (wcag-2.2-aa, section-508, en-301-549), vpat emits a VPAT/ACR at the end of a program, and domains lists the UI domains that get the accessibility checks and gate.

accessibility:
  enabled: true
  standards: [wcag-2.2-aa, section-508, en-301-549]
  vpat: true
  domains: [web, mobile, game-mobile, rn]

verification

Controls the runner-side checks that gate done: the configured test and typecheck commands are re-run by the runner at finalize, new test files that the configured command never executes are reported as orphans, and every acceptance criterion needs a verdict. command_timeout_ms bounds each command (default 20 minutes). orphan_tests is fail (default) or warn. See How Pipemason verifies results.

verification:
  command_timeout_ms: 1200000
  orphan_tests: fail

drift_check

On by default. At the exit of each listed phase, Pipemason checks the phase’s changes against the spec and the agreed interfaces before the run advances. See How Pipemason verifies results for the full behavior.

KeyDefaultMeaning
drift_check.enabledtrueMaster switch. false turns drift checks off.
drift_check.phases[tdd, implement, e2e, ui]Phases whose exit is checked. A present list replaces the default wholesale and may not be empty.
drift_check.max_bounces2How many times a phase may be sent back to correct a drift verdict before the run escalates.
drift_check:
  enabled: true
  phases: [tdd, implement, e2e, ui]
  max_bounces: 2

Note

Set enabled: false to turn drift checks off.

review

On by default. Adds a pr_review phase between runtime_check and rebase: independent reviewers (goal, security, maintainability, plus one domain reviewer per active domain) review the story diff as a PR. Each comment is fixed or declined with a reason, and the reviewer accepts or rejects the fix. The finalize gate refuses to push while any thread whose severity is in block_on is still open. Full log: .pipeline/artifacts/review/<story>/review.json. Opt out for one run with --no-review on pipemason start or pipemason program start (writes review_disabled: true to STATE.md; sticky across resume, never rewrites config.yml).

KeyDefaultMeaning
review.enabledtrueMaster switch. false (or --no-review for one run) skips pr_review entirely, and the finalize gate ignores review.
review.max_rounds3Round 1 is the full review, round 2 verifies the remediation, round 3 is the final pass. Once the limit is reached with a block_on thread still open, the run escalates.
review.reviewers[goal, security, maintainability, domain]The review lenses to use. A list you provide replaces the default completely. domain reviews once per active domain.
review.block_on[blocking]Severities (blocking | suggestion) that must end closed_* before rebase and before the finalize gate will push. nit never blocks.
review.pr_summarytrueAdds a ## Pre-review (agent) section to the PR body when finalize creates a PR.
# review:
#   enabled: true
#   max_rounds: 3
#   reviewers: [goal, security, maintainability, domain]
#   block_on: [blocking]
#   pr_summary: true

Note

Set enabled: false, or pass --no-review for a single run, to restore pre-feature behavior: runtime_check advances straight to rebase, and the finalize gate never looks at review.json.