Runtime architecture¶
The current runtime has two HTTP boundaries that serve different callers:
- The Handler accepts application interaction requests.
- The Pipeline coordinates dialogue-processing services for the Handler.
Tala supplies DDD loading, shared semantic models, and authored NLG realization. TDM's Dialogue Management Engine (DME) updates the dialogue state and selects moves from those models. NLU/NDU and NDG services participate in interpretation and realization. The Pipeline also performs Tala's in-process NLG realization and coordinates calls according to the request, session, configured endpoints, and enabled neural settings.
Request path¶
Application
│ interaction request
▼
Handler (/interact/{offer_id})
│ prepares offer/session and forwards request
▼
Pipeline (route `pipeline-fn`; direct path `/api/pipeline-fn` by default)
├── language understanding and interpretation
├── DME dialogue processing
├── optional follow-up component calls
└── response enrichment
│
▼
Handler response to application
The Handler may load an offer when the session does not already contain its ODB. An existing session.offer_id takes precedence over the route's offer_id; changing the route while continuing an existing session does not switch offers. The Handler forwards the request to the Pipeline, handles any service invocation requested by the Pipeline, and resubmits the result until a user-facing response is ready. It also applies Handler-specific behavior such as session encryption, wakeword handling, and response timing.
The Pipeline's request runner prepares session data, coordinates interpretation and DME processing, may restart interpretation after an ASR/NDU correction, then enriches the response and trims dialogue history. It invokes NLG through Tala in-process; NLG is not a separately configured FUNCTION_ENDPOINT_* service. This is asynchronous service orchestration, not a single direct DME call.
Repository ownership¶
| Component | Responsibility | Main boundary/model |
|---|---|---|
| Handler | Application interaction boundary | Session lifecycle and /interact/{offer_id} |
| Pipeline | Runtime orchestration | Component calls and /pipeline-fn |
| Tala | DDD loading, semantic models, and NLG realization | DDD formats, shared model vocabulary, authored NLG |
| TDM/DME | Dialogue management | Dialogue state and move selection |
The production endpoint configuration is supplied to the deployed services. This site documents configuration names and behavior, not environment-specific URLs, credentials, or deployment values.
Revision and compatibility boundary¶
Implementation details in this reference correspond to these source revisions: Handler 44616a5e34b6, Pipeline 34c971f1aef8, TDM f555673fec31, and Tala 31.0.2 source commit bc6f9cbabf81. These identify the documented source snapshots, not necessarily the deployed revisions. DDD syntax and compiler behavior in the authoring references use Tala 31.3.0; the cited Tala commit identifies the older snapshot used for these architecture details. The Handler version cited here registers only /interact/{offer_id}. Wakeword handling occurs within that route and does not create a separate legacy interact route. Check deployment revisions before relying on implementation-specific details.
The Handler, Pipeline, and TDM versions cited above have service-continuation contract mismatches. In particular, Handler action/validator result payloads do not match TDM's declared request schema, and Pipeline's service-result guard expects an event marker that Handler's continuation does not add. Service action and validator round-trips are therefore not compatible across these specific revisions; see the API pages for details.