Runtime architecture
Control and data
Section titled “Control and data”Native central and Host roles use the same App executable. A normal launch starts the central process; module launches start App subprocesses that load plugin libraries. Python modules continue to use the selected CPython interpreter.
The central runtime manages module lifecycle and framework services. Each module has its own process, a shared Socket control protocol, and bidirectional heartbeat. Message Bus payloads use shared memory; registration and topology use the control channel.
Each Publisher owns a RingBuffer. A topic may have several Publishers. Subscribers receive local copies; publishers may push local messages or borrow fixed-capacity shared storage before commit.
Isolation has boundaries
Section titled “Isolation has boundaries”Heartbeat indicates process communication, not the health of every user function. Shared resources require ownership and confirmed process-exit cleanup. Process isolation is not a security sandbox or a hard real-time guarantee.
Read the Message Bus design for ordering, collision waits and recovery contracts.