A software product that delivers live and recorded media carries two different kinds of responsibility. It decides who may take part, what the experience looks like and what happens afterwards. It also has to move audio, video, slides and recordings reliably. When those responsibilities blur, each becomes harder to change and harder to trust. This article explains why the line matters and how cRUD Morph draws it.
TL;DR
- Product authority and media execution are different jobs, and each should have its own owner.
- In cRUD Morph, every fact has exactly one authoritative owner, either the customer product or cRUD Morph.
- The product keeps its users, roles, plans, registration, interactions and commercial relationship. cRUD Morph keeps media sessions, Program Output, recording lineage and delivery state.
- Carrying a message across the boundary never transfers ownership of it.
Two jobs that are easy to confuse
Consider a live session inside a learning, events or communications product. Before anyone joins, the product has already decided who is registered, who may speak, which plan the customer is on and what the session is called. During the session, a different layer decides which tracks are published, how quality responds to the network, how the output is composed and where it is recorded.
The first group of decisions belongs to the product. They express the customer’s business, its users and its promises to them. The second group is media execution. It has to be precise and governed, but it should not need to understand the product’s business vocabulary to do its job.
One owner for every fact
cRUD Morph starts from a simple rule. Every fact has exactly one authoritative owner, either the customer product or cRUD Morph. Duplicate truth is where systems quietly disagree. If a media layer keeps its own copy of a session’s schedule, its attendee list or a customer’s plan, sooner or later the copy and the original diverge, and nobody can say which one is right.
cRUD Morph therefore keeps no second source of truth for webinars, attendees or users, plans and entitlements, and business roles. The rule applies to every customer, so the core of cRUD Morph never interprets one customer’s plan names or role names.
Its organisation or workspace, users and profiles, business roles, plans and entitlements, registration, admission decisions, scheduling, customer-facing policy, chat, polls, Q&A and reactions, and its commercial relationship with its own customers.
Its tenant and environment identity, media sessions and rooms, participant media presence, versions of media policy, presentation state when the product delegates it, Program Output, recording lineage, normalised delivery state and immutable usage facts.
How the boundary is crossed
The two sides still need to work together. In cRUD Morph, they meet through mappings rather than copies. A mapping records that an engine resource corresponds to a customer reference. It does not record the customer entity’s name, status, schedule, roles or plan as engine truth.
Commands travel in one direction and outcomes in the other. A customer adapter translates the product’s identities, roles and entitlements into capabilities the engine can understand. It then sends signed commands limited to the approved capabilities. cRUD Morph answers with normalised events and usage facts, and the product decides what those events mean for its own users.
- Customer references are mapped, never copied.
- Roles and entitlements arrive as capabilities, not as product vocabulary.
- Outcomes return as events the product can interpret.
- Usage facts are immutable and never become a second record of the product’s business.
Transport is not ownership
Some product features sit close to the media without being media. Chat, polls, Q&A, reactions and registration remain the product’s business. Where a media layer carries timing references or envelopes for them, it does so as transport only. Moving a message from one place to another does not make the carrier its owner.
The same reasoning runs the other way. A control decision is never inferred from the existence of media alone. The fact that a video track is flowing does not prove that a participant was admitted, and a missing receipt does not prove that a job failed. Each answer comes from the side that owns it.
What the boundary protects
A clear boundary protects the product’s identity. Its brand, interface, users and engagement features remain its own, and its commercial model stays its own decision. The cRUD Morph approach sets out the same boundary from the product side.
It also protects the media layer. Because the core never depends on one customer’s business vocabulary, the same contracts can serve different products, and behaviour tied to a particular provider can stay behind adapters instead of leaking into product logic. Partial failures stay contained as well. A problem in one plane must not silently overwrite authority in another.
Questions to ask of any media layer
- Which facts does the media layer keep as its own truth, and which does it only reference?
- Does it ever store a copy of your users, roles, plans or schedules?
- How do your product’s permissions reach it, and can it act beyond them?
- Where do outcomes come from, and how does your product learn about them?
- What happens to authority when one part of the system fails?
A responsibility model for the boundary
A useful boundary does more than divide two systems. It tells each team what it owns, which decisions may cross the line and what evidence must return. The customer product should remain the authority for users, roles, commercial rules, experience and interaction content. cRUD Morph should remain responsible for the approved media work it accepts.
User identity, participant roles, product permissions, commercial policy, the interface and the decision to begin or change a media session.
Media-session execution, provider coordination, representation, routing, Program Output, recording state and normalised operational evidence.
Authorised commands move in. Stable identifiers, accepted state, outcomes, receipts and errors return.
Provider dashboards, internal credentials, hidden implementation detail or authority over the customer's users and product decisions.
When a provider fails
The customer product should not have to learn a provider's private error model before it can respond. cRUD Morph interprets the provider outcome, preserves what is known and returns a stable state that the product can explain. A retry or alternate route remains governed by the authorised policy. The product keeps control of the customer experience while the media layer handles the operational response.
When a provider changes
A provider change should alter the implementation behind the boundary, not the customer product's meaning. Session identities, roles, commands and returned evidence remain consistent. The new provider must pass the required connection and conformance checks before it carries approved work. This is how portability becomes an operating property rather than a promise made during procurement.
Summary
Media delivery works best beneath a clear product boundary. The product keeps authority over its users, roles, plans, interactions and experience. cRUD Morph owns media sessions, outputs and delivery state, with exactly one owner for every fact and mappings rather than copies between them.
About this article. It explains how cRUD Morph works. It makes no performance, quality, availability or cost claim. Those results are measured for each engagement against a matched baseline.