What this is
This page defines Hub status labels so users can make good launch decisions before starting work.
Why I built this
I built Hub so people can launch the right side project from one place and understand current readiness at a glance. Side projects are useful only when access is simple and status is obvious, otherwise they become scattered bookmarks. Hub acts as the front door with clear launch links and status labels so work can move quickly.
Who should use this
- Users who work across multiple Cumulus side products.
- Operators who need one launch point instead of many bookmarks.
- Teams who need status context before opening a project.
What you can do today
- Read status labels with practical interpretation.
- Choose stable products for critical tasks.
- Avoid confusion when a product is still evolving.
Quick start
By the end of this page, you will have a clear and repeatable first outcome in Hub Project Statuses.
- Check status label before launching any side project.
- Use Active paths for time-sensitive work.
- Use Building paths for exploration and feedback.
Known limits and maturity
- Status values can evolve as products mature.
- A status badge is not a substitute for product troubleshooting guidance.
- Always confirm workflow behavior in first run when status is Building.
- Current maturity: active.