---
title: "Creative-Ops Pipeline — Flagship case study | Harshith Nayaka L"
description: "Multi-model content pipeline turning a one-line brief into validated, on-brand output through tiered routing, schema-constrained generation and QA gates."
canonical: "https://harshith-nayaka-l-portfolio.vercel.app/work/creative-ops-pipeline"
last-updated: "2026-08-22T04:29:48Z"
author: "Harshith Nayaka L"
content-type: "text/markdown"
html-version: "https://harshith-nayaka-l-portfolio.vercel.app/work/creative-ops-pipeline"
---
# Creative-Ops Pipeline — Flagship case study

> A multi-model content pipeline that turns a one-line brief into validated, on-brand output, without a human babysitting every step.

Case study by Harshith Nayaka L, AI Engineer (Full-Stack), Bengaluru, India.
Canonical page: https://harshith-nayaka-l-portfolio.vercel.app/work/creative-ops-pipeline

- **Type:** Production AI pipeline
- **Focus:** Reliability & cost engineering
- **Pattern:** Multi-model + QA gates

## The problem

Producing on-brand content at volume is mostly invisible manual labour: drafting, reformatting, checking it didn't drift off-brand, fixing the one field that came back malformed, doing it again tomorrow. It scales linearly with headcount, which is to say it doesn't scale.

The interesting problem isn't 'can an LLM write this'. It's 'can a system produce this reliably, at a sane cost, and fail safely when a model misbehaves'.

## What I built

A pipeline that takes a structured brief and runs it through tiered models, schema-constrained generation, and explicit quality gates before anything is considered done. Cheap models do the bulk work; expensive models are spent only where judgment is actually needed.

Every stage assumes the model can be wrong. Output is validated against a schema, checked by a QA gate, and when something fails the run is logged with enough context to recover, not silently dropped.

This is a clean rebuild around public APIs that demonstrates the architecture and the engineering judgment behind it, with generic demo content in place of any real campaign data.

## Pipeline

- **Intake:** Structured brief (What, for whom, constraints)
- **Route:** Draft (low-cost model) (Bulk generation) → Refine (high-capability model) (Only where it pays off)
- **Structure:** Schema-constrained output (Generate then validate)
- **Gate:** Rule checks (Format, fields, limits) → LLM critique gate (On-brand? On-spec?)
- **Resolve:** Error log that still saves (Recover, don't drop) → Approved output (Ready downstream)

## The judgment calls

**Cost-tiered models, spent on purpose**

Not every token needs a frontier model. The bulk of generation runs on a cheaper model; the expensive one is reserved for the steps where its judgment changes the outcome. The result is the same quality bar at a fraction of the bill.

**Generate, then validate, then trust**

Structured output is requested against a schema, but the schema request is treated as a hope, not a guarantee. Every output is validated before the pipeline acts on it. Malformed responses are caught at the boundary, not three steps later.

**QA gates as code, not vibes**

Quality is checked explicitly: deterministic rule checks for the things rules can catch, and an LLM critique pass for the judgment calls ('is this actually on-brand'). Nothing passes on optimism.

**Failures save their work**

When a run breaks, it isn't thrown away. It's logged with enough context to resume or retry the failing step, so a single bad model response never costs the whole job.

## What it changed

**What it demonstrates:** Judgment about where to spend compute, how to make LLM output trustworthy enough to build on, and how to fail without losing work.

**Honesty note:** This is a clean rebuild on public APIs with generic demo content. No client data, no proprietary logic. The skill is the point, not the source material.

## Built with

LLM orchestration, Tiered model routing, Schema-constrained output, Validation layer, QA gates, Structured logging