From One Deal Link to Three Channels: Anatomy of an Agentic Distribution Pipeline

5 days ago
4 min read

Input: a link to a commercial offer. Output: publications ready for three social channels, each in the channel's native language. Here is the anatomy of a pipeline we run in production — and why the interesting part isn't the generation.

When we show this pipeline, everyone looks at the model that writes. The value is elsewhere: in the division of roles between deterministic code, model and human, in the compliance gate, and in the metrics that decide what lives or dies.

Key takeaways

The division of roles is strict: deterministic code extracts the facts, the model writes the tone, the human publishes. Never the other way around.
A channel is not an export format, it's a native language: title constraints, tag counts, image ratios, cultural codes — encoded per channel.
The north star is not publication volume, it's the number of new users brought to the platform. That metric choice has killed more features than any committee.

The division rule: deterministic extracts, model writes

First structuring decision: the model extracts no facts. Price, discount, validity dates, images, merchant name — all of it comes from a Python extractor, deterministic, testable, that fails loudly when a page changes. The model only sees already-extracted fields, and writes from them, never from its memory.

The reason is simple: an awkward phrase can be fixed; an invented price destroys trust. On commercial content, the factual error is the only fatal error — so it's assigned to the layer that cannot hallucinate. The model, in turn, does what it does better than code: the right tone for each channel.

One channel, one native language

The classic multichannel trap: write once, export everywhere. The result smells like translation, and every platform punishes it. Our three channels have three grammars: different title lengths, different tag counts, different image ratios, and above all different writing codes — what hooks on a visual recommendation network has nothing to do with what works in a group conversation.

So each channel has its own encoded formula: the pipeline doesn't translate one post, it writes three native posts from the same extracted facts. It costs more in generation, and is incomparably more effective in distribution.

The compliance gate: a door, not a prayer

Social platforms have rules — regulated commercial phrasing, forbidden claims, required mentions — and breaking them costs the account's visibility, sometimes the account. Our answer is not a line in the prompt ("be careful"); it's a gate: a compliance lexicon, maintained like code and versioned, that rewrites or blocks risky phrasing before any human review. By default, the generated hook is the conservative variant; more aggressive variants exist, but they require an explicit human decision.

It's the same principle as everywhere else in our systems: what must be reliable is not asked of the model, it is enforced by a gate.

Publishing stays a human gesture

The pipeline stops dead before publication. Deliberately. Publishing under a brand is irreversible and engages the account; platform terms of service constrain automation; and the publishing calendar is an operations decision, not a generation one. The operator receives a complete package — visuals, copy, tags, variants — and decides what goes out, when, on which account. The machine prepares everything; it doesn't press the button.

An assumed corollary: we grow a small number of official accounts rather than an army of anonymous ones. An audience's trust accumulates on a stable identity — it's slower, and it's the only asset that survives algorithm changes.

The metrics that decide

A distribution pipeline can produce flattering numbers at will: posts per day, impressions, likes. We steer by none of them. The north star is single: new users brought to the platform. That choice has a practical consequence: any feature that raises volume without moving the north star is dropped, however seductive. Generated video avatars are the example: tested, judged negative on return versus risk, not deployed — the interface is reserved in the architecture, and it will wait until the equation changes.

A pipeline is judged by what it refuses to automate as much as by what it automates.

FAQ

Why not automate all the way to publication? Because publishing is irreversible, engages the brand, and end-to-end automation is constrained by the platforms. The marginal gain covers neither the compliance risk nor the loss of editorial control.

One model for all channels? Yes — same model, different formulas. Differentiation comes from the per-channel formula and the extracted facts, not from the model choice.

How do you measure real effect? Through attribution to the platform: tracked links per channel, and one north star — new users. Publication volume is a cost, not a result.

ECTIME AI Lab is the applied-AI research and deployment unit of ECTIME Group. We build, ship and stress-test agentic systems in production, from GEO/SEO automation to multi-step autonomous agents. We maintain open-source Claude Skills for GEO/SEO and advise European brands on deploying AI that is not just autonomous, but verifiable and authorized.