client-sdk is the designated consumer-facing boundary layer between human intent and the Omni-Dromenon generative engine — the single conduit through which audience votes, performer parameter commands, and observer data streams all flow. Two artifacts are working today: a zero-dependency EventBus (typed pub/sub with configurable history, returnable unsubscribe functions, and no external dependencies) that any sibling repo can import immediately, and a PoiesisClient skeleton with a typed connection-state machine, request-correlation infrastructure, and sensible config defaults that already establishes the correct API contract. The library's highest latent value is architectural: by formalizing three distinct connection roles — audience (vote-only, filtered events), performer (full read/write parameter control), and observer (full read-only stream) — with differentiated TypeScript API surfaces and server-side authorization scope, it gives every downstream consumer a single coherent interface rather than ad-hoc WebSocket logic, unlocking performance-sdk UI components, a-mavs-olevm audiovisual integration, and ORGAN-III SaaS audience-participation products. The single best concrete first task is to replace the simulated transport in PoiesisClient.connect() with an actual WebSocket implementation (Node.js built-in / browser native), which would make the library immediately consumable by its two primary dependents without changing any public API surface.