Every product in our catalog runs through the same internal pipeline. It began as a file-based ticket system for a two-person team and stayed that way on purpose — precision over ceremony. Below is the whole thing: the five roles, the tooling underneath, and two live case studies.
Each role is a single character — its seal. One finds the signal, one owns the truth, one ships it; two more coordinate and protect the work.
Gathers and structures outside signal — market data, competitor pricing, raw bilingual language pairs pulled from the open web (menus, listings, public corpora). Dedupes to a common schema, then surfaces the highest-frequency gaps for the Archivist to weigh in on. Explicitly out of scope: authoring final entries — the Scout finds, never decides.
Owns and curates the studio's actual intellectual property — the canonical translation dictionary, the naming standards, the review taxonomy. Every entry carries a reviewer role and a sign-off gate. This is the one role whose day-to-day output is the defensible asset the rest of the system exists to protect and extend.
名不正,则言不顺 — ANALECTS 13.3 · 论语
Implements the code — matchers, pipelines, APIs — and ships what the Scout and Archivist feed it. Promotes new dictionary and config versions to production, then verifies against real traffic before handing back to the Conductor for close-out.
Routes tickets between the other roles, sequences handoffs, and runs a fixed weekly cadence — Plan → Gather → Vet → Ship → Verify. Every ship is gated on founder approval. Nothing reaches production without passing back through this role.
Least-privilege IAM, key rotation, budget alerts, deploys. Keeps the other four roles safe to move fast without babysitting infrastructure themselves.
No proprietary platform underneath — the differentiator is the role discipline above, not exotic tooling. What we actually run on:
The five roles run as Claude Code / Claude agent sessions, coordinated through the ticket-bus files themselves.
Source of truth for every repo; the ticket bus itself lives in-repo, versioned alongside the code it describes.
OCR / Bedrock, IAM, and the Operator's home turf — least-privilege by default, budget-alerted.
Production hosting for Chow Down — fast iteration, one command to promote.
Pages hosting + Access for the studio site and gated family properties.
Serverless Postgres — the Archivist's dictionary asset is promoted here for production reads.
Reviewers across Mandarin, Cantonese, and English sign off on translation quality through a shared, auditable workflow — role-based queue, full audit trail, JSON export. Built to support cross-dialect review as the team grows.
Reviewer roles built into the dictionary schema: founder · mandarin · cantonese — Cantonese-family dishes route automatically to the Cantonese reviewer.
A heavily customized speech-recognition pipeline and purpose-built review dashboard, tuned for bilingual, code-switched family conversation.