starred/aryx
1
0
Fork 0
mirror of https://github.com/davidkaya/aryx.git synced 2026-08-07 20:28:46 +02:00
Code Issues 3 Packages Projects Releases 10 Wiki Activity

feat: add graph-backed orchestration topology

Browse Source 
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This commit is contained in:
David Kaya
2026-03-24 22:44:17 +01:00
co-authored by Copilot
parent 5ab0b22d15
commit 2e2caf78f9
13 changed files with 1871 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ARCHITECTURE.md
+6
View File
@@ -138,6 +138,12 @@ Their runtime semantics follow the Agent Framework orchestration model: sequenti
Patterns are shared application data, not renderer-only configuration. That means the same pattern definition can drive validation, persistence, UI rendering, and sidecar execution.
Patterns now persist an explicit graph-backed topology alongside the flat agent list. Agent nodes carry stable agent ids, ordering, and layout metadata, while system nodes such as user input/output, distributor, collector, and orchestrator make mode-specific flow visible in the saved contract.
That graph is now the execution contract for the sidecar: sequential order comes from the saved path, handoff routes come from directed graph edges, and concurrent/group-chat participant ordering can be derived from graph node metadata instead of hard-coded runtime assumptions.
Until the dedicated canvas editor lands, the current form-based pattern editor keeps the graph synchronized by rebuilding the saved topology from the selected mode and agent list on change/save. This is an intentional temporary adapter so backend/runtime work can land before the renderer graph UX is replaced.
### Sessions
A session is the working unit of the product. It binds together: