What readiness requires#
The first step is confirming reliable task reading and in-context replies in the Windows Codex environment. Local voice, draft persistence, permissions, installation and update behavior then need platform-specific verification.
A Windows source folder or prototype does not mean those user routes are ready. A released installer and documented acceptance are better evidence than a roadmap label alone.
Use the current route#
For now, use the published Mac companion where appropriate, or work directly in Codex on Windows. Manually transfer a reviewed note if needed; do not call that transfer CueSpec synchronization.
The roadmap does not provide a delivery date, feature-parity promise or Windows minimum-system matrix. Future Windows documentation should specify the actual release, dependencies and limits. It should also separate normal computer interaction from the hardware integration path, so a ready desktop build is not mistaken for complete SPECS 01 control support.