Runtime matrix

Yieldstar separates a runtime family from its connectors. A runtime family defines where coordination, scheduling, and workflow execution live. A connector binds that family to a host runtime and persistence driver.

Version 0.5 ships one runtime family: the resident-process runtime. Its coordinator, event loop, and SQLite connection stay inside one long-lived application process, while each workflow execution runs in a forked child process.

Runtime family	Host	Persistence connector	Workflow execution	Ingress
Resident process	Bun	`@yieldstar/sqlite-runtime/bun` using `bun:sqlite`	`@yieldstar/worker-invoker` child process	Local SDK or HTTP routes
Resident process	Node 22.6+	`@yieldstar/sqlite-runtime/node` using `node:sqlite`	`@yieldstar/worker-invoker` child process	Local SDK or any Request-to-Response HTTP router

The SQLite runtime implementation is shared across both rows. Only createSqliteDb and the native prepared-statement adapter differ, so heap, scheduler, timers, task queue, stores, and event-loop semantics remain identical.

Start with Resident-process runtime, then choose Bun with SQLite or Node with SQLite.