> ## 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" href="/product/wizards">
    A configured assistant that combines instructions, capabilities, display settings, and one
    placement.
  </Card>

  <Card title="Capability" icon="blocks" href="/product/capabilities-actions#capabilities-are-the-composition-layer">
    A reusable package of instructions and context. Skill capabilities can also expose approved
    actions.
  </Card>

  <Card title="Action" icon="zap" href="/product/capabilities-actions#actions-are-catalog-contracts">
    A governed product operation exposed through a Skill capability. Current types are Session
    API actions and client-side callbacks.
  </Card>

  <Card title="Knowledge" icon="book-open" href="/product/knowledge">
    The reviewable workspace corpus available to experiences through an explicit retrieval scope.
  </Card>

  <Card title="Guide" icon="route" href="/product/guidance">
    A reviewed Guidance sequence containing message, perform, indicate, and ask steps.
  </Card>

  <Card title="Placement" icon="panel-right" href="/product/wizards#choose-a-placement">
    Where and when a wizard appears: bubble, inline, sidebar, or fullscreen, optionally targeted
    by page.
  </Card>

  <Card title="Resource Center" icon="library" href="/product/resource-center">
    Page-aware support with curated content, Search, Ask, and its reserved Resource Center Agent.
  </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>