Pattern Proposal: Centralised Flow Runner Pipeline

Summary

A central FlowRunner appears to coordinate multi-step CAS flow execution from the CLI.

Candidate Pattern

• ID: centralised-flow-runner-pipeline
• Classification: intelligence
• Maturity: strategic_direction
• Type: emerging

Observed Signals

No specific signals listed.

Evidence

Supporting Evidence

• src/cas_runner/runner.py (FlowRunner) - Central runner class for flow execution.
• src/cas_runner/cli.py (main) - CLI entry point that likely invokes flow execution.
• docs/architecture/cas-orchestration-flow.md - Documentation names orchestration flow.
• docs/architecture/cas-automated-run-flow.md - Documentation names automated run flow.
• docs/architecture/cas-execution-sequence.md - Documentation indicates a defined execution sequence.

Scope Assessment

• Evidence Strength: medium
• Confidence: medium
• Applies to: ideas-to-life-cas

Rationale

• Intent: Give flows a single, inspectable execution point instead of scattered ad hoc agent invocations.
• Context: src/cas_runner/runner.py contains FlowRunner and src/cas_runner/cli.py contains main; documentation describes orchestration and automated run flows.
• Force: flows need predictable ordering
• Force: execution must be inspectable for governance
• Force: CLI entry points need a common execution path

Traceability

Artifact source: proposed-patterns