> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dubot.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Object model

> The building blocks behind Dubot experiences

Dubot separates reusable product knowledge and operations from the customer-facing experience
that uses them.

```text theme={null}
Knowledge corpus + Action catalog
  -> capabilities
    -> wizards
    -> Resource Center Agent

Curated content + Resource Center Agent
  -> Resource Center

Brand + page rules
  -> presentation and placement

Reviewed guides
  -> Guidance
```

## Core objects

<CardGroup cols={2}>
  <Card title="Wizard" icon="message-circle">
    The dashboard name for a configured assistant. A wizard combines instructions, capabilities,
    display settings, and at most one placement. The underlying API and runtime entity is an
    agent configuration.
  </Card>

  <Card title="Capability" icon="blocks">
    A reusable package of instructions and context, sometimes including actions. Capability
    types are Skill, Product Domain, Security, and Brand Voice. Each capability is delivered as
    Always, On-demand, or Optional, and can attach to Wizards or the reserved Resource Center
    Agent.
  </Card>

  <Card title="Action" icon="zap">
    A named operation in the workspace Action catalog. For an in-product agent, it becomes
    available through an attached Skill capability. Session API actions call a reviewed product
    endpoint through customer-owned code. Client-side callbacks run a function registered by the
    host application. The end-user MCP channel has separate enablement.
  </Card>

  <Card title="Knowledge" icon="book-open">
    The workspace Knowledge corpus: the governed source material that capabilities and agents
    can use. It is distinct from the instructions and context packaged by a capability.
  </Card>

  <Card title="Guide" icon="route">
    A reviewed Guidance sequence containing message, perform, indicate, and ask steps. Guides can
    launch from the Resource Center or another supported entry point.
  </Card>

  <Card title="Placement" icon="panel-right">
    Where and when one wizard appears. The current modes are bubble, inline, sidebar, and
    fullscreen, with optional page targeting.
  </Card>

  <Card title="Resource Center" icon="library">
    A first-class, page-aware destination with curated content, Search, Ask Agent, settings,
    trigger and availability controls, and analytics. Its reserved Resource Center Agent saves
    and publishes with the Resource Center and has no placement.
  </Card>
</CardGroup>

## Workspace-owned objects

Each workspace also has:

* a Resource Center configuration and its reserved Resource Center Agent;
* a separately governed reserved Guidance configuration;
* one or more brand configurations, with an optional default;
* Test and Production versions of publishable configuration;
* team, identity, SDK, and MCP settings.

## Naming: wizard and agent

The Dubot application uses **Wizard** for the assistants that end users see. Technical interfaces
retain **agent** in routes, identifiers, artifacts, and API field names. In these docs, wizard
means the product experience; agent is used only where the technical name matters.

<Note>
  A guide is not a rigid browser recording, and a capability is not a standalone end-user
  surface. Guidance is separately governed, and reviewed guides can launch from the Resource
  Center. Those distinctions keep reusable context, reviewed behavior, and presentation
  independently governable.
</Note>