Glossary

Plain-English definitions for the terms used across the Obelisk documentation

Page-aware AI

Ask AI about this page

Get answers grounded in the live Obelisk docs set, with source links, selected-text explainers, and prompts for the next document to read.

Use this page when a term appears in the docs and you want the shortest clear definition.

A

  • Account: Your personal identity in Obelisk, including profile, session, and preferences.
  • Active Organization: The organization currently selected in session state. Most tenant workflows depend on it.
  • Admin Console: The platform-wide surface for governing users, organizations, notifications, configuration, and alerts.
  • API Key: A scoped machine credential used to access supported public automation endpoints.
  • Audit Log: A historical record of important operational actions and system events.

B

  • Billing: The subscription, invoice, payment method, credit, and auto top-up workflows for an organization.

C

  • Channel Lab: The organization workspace used to provision and operate managed Dubhe channel deployments.
  • Contract Lab: The organization workspace used to create contract projects, manage revisions, validate changes, and deploy.
  • Credits: Usage-backed value available to an organization for supported product workflows, including AI-assisted features.

D

  • Deployment: A persisted runtime record representing a provisioned or queued runtime workload.
  • Dubhe: The runtime ecosystem surfaced through Contract Lab and Channel Lab inside Obelisk.

I

  • Indexer Lab: The organization workspace used to provision and control managed indexer deployments.
  • Integrations: The organization page that summarizes automation surfaces such as API access, webhooks, notifications, and runtime entry points.

N

  • Notifications: In-app messages delivered to organization members or platform admins, depending on context.

O

  • Organization: The tenant boundary in Obelisk. Most operational, billing, and automation workflows are scoped here.
  • Organization Role: Tenant-local permission level such as owner, admin, or member.

P

  • Platform Alert: A platform-level health, delivery, or incident signal meant for admin review and acknowledgement.
  • Platform Role: Global permission level such as user or admin.
  • Public Deployment API: The authenticated HTTP endpoints exposed for supported deployment workflows.

R

  • Revision: An immutable saved version of a contract project that can be reviewed, validated, and deployed.
  • Runtime Surface: A product area that controls live or queued infrastructure workflows, such as Contract Lab, Indexer Lab, or Channel Lab.

S

  • Session: The authenticated browser state that identifies the current user and active context.
  • Support: The organization-facing surface for requesting help, finding docs, and escalating issues.

T

  • Tenant Isolation: The principle that one organization's data and workflows are separated from another's through access control and scoping.

W

  • Webhook: An outbound HTTP delivery configured by an organization to receive product events.
  • Workspace: A scoped area of the product used for a specific context, usually personal, organization, or admin work.

On this page