refactor(orchestrator): replace SDLC actions with protocols by alexsoyes · Pull Request #517 · ai-driven-dev/framework

alexsoyes · 2026-07-25T07:36:22Z

What

Moves SDLC orchestration from aidd-dev to aidd-orchestrator and replaces the rigid action tree with three routing protocols:

$request → Frame → Deliver → Check → draft PR

Recipe skills own validation and retry loops.
@executor implements, validates, debugs unclear failures, and commits.
A fresh @checker reviews and challenges the outcome independently.
Product gaps return to Frame; implementation findings return to Deliver, in parallel through /aidd-dev:10-todo when independent.
The flow acts autonomously unless money, an irreversible action, or user authority is involved.

Verification

Review: 24/24, no findings
4 Mermaid diagrams rendered
5 flat distributions built
0 broken Markdown links

✅ I certify

I DO CERTIFY I READ EACH LINE OF THE PULL REQUEST BECAUSE I AM A SOFTWARE ENGINEER, NOT A AI PUPPY.

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 · 2026-07-26T05:37:05Z

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 · 2026-07-27T03:58:42Z

@@ -0,0 +1,48 @@
+# 01 - Frame
+
+## Behavior


On sort completement de la structure des autres skills. Pourquoi pas mais à challenger et ça a pour conséquence : définir un nouveau type de skill a generer côté skill-generate, dans les cours, dans la formation

blafourcade · 2026-07-27T03:59:32Z

+  subgraph SourceStage["Resolve the source"]
+    direction TB
+    Source["$source"]
+    Ticket["/aidd-pm:01-ticket-info"]


Trop orienté pour moi on doit être haut niveau ici

Le but c'est de définir un flot sur lequel l'IA peut se rattacher et suivre une ligne directrice. Qu'est-ce qui ne te convient pas ici ?

Les plugins sont optionnels donc ici tu as un risque que ça n'existe pas. Si quelqu'un a une autre façon de faire tu l'oblige a suivre cette façon de faire.

Vu qu'on est sur de l'orchestration, en ayant discuté aussi avec Jerem on est aligné pour utiliser le concept "Ticketing Information" ou autre vs un skill en dur

Je suis pas sur de comprendre on est sur un skill d'orchestration donc ofc y'a de la dépendance -- tu aurais fait quoi ?

blafourcade · 2026-07-27T03:59:40Z

+  subgraph FrameStage["Frame the contract when needed"]
+    direction TB
+    Brainstorm["/aidd-refine:01-brainstorm"]
+    Spec["/aidd-pm:04-spec"]


C'est une bonne chose, ça sert de doc à l'IA + aux humains ?

Un dev ça cross les barrières en fonction

alexsoyes · 2026-07-28T07:25:35Z

@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 ?

blafourcade · 2026-07-28T07:48:19Z

@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 ?

Oui je pense

alexsoyes

@blafourcade sounds good ?

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.

alexsoyes added 26 commits July 25, 2026 09:28

refactor(framework): move SDLC orchestration

ad48cdf

refactor(orchestrator): replace SDLC actions with protocols

aa55f35

refactor(orchestrator): parallelize review fixes

28654f5

fix(orchestrator): align SDLC protocol notation

e95c08e

fix(orchestrator): name SDLC providers explicitly

cc35876

refactor(orchestrator): simplify SDLC diagrams

9399371

refactor(orchestrator): orient SDLC flows left to right

48c7e30

docs(review): assess SDLC orchestration

c88a5ea

refactor(orchestrator): clarify SDLC diagram labels

a1b4d80

refactor(orchestrator): make SDLC autonomous

5751a70

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.

docs(orchestrator): align autonomous SDLC guidance

782e53f

Remove the remaining interactive and mandatory-spec descriptions so every public path points to the same autonomous contract.

style(tooling): drop unrelated formatting change

7097f21

docs(review): approve autonomous SDLC flow

6d3dedc

Record the clean three-axis review after validation loops, fresh checker inputs, bounded Todo fan-out, and public guidance were aligned.

fix(framework): use canonical orchestration addresses

