refactor(orchestrator): replace SDLC actions with protocols - #517
Open
alexsoyes wants to merge 28 commits into
Open
refactor(orchestrator): replace SDLC actions with protocols#517alexsoyes wants to merge 28 commits into
alexsoyes wants to merge 28 commits into
Conversation
Keep the orchestrator moving until validation, independent review, and the final outcome challenge all pass. Route contract and implementation gaps back through explicit bounded loops.
Remove the remaining interactive and mandatory-spec descriptions so every public path points to the same autonomous contract.
Record the clean three-axis review after validation loops, fresh checker inputs, bounded Todo fan-out, and public guidance were aligned.
Keep Mermaid ownership links and agent capability declarations explicit so responsibility maps resolve to installed providers.
Put autonomous invariants before each flowchart and let Mermaid remain the single source for transitions instead of repeating every edge in trailing bullets.
Refresh the evidence after canonical agent permissions, the repaired codebase map, and behavior-first protocol documentation.
Use vertical stage subgraphs so each protocol remains readable in a normal Markdown viewport without changing its routing contract.
Keep each protocol self-contained and human-readable while preserving autonomous routing, useful parallelism, and review freshness without exposing Git jargon.
Move validation gates into their owning recipe skills so the orchestration references teach only behavior, delegation, and handoffs.
Record the simplified source handoff, delegated gates, Mermaid renders, and five target builds.
The diagrams describe an already-running orchestration, so routing now starts directly from each zone input.
Record that internal diagrams no longer represent the already-invoked orchestrator as a node.
Keep confirmation boundaries in the SDLC contract and route unclear validation failures through the executor debugging capability.
Record the executor debug fallback and the refined SDLC authority boundary.
alexsoyes
marked this pull request as ready for review
July 25, 2026 16:46
Contributor
Author
|
Hello @blafourcade , J'ai documenté les flows + déplacé l'orchestration dans le bon plugin + viré les actions pour les rendre plus simples / suivables ! |
blafourcade
reviewed
Jul 27, 2026
Contributor
Author
|
@blafourcade du coup, tu voudrais que je mette ça dans des dossiers de référence ? Ça ferait plus de sens pour toi sur le flow ? |
Contributor
Oui je pense |
alexsoyes
commented
Jul 31, 2026
alexsoyes
left a comment
Contributor
Author
There was a problem hiding this comment.
@blafourcade sounds good ?
alexsoyes
enabled auto-merge (squash)
July 31, 2026 05:29
Keep the current PM catalog additions while preserving the relocated synchronous SDLC documentation. Follow next's intentional removal of the frozen v3-to-v4 upgrade guide.
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
Moves SDLC orchestration from
aidd-devtoaidd-orchestratorand replaces the rigid action tree with three routing protocols:$request → Frame → Deliver → Check → draft PR@executorimplements, validates, debugs unclear failures, and commits.@checkerreviews and challenges the outcome independently./aidd-dev:10-todowhen independent.Verification
✅ I certify