Quest and World State Integrations

Review draft. This source page has not completed website editorial and release-specific verification.

Dialogue Director owns Dialogue definitions, traversal, and history. Quest Director owns Quest definitions, state, and event semantics. World State owns its keys and values. Their canonical optional Dialogue integrations are supplied by DirectorBridge; no domain bridge implementation is included in the Dialogue product.

Dialogue remains standalone. Its generic Runtime contracts include reflected and native external Condition providers, native Action routes, and optional Event sinks. Its Editor contracts include generic authoring providers, preview extensions, and interchange adapters. Providers translate typed domain payloads and report explicit unavailable or failure results. The Dialogue Editor and Runtime do not depend on Quest Director, World State, or DirectorBridge.

Install the relevant owner plugins and optional DirectorBridge integration only in a host that uses those domains. Integration-specific setup and semantics are documented with DirectorBridge. This guide describes Dialogue-owned extension boundaries and does not duplicate integration implementation documentation.

Relationship Probability remains a separate optional DirectorBridge integration. Dialogue’s resolution provider contract stays Probability-neutral, and Dialogue remains independent from Probability Director.

See V1 Workflow Examples for provider-independent authoring and C++ API for Dialogue-owned provider contracts.