Core Concepts
Architecture
GoClaw is built around a central in-process event bus and a single WebSocket gateway. All components communicate through the bus β no direct inter-component dependencies, no microservices.
architecture overview
text
Key design decisions
- β‘ Goroutine-native: Each channel adapter runs in its own goroutine. The event bus dispatches to subscriber goroutines concurrently β no blocking, no head-of-line problems.
- π No shared mutable state: Components communicate only via the bus or explicit function calls. Never shared variables. Race-condition-free by design.
- π Filesystem-first memory: Plain Markdown files. No database means no migration headaches, no extra process, and easy manual editing from any text editor.
- π Language-agnostic skills: The gRPC contract is the only interface. Any language that can speak Protocol Buffers can be a first-class GoClaw skill.