Domain glossary

These terms are capitalized in the VAANI contracts. The definitions below are plain-language entry points; the repository's CONTEXT.md remains the complete domain authority.

ActiveCall

The handle for one accepted call attempt that VAANI now owns. The participant may not be ready yet.

Closure

The one terminal point where VAANI atomically publishes the immutable CallResult and the lifecycle becomes CLOSED.

Consumer

Your application. It owns product behavior, business state, credentials, provider choices, and deployment composition.

Preflight

Validation performed before VAANI accepts lifecycle ownership. A preflight success says configuration is internally usable; it does not prove a provider or LiveKit connection.

Provider-neutral

Expressed in VAANI terms rather than raw provider payloads. Route IDs, errors, usage, and lifecycle evidence can still identify their provider provenance.

Canonical result

The deterministic serialized bytes of one CallResult. The SHA-256 result digest is computed over those exact bytes.

Revision

The committed version of a running call's changeable configuration. Atomic updates use an expected revision so competing decisions cannot silently overwrite each other.

Handoff boundary

The point where deployment-owned work becomes VAANI-owned work. In VAANI 1.0, the deployment hands over an already-routed LiveKit call; VAANI does not own numbers, trunks, SIP credentials, or dispatch.

Continue with the architecture, lifecycle, or result evidence.