Product news
What shipped, and what it changes.
Release notes and platform announcements, written so you can tell whether a change affects a workflow you already run.
Change-led
What it changes, not what it is called
Scoped
Says who is affected and who is not
Free
No signup
Introduction
What an entry here is supposed to tell you.
Release notes are only useful if you can tell in one read whether they affect you. Each entry states what changed, who it affects, and whether any action is required — before it describes the feature.
Where a change is default-off or gated behind a flag, that is stated, because "shipped" and "affecting your workspace" are different things and conflating them is how release notes lose trust.
- Format
- Change, scope, action
- Engineering detail
- On the blog
- Cost
- Free, no signup
- Cadence
- On release
Why this exists
Most release notes optimise for announcement rather than for the reader.
The common format leads with the feature name and buries whether anything is required of you. That makes the reader do the work of figuring out relevance, which most will not do, which defeats the point of publishing.
The second failure is treating a shipped-but-disabled change as a live one. Stating the rollout state is the difference between a useful note and a marketing item.
You're likely here because
- You need to know whether a change affects a running workflow
- You are auditing what changed in a period
- A behaviour changed and you want to know when
How to choose
Where to look.
If
You want to know what changed recently
Start with
The entries below
If
You want engineering detail behind a change
Start with
The blogIf
You want how the platform works overall
Start with
The platform pagesIf
You want security or compliance posture
Start with
Trust and securityHow it works
What each entry states.
Step 01
What changed
The behaviour difference, in one sentence, before any feature naming.
Step 02
Who it affects
Which workspaces, plans, or workflows are in scope — and who is explicitly not.
Step 03
Rollout state
Whether it is live, gated, or default-off, since shipped and active are different.
Step 04
Action required
What you need to do, including "nothing" where that is the answer.
Step 05
Where to read more
A link to the deeper explanation where one exists.
Announcements
Recent news.
Announcements
Only source-backed company updates belong here.
The repository does not currently contain an approved historical announcement set to restore into this page. Rather than manufacture a press archive, this surface stays factual and ready for real releases as they are approved.
01
Company
Corporate announcements, operating-layer milestones, and UbiGrowth updates.
02
Platform
Material UbiVibe and ARIA product announcements when they are approved for public release.
03
Products
Launch and Grow releases that materially change what customers can build or operate.
Scope
What this page will not do.
- It does not announce roadmap items that have not shipped.
- It does not present a default-off change as generally available.
- It does not name customers in announcements.
- It is not a substitute for the security page on compliance posture.
FAQ
Questions about this collection.
How is this different from the blog?
News covers what shipped and what it changes. The blog covers engineering write-ups, usually about failure modes and how a design responded.
Do you announce roadmap?
No. Entries here describe changes that have shipped, with their rollout state stated.
How do I know if a change affects me?
Each entry states scope and required action near the top, which is the whole point of the format.
Where do I find security notices?
Security posture lives on the trust and security page; material notices are communicated directly rather than only published.
Can I subscribe?
No gated list. Entries are published here as changes ship.
What does default-off mean?
The code has shipped but the behaviour is not active for your workspace until enabled. It is stated because the distinction matters.
Keep exploring
Related paths.
Start with ARIA
Ask ARIA about news.
You do not have to pick your way through this collection to get started. Describe the outcome you want and ARIA determines which capabilities, systems, and workflows the job needs.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Changes are easier to judge against a running workflow.
If you are trying to work out whether something affects you, describing the workflow to ARIA is faster than reading the archive.