Glossary
This page uses public-facing definitions. The technical documentation contains the exact contracts and schemas.
Organization
The tenant and operational boundary in Orgo. Cases, Tasks, profiles and permissions belong to an Organization.
Signal
An input that may require work: an email, form, API call, event, offline input or similar trigger.
A Signal is not automatically a Task.
Case
A durable container for a situation, its context and related work over time.
Task
The canonical unit of work in Orgo.
Workflow
Rules that evaluate signals or operational context and determine what actions should follow.
Label
A compact routing/classification address used to help place work in the right operational context.
Profile
Organization-specific behavioral configuration, including defaults for reactivity, transparency, retention, pattern sensitivity and automation.
Domain module
A specialized layer for a domain such as Maintenance, HR or Education that adds context while reusing the common Task/Case engine.
Insight
A derived analytical view over operational activity.
Cyclic Overview
A recurring review loop that turns operational history into organizational learning and, when appropriate, new governed work.
User
An authenticated Orgo actor/account.
Person
A human subject/profile represented in Orgo, whether or not the person has a User account.
Charter
A semantic vocabulary/reference layer that helps Orgo reuse and refine common concepts across domains.
Receipt
Structured evidence that an external or internal operation was accepted, rejected or executed. It helps Orgo reconcile workflow without replacing the authoritative state it refers to.
Ecosystem system
A system with its own significant domain authority and boundaries. Orgo is one ecosystem system in the kOA Digital Ecosystem.