e1abb5d

Keep Mermaid ownership links and agent capability declarations explicit so responsibility maps resolve to installed providers.

refactor(orchestrator): separate behavior from routing

9688634

Put autonomous invariants before each flowchart and let Mermaid remain the single source for transitions instead of repeating every edge in trailing bullets.

docs(review): verify canonical SDLC protocols

944637f

Refresh the evidence after canonical agent permissions, the repaired codebase map, and behavior-first protocol documentation.

refactor(orchestrator): group SDLC diagrams top-down

f12b285

Use vertical stage subgraphs so each protocol remains readable in a normal Markdown viewport without changing its routing contract.

docs(review): record grouped SDLC diagrams

269a3c8

refactor(orchestrator): simplify autonomous SDLC contract

cbb9631

Keep each protocol self-contained and human-readable while preserving autonomous routing, useful parallelism, and review freshness without exposing Git jargon.

docs(review): verify simplified SDLC contract

daf325f

refactor(orchestrator): keep SDLC focused on routing

0988aaf

Move validation gates into their owning recipe skills so the orchestration references teach only behavior, delegation, and handoffs.

docs(review): verify routing-only SDLC protocols

7beb1cb

Record the simplified source handoff, delegated gates, Mermaid renders, and five target builds.

refactor(orchestrator): remove SDLC self-references

313178d

The diagrams describe an already-running orchestration, so routing now starts directly from each zone input.

docs(docs): verify direct SDLC routing

c15f714

Record that internal diagrams no longer represent the already-invoked orchestrator as a node.

refactor(framework): clarify autonomous recovery

2f0003d

Keep confirmation boundaries in the SDLC contract and route unclear validation failures through the executor debugging capability.

docs(docs): verify autonomous recovery contract

c9a8ef3

Record the executor debug fallback and the refined SDLC authority boundary.

alexsoyes requested a review from blafourcade July 25, 2026 16:44

alexsoyes assigned blafourcade Jul 25, 2026

alexsoyes added this to AIDD Roadmap Jul 25, 2026

github-project-automation Bot moved this to Todo in AIDD Roadmap Jul 25, 2026

alexsoyes moved this from Todo to Done in AIDD Roadmap Jul 25, 2026

alexsoyes marked this pull request as ready for review July 25, 2026 16:46

blafourcade reviewed Jul 27, 2026

View reviewed changes

blafourcade assigned alexsoyes and unassigned blafourcade Jul 27, 2026

alexsoyes assigned blafourcade and unassigned alexsoyes Jul 28, 2026

blafourcade assigned alexsoyes and unassigned blafourcade Jul 28, 2026

blafourcade moved this from Done to In review in AIDD Roadmap Jul 30, 2026

alexsoyes commented Jul 31, 2026

View reviewed changes

alexsoyes enabled auto-merge (squash) July 31, 2026 05:29

chore(framework): merge next into sdlc orchestration

578a728

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.

alexsoyes requested a review from a team as a code owner July 31, 2026 05:40

chore(environment): remove setup script from environment.toml

fd766e3

Uh oh!

Conversation

alexsoyes commented Jul 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Verification

✅ I certify

Uh oh!

alexsoyes commented Jul 26, 2026

Uh oh!

Uh oh!

Uh oh!

blafourcade Jul 27, 2026

Choose a reason for hiding this comment

Uh oh!

blafourcade Jul 27, 2026

Choose a reason for hiding this comment

Uh oh!

alexsoyes Jul 28, 2026

Choose a reason for hiding this comment

Uh oh!

blafourcade Jul 28, 2026

Choose a reason for hiding this comment

Uh oh!

alexsoyes Jul 28, 2026

Choose a reason for hiding this comment

Uh oh!

blafourcade Jul 27, 2026

Choose a reason for hiding this comment

Uh oh!

alexsoyes Jul 28, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

alexsoyes commented Jul 28, 2026

Uh oh!

blafourcade commented Jul 28, 2026

Uh oh!

alexsoyes left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

alexsoyes commented Jul 25, 2026 •

edited

Loading