What this is
This glossary defines recurring terms in plain language so you can read guides without technical friction.
Why I built this
I built this ecosystem because most teams are forced to jump between disconnected tools, and that creates delays, confusion, and missed handoffs. In real work, people do not need ten dashboards. They need one clear path to choose the right app, finish the task, and move on with confidence. The result is a practical ecosystem where each app has a clear job, and the documentation helps people use that job without technical friction.
Who should use this
- New users entering the Cumulus ecosystem for the first time.
- Team leads who need a clear map of which app solves which job.
- Operators who want step-by-step guidance without technical language.
What you can do today
- Understand role labels such as admin, worker, client, and vendor.
- Understand workflow words such as assignment, run, and approval.
- Use consistent meaning across products without guessing.
Quick start
By the end of this page, you will have a clear and repeatable first outcome in Plain-Language Glossary.
- Open this page whenever a guide uses a term that is new to you.
- Read the short definition and return to your original guide.
- Save this page as your reference while learning the ecosystem.
Known limits and maturity
- Glossary definitions are concise and focused on practical usage.
- If a term changes product meaning over time, guides take priority.
- This glossary intentionally avoids deep technical vocabulary.
- Current maturity: active.