← All work

Content operations · 2026

How do you keep a brand intact from hero to halo?

The hero asset gets everyone’s attention. The halo is the hundred adaptations behind it, made faster, by more people, with less room, and it is where brand quality quietly goes. Throughline turns the brand system, the approved claims and the business rules into something a production process can carry all the way down.

My role
Concept, system design, build
Method
Decisions made early, carried forward intact
Output
One governed message, adapted per channel and audience

Generating content faster does not fix this. It produces more of it, with the same gaps, at greater volume.

Efficiency comes from smarter decisions, not faster generation. So the decisions move to the front, and everything downstream inherits them.

Decide once, carry it down

One approved claim goes in, and it never moves alone. An assignment arrives in plain language and runs through eight stages grouped under three questions: what do we know, what are we making, how do we make it well. The part that matters is what travels between them.

Two sides of a claim record. The front shows the approved claim with a full and a short message version, its required headline, reference, expiry and target segments. The back shows the claim overview and its structured metadata as JSON-LD.
The durable claim. Approved once, and carrying everything an adaptation needs to inherit: a full and a short version, the reference it rests on, the date it expires, who it is for, and the same facts again as structured data so a machine can read them too.
An assembly canvas for a fictional demo brand: a brand system with its attached evidence and a three-message claim matrix feed a template recipe, which produces the same message as a leaderboard, a square and a half page, each labelled fictional brand, demo only.
Pulled through. One claim matrix fans into every size the plan calls for. The banners are assembled from the approved claim rather than rewritten from it, and each one carries its own disclosure. Note the header: distribution is blocked, because one piece of evidence is still unavailable.
A production gate screen. The source and reference chain runs down the left, each source labelled with the role it plays in review. On the right, six required checks report the qualifier missing and the channel fit failing, two passed and two still pending, and the proceed button is disabled.
Held at the gate. The banner cannot fit the qualifier the claim is required to carry, so it does not proceed. Caught at production, not flagged for someone downstream to catch later. This is the halo holding.

What it taught me

On what’s shown here. The engine was built for a live pharmaceutical program in a rare disease, so almost none of that work can be discussed. What is shown is a client- and agency-independent fork built for this purpose, with a fictional prescription brand called Aster in a public, source-backed context. Every strategy and product detail in it is synthetic and disclosed as such inside the frame. No client, product, molecule or performance figure appears above. The transferable part is the stage model and the claim object.

Built in vanilla JavaScript, no dependencies.

← All work

Talk to the site

Ask it what this page left out.

A voice assistant runs on every page here. It reads a handful of files I wrote by hand, it won’t pretend to be me, and there’s a written list of things it refuses to discuss. Client specifics are on that list.

Needs a microphone.