Pattern Proposal: CLI-to-Runner Orchestration Boundary

Summary

Confine command-line argument parsing and environmental setup to a thin presentation module that delegates all workflow execution to a dedicated Runner component.

Candidate Pattern

• ID: cli-to-runner-orchestration-boundary
• Classification: architectural
• Maturity: strategic_direction
• Type: emerging

Observed Signals

No specific signals listed.

Evidence

Supporting Evidence

• src/cas_runner/cli.py (main) - Parses CLI commands and forwards operational parameters to FlowRunner.
• src/cas_runner/runner.py (FlowRunner) - Orchestrates the sequential flow of architecture tasks independently of CLI specifics.

Scope Assessment

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

Rationale

• Intent: Maintain a clean separation between presentation/entrypoint mechanics and core pipeline execution.
• Context: The package provides a console script entrypoint invoked in local developer shells and GitHub Actions workflows.
• Force: Embedding orchestration logic in CLI scripts makes headless invocation and automated testing difficult
• Force: Changes in CLI argument parsing libraries should not affect workflow logic

Traceability

Artifact source: proposed-patterns