Multi-Agent Is Not Multiple Agents: Parent Runs, Fan-out, and Fan-in
Model child lifecycles, isolated state, and partial failure as one execution tree
AI & AX / Subsection
Research, foundations, and current analysis filed under Agents.
Model child lifecycles, isolated state, and partial failure as one execution tree
Separate graph state from application state to assign responsibility across workers, Redis, databases, and browsers
Safely stream snapshots and events over an HTTP connection with async generators
Linking user intent to side effects so a transfer tool does not run twice
Restore the screen from a snapshot, then keep its timeline complete with cursors
Durable records, hot projections, and resumable snapshots survive different failures
Separate concurrency primitives from ownership of the execution lifecycle
Waiting, blocking SDKs, and CPU-bound computation require different execution tools
Turn time spent waiting on LLMs, databases, and search APIs into concurrency
Execution architecture boundaries — mental model, failure modes, optional deep dives
Compose bounded control flows instead of building one giant autonomous loop