01
What it is
When a global brand enters a new market, a literal translation of the film usually fails: the joke does not land, the holiday is wrong, the gesture means something else. Transcreation is reimagining the campaign in the local cultural code while keeping its strategic core — work normally done by an expensive team of local creatives.
Cultural Attaché decomposes that work into eight stages with ten formal contracts between modules.
The key architectural decision: deterministic hard-fail checks run before generation, not after. If a campaign collides with the local calendar or a taboo, the system stops without spending a single token on creative.
02
capabilities
What it does
01
Eight pipeline stages
Intake → intermediate representation → brief → decision → storyboard → executors → verification → pack. Every transition is a formal contract.
02
Contracts instead of conventions
Ten JSON Schemas, draft 2020-12. A module cannot hand its neighbour something unexpected — that is caught at the boundary, not in production.
03
Hard-fail before generation
Calendar, taboo and market-restriction checks run first. A campaign that fails the gate never reaches the expensive stage.
04
Human gates
A cost gate and other approval points: the system stops and waits for a human decision instead of proceeding “just in case”.
05
Market taxonomies
Seven levels of YAML reference data with their own validation — cultural codes, holidays and sensitive topics modelled as data, not prompt text.
06
Decision log
Every run leaves contract artefacts and log entries. A month later you can still answer why the campaign looks the way it does.
03
architecture
How it works
01
Master campaign in
02
Brief and decision
03
Storyboard and executors
04
Verification and gates
05
Market-ready pack
Under the hood
- The architectural canon lives in one document; all pipeline statuses live in one module, with no duplicated string constants.
- SQLite in WAL mode as the queue — a deliberate call: one moving part, no external broker at this scale.
- FastAPI with token auth and a WebSocket status stream; React + Tailwind in the dashboard.
- A cold audit in a single command: contracts, taxonomies, self-test, secret scanning against git.
- Fixture demo runs — one successful, one deliberately failing — so the gate can be seen working.
- Run artefacts are versioned alongside the code.
04
scale
Numbers
8
pipeline stages
10
formal contracts
7
taxonomy levels
0
tokens spent on a gated-out campaign