lkn
/
ollie
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Clarify internal message bus architecture

This commit is contained in:
Ollie Agent 2026-08-16 19:58:25 +02:00
parent 515137a88c
commit 60ee3c62d5
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/architecture.md
View File

@ -54,9 +54,9 @@ An MCP server can remain an optional external dependency. A bridge tool can invo
Capabilities are not compiled into the agent loop as provider-specific or framework-specific tool objects. Tool behavior lives in external executables or metadata-only commands, and toolsrv owns discovery, loading, execution, sandboxing, and process state. See [`architecture-tools.md`](architecture-tools.md) and [`architecture-toolsrv.md`](architecture-toolsrv.md).
### No second coordination protocol
### No external coordination protocol
Ollie does not add a workflow engine, message bus, actor framework, or master coordinator for multi-agent work. Sessions, agents, `prompt`, `chat`, `statewait`, `feed`, and `ctl` files provide routing, synchronization, observation, and control. Hub-and-spoke, pipeline, scatter-gather, peer, reactive, and self-directed workflows are scripts or agent conventions over those files.
Ollie does not expose a workflow engine, message bus, actor framework, or master coordinator as an external integration boundary. The runtime does contain an internal session event bus for agent and session observers; it is an implementation detail, not a public coordination API. External multi-agent coordination uses sessions, agents, `prompt`, `chat`, `statewait`, `feed`, and `ctl` files. Hub-and-spoke, pipeline, scatter-gather, peer, reactive, and self-directed workflows are scripts or agent conventions over those files.
### No separate frontend control plane