One source of authority for a governed media session

cRUD Research TeamThe cRUD Company

Whitepaper designed for the web

A media session becomes difficult to trust when the customer product, several provider dashboards, client devices and background workers can each appear to decide what is true. This whitepaper defines one source of authority for the media work while preserving the customer product's authority over its users, roles and commercial decisions. It explains the operating model behind Orchestrate in cRUD Morph.

Executive summary

  • The customer product remains authoritative for its business identity, users, roles, entitlement and experience.
  • cRUD Morph becomes authoritative for approved media sessions, provider allocations, Program Output, recording lineage and media evidence.
  • Commands are idempotent, state changes are durable and provider callbacks are treated as evidence that must be reconciled.
  • A provider cannot silently become the source of customer-facing truth.
  • Every accepted operation should produce an explainable state and a stable outcome record.

Authority is a product boundary

One source of authority does not mean one system owns everything. It means every fact has exactly one recognised owner. The customer product owns the customer organisation, product users, business roles, registration, entitlement, prices and the experience it promises. The media foundation owns the media session, approved provider resources, delivery state, Program Output, recording lineage and the evidence produced by that work.

A governed connection maps those two domains without copying them. The customer product supplies stable external references and authorised intent. cRUD Morph returns its own resource identifiers, states and contract events. Neither side should infer the other's business facts from a provider room, a webhook payload or a temporary client connection.

Why sessions split into competing truths

Direct provider integrations often begin with a room created from application code. Over time, the room identifier appears in product records, client state, support tools and analytics. A callback says the room started. A client says it disconnected. A recording worker says the session ended. Each event can be valid in its own context, yet none of them alone defines the customer-facing session.

The problem becomes sharper with several providers or output forms. An interactive room, an audience stream, a recording job and a replay asset can each have separate lifecycles. If the application interprets them independently, partial success can look like complete success and retries can create duplicate work. Orchestrate keeps those resources beneath one media-session identity and one approved policy.

The lifecycle of authoritative intent

An operation begins with authorised intent from the customer product. The request identifies the tenant, environment, external reference, required capability and idempotency key. cRUD Morph validates the boundary, records the accepted request and plans the media work. Provider allocation follows approved policy rather than client preference or an unreviewed callback.

State changes are committed before corresponding contract events leave the boundary. Consumers may receive an event more than once, so every envelope carries stable identity and sequence information. A repeated command with the same idempotency key returns the established result instead of creating a second session. A different command cannot borrow the identity of the first.

This pattern separates acceptance from completion. Accepted means the request passed the contract and has a durable identity. Running means approved work is active. Completed means the defined outcome has been reached. Failed, cancelled and unknown remain explicit. None of those states is inferred merely because one provider resource exists.

Provider allocation is execution, not authority

A provider supplies capacity and reports what happened inside its service. It does not decide customer entitlement, participant roles or whether an overall product operation succeeded. cRUD Morph keeps provider-specific types, identifiers and errors behind adapters. The core receives normalised capabilities, receipts, health and failure categories.

This matters even when only one provider is active. The boundary prevents the first integration from becoming the product model. It also supports cRUD BYOP, where the customer owns the provider account, cRUD MIP, where The cRUD Company operates approved capacity, and hybrid arrangements where ownership differs by component. The authority model remains stable while the operating model changes.

Reconciliation closes the gap between intent and observation

Provider callbacks, polling results and client telemetry are observations. They may arrive late, arrive twice or never arrive. Reconciliation compares those observations with the durable intent and current session state. It can confirm completion, request missing evidence, retry safe work or move an operation to an explicit failure or unknown state.

A reconciliation loop must not invent success. If a recording provider reports a file but the approved Program Output lineage is missing, the recording is not ready for customer use. If an audience route is healthy but presentation state is stale, the overall experience needs investigation. Each component contributes evidence without taking over the session authority.

Roles, permissions and server authority

Clients receive only the authority required for their approved role and current operation. The server establishes tenant and environment context. A speaker may publish an approved source. A producer may change Program Output composition. An audience member may receive selected media and state. None of those client capabilities grants permission to redefine the underlying product role.

Time-limited authority reduces the cost of a leaked token and prevents an old client state from remaining active indefinitely. Revocation, participant removal and policy changes are server decisions. Clients can request and observe, but the authoritative transition is recorded by the media foundation.

Outputs belong to the same session

Program Output, recording, replay and destination delivery are not unrelated jobs. They are outputs of authorised session work. Orchestrate links their identities and states so that the product can tell which composition reached the audience, which version was recorded, when replay became ready and which destinations received an approved output.

This linkage supports reuse without losing meaning. A replay can inherit lineage from the live programme. A Simulive session can identify its approved source. A social destination can receive the same Program Output while maintaining its own delivery receipt. The system keeps one programme meaning without pretending every path is identical.

Operational evidence and audit

A useful session history connects authorised requests, policy versions, provider allocations, state transitions, output lineage, delivery observations, retries and final outcomes. It does not need to expose private implementation or provider secrets. It needs enough stable evidence for the customer and operator to explain what was requested, what was permitted, what operated and what happened next.

That distinction matters during support and legal review. A provider dashboard may show activity, but it cannot establish the customer's consent, entitlement or business decision. The customer product remains the source for those facts. The cRUD Morph record explains the media work performed under them.

How to evaluate session orchestration

Run more than the happy path. Repeat the same create request. Deliver the same callback twice. Delay one provider receipt. Disconnect and reconnect a speaker. Fail an audience path while recording continues. Cancel while a retry is pending. Change a role after client authority has been issued. For each case, ask which state is authoritative, whether duplicate work appeared and whether the final record can explain the outcome.

A credible platform should also show how tenant and environment boundaries are enforced, how provider types stay out of public contracts, how unknown states are handled and how a provider can be changed without rewriting customer identity. Architecture diagrams help, but the proof is in deterministic behaviour under repeated and incomplete evidence.

Conclusion

A governed media session needs one authoritative media lifecycle, not one system pretending to own the complete customer product. Clear fact ownership, idempotent commands, durable state, provider reconciliation and connected outputs let the product retain authority while complex media work remains contained. That is the purpose of Orchestrate within cRUD Morph.

Basis and methodology

This whitepaper describes the public operating principles of cRUD Morph. It is an architectural explanation, not a disclosure of source code or private implementation. It reports no external benchmark or provider certification. Exact providers, capabilities and commitments are confirmed for each technical engagement.

For the public product boundary, review the cRUD Morph approach, capabilities and documentation.

Frequently asked questions

What is the source of authority for a cRUD Morph media session?
cRUD Morph is authoritative for the approved media session and its execution state. The customer product remains authoritative for users, roles, entitlement and business identity.
Can Orchestrate work with more than one provider?
Yes, provider-neutral orchestration is part of the cRUD Morph boundary. Approved provider scope and ownership are confirmed during the technical engagement.
Does cRUD Morph copy the customer product's users and roles?
No. The customer product owns its users and business roles. cRUD Morph receives approved capability and opaque participant references needed for media execution.

About this whitepaper. It explains the public product and operating principles of cRUD Morph. It does not disclose source code, private implementation, provider credentials or customer data.

Put your media architecture questions in writing.

Tell us what your product delivers and which media responsibility you want to evaluate.