240 architecture implement quality control pipeline orchestration

[jeipollack]

Summary

Provide a concise description of the proposed changes.
Include "closes #<ISSUE_NUMBER>" if this addresses an open issue

Note: Validation tests and plots should not be added to the PR; they should be documented in the dedicated issue instead.

What’s changed

Describe the main changes introduced by this PR.
Focus on user-visible changes, bug fixes, performance improvements, or internal changes.

• Example bullet 1
• Example bullet 2

How to test / verify

Outline steps for reviewers or maintainers to validate the changes.
Include commands, scripts, or datasets if relevant.
Full validation results should be referenced in the associated issue, not pasted here.

• Step 1
• Step 2

Scope

Indicate the type of PR:

• Feature
• Bug fix
• Hotfix
• Documentation / process change
• Internal / refactor
• Release

Optionally, note if this PR is part of a larger milestone or set of related PRs.

Changelog

Did this PR introduce user-visible changes?
If yes, a Scriv changelog fragment must be added and committed.

• Changelog fragment added (if applicable)

Reviewer Checklist

Reviewers should confirm the following before approving and merging:

• The PR targets the correct base branch (develop, or main for release PRs)
• The PR is assigned to the developer
• Appropriate labels are applied
• The PR is included in relevant projects and/or milestones
• Description clearly explains what has changed
• Issue references included, if applicable
• Code and documentation adhere to current standards (ruff)
• Documentation updates included, if relevant
• CI tests are passing
• All reviewer comments have been addressed

Next Steps / Notes (if applicable)

Any follow-up actions, known issues, or reminders for maintainers.