Platform behavior cannot be copied blindly
Permissions, background execution, audio routing, and text insertion differ by operating system. Availability is verified per platform rather than inferred from another client.
Platform expansion
Evaluating future client platforms without announcing a release schedule.
A platform name in a product plan is not a release. This note records the technical questions without turning internal direction into a promise.
How account, entitlement, audio, accessibility, and text-delivery behavior should map to operating systems that do not yet have a public ClassEve build.
Which signing, store-review, update, crash-recovery, and support requirements must be complete before a platform can move from planned to public beta.
The artifact is the release boundary
A planned platform has no download button, store URL, release date, or product schema offer. The public registry changes only after a real artifact is verified.
Priority and support capacity
A new platform adds signing, distribution, testing, support, and update obligations. Technical feasibility alone does not decide the order.
Distribution channel
Direct distribution and store distribution have different review, signing, update, and user-trust requirements. No channel is announced until it is operational.
Users should be able to distinguish work that exists from work that is only being evaluated.
Keeping planned-platform records date-free prevents stale roadmaps and lets release pages remain authoritative.