GitHub user armorer-labs added a comment to the discussion: [Discussion] Supervisor + Sub-Agent Orchestration: Concrete Multi-Agent Use Cases for Event-Driven Agents
For event-driven multi-agent systems, the primitive I would care about most is the durable run record between agents. A supervisor/sub-agent design becomes much easier to operate if every handoff carries: - root run id - parent step id - sub-agent identity/version - input artifact references - expected output contract - timeout/retry policy - final artifact or failure reason That seems very aligned with Flink’s strengths: state, replay, event history, and recovery. The interesting part is avoiding “LLM call chains” as the abstraction and instead modeling agents as event-producing workers with inspectable state transitions. GitHub link: https://github.com/apache/flink-agents/discussions/660#discussioncomment-16894663 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
