Developer API documentation
Building contextual references, request examples, response guidance, and clearer integration paths.
Public roadmap
Direction, without false certainty.
Follow what is complete, actively being built, and being considered across the ecosystem. Priorities evolve as the evidence gets better.
4Completed
5In progress
6Planned
Now and next
Work in motion.
Filter the timeline by delivery stage. Dates appear only where confidence makes them useful.
Accessible interface patterns
Preparing framework-free navigation, dialog, search, and disclosure patterns for public release.
Contributor pathways
Define useful first contributions, review expectations, and a transparent maintenance model.
Desktop companion research
Validate whether a native companion solves meaningful offline or workflow problems before committing to a build.
Premium public headquarters
Delivered a connected product, documentation, editorial, community, roadmap, release, and status experience.
Connected domain model
Established clear boundaries for discovery, identity, private workspace activity, and developer APIs.
How to read this
Commitment without theatre.
The roadmap publishes problems and stages of progress. The changelog records what actually shipped.
- 01
Problems before features
Items may change shape as the underlying need becomes clearer.
- 02
Evidence changes priority
Research, quality findings, and useful community context can reorder work.
- 03
Completed means shipped
Finished work moves into the changelog as a durable release record.
Add context
Share feedback Help sharpen the direction.
Describe the problem, who experiences it, and what a better outcome would unlock.