Routing and Labels
Orgo uses Labels as a compact routing and classification language.
A label can express three things:
- a vertical or organizational scope;
- a category and subcategory;
- an optional horizontal role.
The general form is:
<BASE>.<CATEGORY><SUBCATEGORY>[.<HORIZONTAL_ROLE>]
Example:
100.94.Operations.Safety
The precise codes are configured and documented technically, but public users mainly need to understand the idea: a label is an address for operational context.
Labels are not permissions
A label can help determine where work belongs, but it does not replace authorization.
Seeing a routing label does not automatically grant access to the underlying Case or Task.
One canonical routing label
Orgo keeps one canonical routing label on the work object rather than trying to encode every possible taxonomy dimension into one string.
Additional classification can live in metadata, tags or domain-specific structures.
Broadcast labels
Some label bases represent broadcasts.
A broadcast is informational by default:
broadcast
≠ mandatory Task
If the information requires action, a workflow must explicitly create or assign that work.
This prevents announcements from silently becoming obligations.