Functions and intents

Functions are model-facing tool definitions. Each function has a name, description, and structured parameter schema. Intents are normalized action requests produced by those tool calls or other supported runtime detection.

An intent router maps the function or intent name to an adapter. The active policy determines which custom functions and adapters are available. This keeps model reasoning separate from external side effects.

The runtime also supplies definitions for hangup, call_transfer, and conference. A tenant function with the same name can replace the default definition. The definition alone does not perform the action; a compatible adapter and intent route are still required.

Functions, routers, adapters, and policies are reusable tenant objects. Their Bot assignments must form a complete dependency graph before the control plane will publish them to a runtime.