The system is usable now. This compact roadmap communicates product direction and the major capability sequence. It is direction, not a release calendar.
Next sequence: Composer first, Attachment second, then the agent context-efficiency baseline before the system and its documentation expand further.
Semantic tokens, layout primitives, accessibility roles, machine-readable exports, and validation form the base of the system.
Framework-free references and machine-readable contracts define the approved component API and its states.
Replace identity assets, fonts, and semantic mappings, then regenerate the adapters without rewriting components.
Message is available. Composer is the next component; Attachment follows immediately after it. Conversation waits until both contracts are proven.
Define chart selection, semantics, formatting, accessibility, and responsive behavior, then prove the language through a production charting-library adapter.
Complete App shell, Dashboard, Settings, and Conversation as realistic integration specimens over approved components.
Show what an automated agent is doing, what it has completed, where it is blocked, and when it needs a person’s permission before taking a consequential action.
Implement production components against the same contracts while keeping runtime behavior out of the foundation layer.
Turn natural-language direction into a complete token candidate, run the existing gates, and preview only systems that pass.
A pattern moves to Available only when its contract, reference implementation, accessibility and state rules, and validator all agree. Until then, the name is a destination, not an API.