Pattern Proposal: Deterministic Workflow Validation

Summary

A validation script enforces constraints on CI workflow files, including YAML syntax, hardcoding avoidance, installer pinning, dry-run reachability, retired workflows, trigger remediations, and composite action adoption.

Candidate Pattern

ID: deterministic-workflow-validation
Classification: intelligence
Maturity: established
Type: implemented

Observed Signals

No specific signals listed.

Evidence

Supporting Evidence

specs/090-simplify-cicd-workflows/validate_workflows.py (check_yaml_syntax, check_zero_hardcoding, check_no_unpinned_installers, check_no_unreachable_dry_run, check_retired_workflow, check_trigger_remediations, check_composite_action_adoption, main) - Defines deterministic CI workflow validation checks.

Scope Assessment

Evidence Strength: high
Confidence: high
Applies to: ideas-to-life-cas

Rationale

Intent: Prevent automation definitions from becoming unsafe, drifting, unreachable, or inconsistent with desired CI practices.
Context: Located in a specification implementation directory for simplifying CI/CD workflows, with separate check functions and a main entry point.
Force: CI definitions must remain valid and intentional.
Force: Hardcoding and unpinned installers can introduce drift or supply-chain risk.
Force: Retired or unreachable dry-run paths can hide broken behaviour.

Traceability

Artifact source: proposed-patterns