execution_id correlates the work
It is the authoritative business-execution correlation identity; call/session/provider/device identities remain separate.
Developers
Build continuity into the journey.
Not another isolated channel.
Jodoworld exposes governed SDK, API, event, webhook and adapter surfaces around business domains. Provider infrastructure does not become the owner of business truth.
The mental model
Business flow outside. Precise identities inside.
Participants are not endpoints
Human, AI, automation and system identity remain distinct from the browser, number, SIP device or other reachability endpoint.
Authority is contextual
Identity, entitlement, acting capacity and step authority remain separate.
Providers are transport or capability routes
Carrier, AI and media providers do not own tenant, workflow, handoff or business-outcome truth.
Facts are not recommendations
Evidence, metric, inference, recommendation and approved action stay distinguishable.
Approved Product contracts
New developer surfaces are being defined around a broader communications model.
Exact services, schemas, APIs, algorithms and provider adapters are defined in controlled technical specifications for the implementation scope.
Communication identity
Business-facing alias, presentation identity and endpoint remain separate Product objects.
Capability profile
Country, provider, recording, AI, RTLT and number eligibility can be release-profile controlled.
Carrier portfolio
Multiple carrier configurations can coexist without creating duplicate execution truth.
Temporal policy
Local time, business hours, holidays and after-hours paths become governed inputs.
Management signals
Evidence can lead to a signal, recommendation, approval and validated action without conflating those states.
Metric definitions
Material metrics carry formula, inputs, scope, version, owner and evidence/inference classification.