Today was about tightening navigation and onboarding clarity as we finish the release cycle.
A cleaner way to navigate
We landed the functional navigation context stack under the existing top header. The stack keeps users in the right domain context (inventory, systems, models, cost reports, readiness flows) without mixing account and platform settings pages in the same command stream.
It is intentionally lightweight and practical: users should reach the part of the product they are working in without scanning unrelated areas.
One clear action to begin
The onboarding entry action at registration was simplified to a single clear path:
Create organization.
That removed the previous mixed wording that implied two separate actions and made the flow less direct. Tests were updated so the copy and behavior now match exactly.
Hosted rollout and operational check
The navigation work was packaged and deployed as 20260904.3 · v1.1.0-rc88, then
verified across both hosted cells using health and readiness checks.
This gave us confidence that the navigation runtime and related handlers are running in the same image and route path used by production traffic.
Why this is useful
These are small changes on the surface, but they remove friction where it matters most: how people find their tasks and how new users begin.
For product momentum, small clarity steps add up fast. Each release should make the next action obvious, especially at account creation and when moving through core operations.
Next
Publish the final copy update through normal deployment so both the app shell and hosted route surfaces consistently present the same action language to all users.