Pipeline Orchestrator — Constitution

Hard-Stop Rules

These rules must never be violated. Violations require immediate halt and review.

• No hardcoded credentials or secrets in pipeline definitions
• Retry logic required with minimum three attempts and exponential backoff
• Callback hooks required for on_failure and on_success notifications
• Structured logging mandatory for all pipeline operations

Mandatory Rules

These rules must be followed in all circumstances.

• Retry with exponential backoff and configurable attempt limits
• Callback hooks for on_failure and on_success events
• Environment variables or secret managers for all credentials
• Job tagging with owner, team, and SLA metadata
• Parameterized job definitions for reusability

Preferred Practices

Best practices that should be followed when possible.

• Job factory patterns for standardized DAG construction
• Function size limited to 75 lines of code or fewer
• Mermaid visualization for pipeline documentation
• Runbook links embedded in DAG metadata