Product docs

Reference

Glossary

Definitions for common ArchiBot Console, workspace, access, billing, delivery, and support terms used across the docs.

Customer adminsCustomer membersPlatform operators

Last updated

ArchiBot Console with the grouped navigation rail and My Workspaces, on safe example data.
Console example with safe data: glossary terms describe the product surfaces, roles, workflows, and controls shown throughout the docs.

Use this page when a guide uses an ArchiBot-specific term. In each language, the first occurrence of common terms links here and shows a short definition on hover or keyboard focus.

Core surfaces

ArchiBot Console

The customer-facing web app for account setup, workspace creation, access, usage, support, and operator views. Console is where most customer and operator workflows begin.

ArchiBot Chat

The hosted chat and API surface for ArchiBot. It uses approved account access, the customer’s Universal Archibot Credit wallet, and data-boundary settings before it processes requests.

Workspaces

Workspace

A customer-scoped development environment with the editor, runtime, source checkout, and services needed for assigned work.

Browser IDE

The browser-based editor opened from Console for working inside a running workspace.

Template

An approved workspace blueprint that sets the image, runtime defaults, parameters, and startup behavior for new workspaces.

Runtime

The software and services inside a workspace that run the editor, application stack, database access, tools, and bots.

Workspace preset

A reusable, non-secret launch shape. The Create preset library is currently turned off, and /presets opens Create Workspace; repeat a launch by setting the same Create checklist values.

Workspace source

The code source selected in Create Workspace: a connected Git repository or, where supported, a managed WebCentral WAR artifact. The WAR path does not require a Git branch.

Backup

A prepared restore source, such as a database or project snapshot, used to start or rebuild a workspace from known data.

Shared Drive

The customer-scoped file store for sanitized artifacts, handoff files, exports, and evidence that should outlive a workspace.

Workspace bot

The managed ArchiBot assistant available inside a workspace through the terminal or editor panel.

Git Health

A workspace check that reports repository connectivity and checkout status without requiring a terminal.

Roles

Customer admin

A customer user who manages account setup, invites, workspace readiness, billing details, and allowed customer operations.

Customer member

A customer user who creates, opens, and manages their assigned workspaces and allowed Chat access.

Platform operator

An ISM operator who supports customer setup, readiness, incidents, and approved operational actions.

Access and security

SSO

Single sign-on through the customer’s identity provider. Console uses it to sign in users and map them to approved roles.

API key

A generated credential for the public API surface. Treat it like a password, and rotate or revoke it when needed.

Data boundary

The approved limit on what data may be entered, uploaded, processed, stored, or shared through an ArchiBot service.

Managed AI

ArchiBot-owned routing, prompting, metering, and policy controls around approved AI model usage.

Billing

Universal Archibot Credits

The canonical credit_v1 unit used across ArchiBot services. Browser Chat and generated /v1 response requests reserve and debit the same customer wallet. One hundred Archibot Credits represent one US dollar of metered value.

Delivery

CI & Review

The Console workflow for running checks, review, QA, and promotion gates against code or environment changes.

Persistent environment

A longer-lived workspace-backed environment used for review, QA, demos, or promotion instead of short personal work.

Design work details

The Design Work details panel: a work revision’s objective, resolved product, view, workspace and repository context, constraints, and definition of done. It helps check context; it does not prove runtime validation.

Usage estimate

A scoped Analytics value for the selected team and time window. Estimates, provider reconciliation, and finalized billing records are distinct; a missing ledger value is not zero.

Support

Operations

The Console area for customer-scoped health, capacity, workspace, bot, CI, storage, and support signals.

Support handoff

The sanitized context package sent to support: visible error, time, account, workspace, and steps, without secrets.

Done When

  • You can distinguish Console, Chat, workspace, and support terms.
  • Inline glossary terms in other guides link back to this page.
  • You know which terms describe roles, access, billing, delivery, and support.