From event to post, in four steps
A short walk through what actually happens between something occurring in your data and a video appearing on your channel.
The whole system is four steps, and it is worth understanding, because every feature is one of those four done better.
1. Something happens
An event arrives. It comes from a feed we carry, from your own systems over the API, or from a post you wrote by hand in a post list. It is data, not a video brief: a price, a result, a name, a date.
2. It is matched to a composition
A channel is subscribed to a source, and that subscription pins an exact template version. Not latest, an exact version, because a clip published last quarter should still be explicable. The event’s fields are validated against that template’s declared keys before anything is rendered, so an over-long headline is a refusal naming the field rather than a clipped line on a published video.
3. It is rendered, wearing your brand
The composition receives exactly three things: your brand, the channel, and the content. Nothing else. A template cannot know which customer it is rendering for, which is deliberate: a template that could would eventually be written to behave differently for one of them.
Every aspect ratio and every language the channel publishes in comes out of that one composition.
4. It goes out
To the channels you connected, at the time you chose, after a person has cleared it if you asked for that. The delivery is recorded, and the clip stays explicable afterwards: which template version, which brand version, which event.
Four steps. Everything else we do is one of those four, made harder to get wrong.
