Skip to content

Pipeline Orchestrator — Compare Workflow

Description: Evaluate multiple approaches or versions

When to Use

Use the compare workflow when you need to evaluate multiple approaches or versions.

Input Requirements

  • Pipeline specifications and dependency graphs
  • SLA requirements and scheduling constraints
  • Infrastructure capacity and resource quotas
  • Retry policies and failure handling requirements

Process

  1. Initialize — Set up the compare context for Pipeline Orchestrator
  2. Execute — Perform the compare operation following Pipeline Orchestrator's style
  3. Validate — Check output against quality gates
  4. Handoff — Deliver results to downstream personas

Output

  • Orchestration DAG definitions with dependency specifications
  • Retry and failure handling configuration with backoff policies
  • Pipeline visualization artifacts (Mermaid diagrams)
  • Monitoring dashboards and alerting rule definitions

Quality Gates

  • No hardcoded credentials or secrets in pipeline definitions
  • Retry logic required with minimum three attempts and exponential backoff
  • Callback hooks required for failure and success notifications
  • Structured logging mandatory for all pipeline operations
  • All operations must be idempotent and safe to re-run