Move AI orchestration runtime out of phases#23916
Open
luisorofino wants to merge 2 commits into
Open
Conversation
Contributor
|
3 tasks
Contributor
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jun 3, 2026
fec8bb0 to
fd4614c
Compare
4684d6f to
172b8e4
Compare
Contributor
Validation ReportAll 21 validations passed. Show details
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What does this PR do?
Moves AI flow runtime concerns out of the
phasespackage and into a dedicatedruntimelayer:PhaseOrchestratortoddev.ai.runtime.orchestrator.ddev.ai.runtime.checkpoints.ddev.ai.runtime.resources.RunResources.ddev.ai.phases.registry.PhaseResourcesprotocol inddev.ai.phases.resourcesso phase implementations depend on a small resource contract instead of the concrete orchestrator module.Motivation
The AI framework now has clearer responsibility boundaries: phases define executable phase behavior, while runtime owns orchestration, checkpoints, and run-scoped resource wiring. This also improves dependency direction: the runtime layer depends on phases, and phases depend only on the
PhaseResourcesprotocol rather than the orchestrator implementation.Review checklist (to be filled by reviewers)
qa/requiredif this PR needs QA validation, orqa/skip-qaif it does not. Exactly one of the two is required.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged