Roadmap · 2026-10-25
The private runtime is deployed and verified. General public distribution, signed installers, and the full quality and hardware certification remain unfinished. The remaining work includes unfinished setup, external account/device prerequisites, and quality evidence. These are different kinds of work.
Accept any further model family, custom node, video mode, or renderer/control combination against its exact installation before use.
Why it remains: The installed SDXL and conditioning cases are verified; that evidence cannot certify every upstream model or extension.
Configure Firefly/ElevenLabs credentials, wider xAI key permissions when needed, Google Photos Picker OAuth, and any additional billing accounts.
Why it remains: These paths need real credentials or account consent; they cannot be supplied by documentation or tests.
Use representative benchmarks with hard negatives, multiple characters, and clothing, pose, lighting, location, and style variation. The first fixed render set is recorded, including its subject-count and pose failures.
Why it remains: Successful execution proves the path works. It does not establish accuracy or safe strict-continuity thresholds.
Complete missing real archive/phone, separate-machine, reboot/failure, and large-library scenarios.
Why it remains: Component tests and emulator checks do not certify every production environment or workload.
Finish signed/notarized packaging, Android release signing, public privacy/provenance review, and release certification.
Why it remains: The working private installation is a different milestone from a supported public download.
The native API batch exposes 881 non-deprecated operation contracts across seven providers, including native parameters, managed uploads, streamed results and original-job polling. API versions are included in that count. Another 52 deprecated contracts are hidden from normal discovery and retained only for explicit legacy recovery or migration; 14 signed transfer helpers are counted separately. Remaining account permissions and credentials are access prerequisites, not missing provider connections.
The UI is optional. Further native-view and accessibility checks cannot become a prerequisite for agent operation. Peer delivery through HawkSpan is a separate, unaccepted integration in the reference installation. Automatic OpenAI Batch scheduling remains disabled; explicit native Batch requests follow the task’s authorization. concurrent provider rendering and coordinated parallel creative agents remain future options.
Permanent runtime directories, broad Resolve integration, the current Descript connection, and installed local analysis providers are completed work. Old status snapshots are not instructions to build them again.
Read this roadmap as Markdown