Development direction
A view of the work ahead, not a release calendar. Each product advances on its own evidence.
Dataset review and planning, creative queues and libraries, audio project data, image-to-PBR maps, project knowledge, controlled CLI execution and early native runtime work. Hub has a bounded real local Qwen path through Runtime and durable Harness sessions.
Model Lab demonstrations remain simulated. Voice outputs remain mock test tones. Product captures show these distinctions.
Broader provider validation, reproducible quality evidence, target-platform validation, practical packaging and clearer public availability. No download or hosted service is promised before that work is verified.
Core for suite conventions, Graph for shared graph semantics, Runtime for provider/model lifecycle, readiness, ownership and resources. These responsibilities remain distinct; not every app consumes Runtime or Graph. Hub presents requests and audit; it does not own lifecycle.
A future capability-driven operating environment: on-demand services, provider choice, machine profiles and recovery. Concept only; no OS implementation, installer, launch date or compatibility guarantee.
Read the OS concept