Skip to main content

Services Overview

Services are the main runtime-facing layer used to interact with Dialogue systems and data.

In practice, a service is the object that owns a specific part of the conversation pipeline. It sits between raw dialogue data and the rest of the runtime.

What to expect from this section​

The service pages are reference-style documents. They are most useful once you already understand the feature area and want to know which runtime object is responsible for a specific part of the system.

When to read service docs​

Read the service docs when you need to:

  • understand ownership of a system
  • find the right abstraction for a feature
  • trace how a concept is exposed to the rest of the module
  • match runtime responsibilities to guide concepts

Before diving into service pages, read:

  1. Guides Overview
  2. Introduction to the Dialogue System
  3. Architecture Overview

How service pages are structured​

Most service pages describe:

  • what the service is responsible for
  • where it fits in the larger system
  • the main interface it implements
  • the public properties and methods you are most likely to use or inspect

Important note​

The Dialogue module uses the same shared bootstrap and service registry model as CIVIL-AI-SYSTEM. Services are registered in DialogueModuleRegistrar and resolved through the shared IServiceRegistry.

When both modules are installed, Dialogue can consume shared services such as IWorldClock and IItemCatalog provided by CivilAI. When running standalone, Dialogue registers its own fallback implementations.

Last updated on