Two builds took the heat at SGInnovate: a parallel AI content pipeline and an evaluation harness for AI agents. This recap preserves the practical decisions, trade-offs, and questions raised in the room.
Speaker 01
AI Content Pipeline
Brought a content pipeline that fans one piece of source material out into a podcast, blog, images, and audio in parallel. The conversation concentrated on orchestrating parallel generation, engineering error handling so effort is never discarded, and choosing image models when text-in-image matters.
When you run a parallel workflow — one source, multiple outputs at once — always plan for orchestration and piecing things together up front. The fan-out is the easy part; reassembling coherent pieces from independent branches is where the complexity lives.
If a branch fails, plan the workflow to continue first and go back to retry afterwards. Do not discard the previous effort — partial success is still worth keeping. Fail-continue beats fail-fast when each branch is expensive to produce.
Imagen is cheaper for image generation than GPT Image, but it does not support rendering text inside the image. If you need legible text baked into the asset, GPT Image remains affordable — or render and superimpose text over the image afterwards to save cost.
For finer control over image aesthetics, explore ComfyUI for image improvement pipelines. For programmatic video, consider Remotion.
Start light with Grafana for monitoring; move to Prometheus when the load warrants the heavier machinery.
Speaker 02
Evals and guardrails can overlap, but they are not the same job. A guardrail can be implemented as deterministic code — it doesn't need to be another model.
Two ways to keep a misbehaving agent from doing damage:
PIC: An Ting
Event ops volunteers