> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rodyne.xyz/llms.txt
> Use this file to discover all available pages before exploring further.
# Glossary
> Rodyne terms used across setup, operations, and provider outcomes.
A server-enforced action grant such as `tickets.write`, `ranks.approve`, or `integrations.manage`.
Rodyne's first-party identity and controlled multi-community network system.
Optional workspace access derived from the member's current roles in the connected guild.
A retry identity that prevents the same logical mutation from creating duplicate records.
A Roblox Group ID and Rank ID joined to a Discord role and Rodyne policy fields.
A reviewed, member-safe view of one eligible source record. It can be withdrawn without erasing its audit history.
The workspace group whose ladder powers normal promotion, demotion, and rank requests.
A mapping that cannot be requested as a target and whose Discord role is not automatically changed.
A follow-up query that confirms Discord or Roblox now holds the intended state.
A bound group used for Discord role synchronization but not ordinary rank requests.
A provider write may have applied, but Rodyne could not safely prove the result. It requires live-state review before retry.
The stable experience identifier used to scope Studio connector credentials. It is different from a place ID.
A Rodyne community boundary with its own staff, provider resources, records, permissions, billing, and audit trail.
## Guided walkthrough
The screenshot above is from the live Rodyne product. Use it to orient yourself, but rely on the current record state and live provider checks when operating the workspace.
## Operating procedure
Identify whether the term describes a tenant, identity, configuration, record, or provider outcome.
Determine which workspace or network controls it.
A mapping or approval describes intent; provider read-back describes reality.
Use the linked guide for procedures and the reference page for exact behavior.
Record uncertain, partial, and completed outcomes distinctly in staff notes.
## Acceptance checks
| Check | Ready when | If it is not ready |
| --------- | -------------------------------------------------- | ------------------------ |
| Workspace | Tenant boundary is explicit | Name the community |
| Identity | Provider IDs and ownership proof are distinguished | Resolve the link state |
| Outcome | Desired and confirmed state are not conflated | Check provider read-back |
## Failure recovery
When two staff members use a term differently, link the record and its glossary definition. Precision matters most for identity, restricted data, approvals, and provider outcomes.
## Continue the workflow