Add Script-Based Workflows (Reduce Reliance on Notebooks) #654
Description
Title
Add Script-Based Workflows (Reduce Reliance on Notebooks)
Context
Current MSML examples and workflows are primarily notebook-driven. While useful for exploration, notebooks are not ideal for:
- Reproducibility
- Version control and code review
- Reuse in pipelines, CI, or automation
Script-based entry points would make MSML easier to integrate into real development workflows.
Goals
- Promote reproducible, testable workflows
- Separate exploratory analysis from executable logic
- Enable CI- and pipeline-friendly usage
Scope
- Add Python scripts as first-class entry points for common workflows
- Refactor core logic out of notebooks into importable modules
- Keep notebooks as they are.
- Document a recommended project structure (scripts + notebooks)
Deliverables
/scripts(or equivalent) directory with example entry points- Refactored notebooks that call into scripts/modules
- Documentation on when to use scripts vs notebooks
Non-Goals
- Removing notebooks
- Full CLI framework (initially)