Status: accepted for specification; implementation pending.
Should SIM-ONE Alpha add LangGraph as a second agent runtime, use a Flue workflow as the graph scheduler, or build the task coordinator around Flue’s existing agent surfaces?
Build a small application-owned TypeScript task-graph coordinator and use Flue agents, subagents, tools, skills, MCP connections, sessions, streams, and persistence as node executors.
Do not add LangGraph as a runtime dependency. Borrow its proven architectural mechanisms where they fit: typed state channels and reducers, partial updates, conditional edges, checkpointed threads, interrupts, private subgraph state, and explicit runtime context.
Do not use a Flue workflow as the TLG scheduler. Flue workflows may package bounded operations, but interrupted workflow functions do not resume from an arbitrary completed step. The SIM-ONE coordinator and Memory Helper own checkpoint and resume behavior.
SIM-ONE Alpha is a Flue product. A second agent runtime would duplicate model, tool, subagent, persistence, event, and deployment concerns. A narrow coordinator supplies the missing graph semantics without weakening Flue ownership.
@langchain/langgraph and routing model work outside Flue.while loop per worker.plan-implementationimplement-core-contractsimplement-agent-runtimeimplement-ingress-operationsintegrate-and-repairreview-architecture-securityspecify-task-lifecycle-architectureverify-release-reconciliation-specificationsRevisit if Flue adds a durable, resumable, step-checkpointed graph API that satisfies the same state, interrupt, context, and evidence contracts without duplicating the SIM-ONE coordinator.