Node architecture

Muxiva Runtime executes only Nodes. There is no separate Provider runtime entity. Agora, Qwen, and FFmpeg are namespaces for officially maintained Nodes; they use the same Manifest, Ports, Frames, lifecycle, and Registry as project Nodes.

flowchart LR
  B["Built-in Nodes<br/>compiled with Runtime"] --> R["One Node Registry"]
  O["Official Nodes<br/>Agora · Qwen"] --> R
  P["Project Nodes<br/>.muxiva/nodes"] --> R
  R --> G["Graph · Studio · Runtime"]

Source	Examples	Meaning
Built-in	builtin.audio_resampler	Generic and vendor-independent
Official	agora.audio_source, qwen.audio_realtime	Maintained integrations and examples
Project	my_agent.rag	Developer-owned code under .muxiva/nodes/

A Node Manifest may declare a connection_id; secrets are stored in the project's .env. Connection configuration does not create another runtime abstraction.

Developers can copy an official Node layout into .muxiva/nodes/<package>/ and implement Rust, Python, TypeScript, or C++. Studio discovers it and shows it in the same Node Library.