How we build — full system

A five-role studio system, not a job title.

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.

通译
章法
The five roles

Signal in. Truth curated. Product out.

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.

External · The Scout · 探

Finds the signal

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.

Internal · The Archivist · 藏

Owns the truth

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 · 论语

Delivery · The Builder · 造

Ships it

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.

Orchestration · The Conductor · 理

Routes and gates

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.

Infrastructure · The Operator · 守

Keeps it safe to move fast

Least-privilege IAM, key rotation, budget alerts, deploys. Keeps the other four roles safe to move fast without babysitting infrastructure themselves.

The tooling

Built on ordinary infrastructure, used deliberately.

No proprietary platform underneath — the differentiator is the role discipline above, not exotic tooling. What we actually run on:

Claude Code

The five roles run as Claude Code / Claude agent sessions, coordinated through the ticket-bus files themselves.

GitHub

Source of truth for every repo; the ticket bus itself lives in-repo, versioned alongside the code it describes.

AWS

OCR / Bedrock, IAM, and the Operator's home turf — least-privilege by default, budget-alerted.

Vercel

Production hosting for Chow Down — fast iteration, one command to promote.

Cloudflare

Pages hosting + Access for the studio site and gated family properties.

Neon

Serverless Postgres — the Archivist's dictionary asset is promoted here for production reads.

Case studies

The system, in production.

Chow Down's review system

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.

Approve Tentative Needs-edit Reject Reassign

Reviewer roles built into the dictionary schema: founder · mandarin · cantonese — Cantonese-family dishes route automatically to the Cantonese reviewer.

The family pipeline

A heavily customized speech-recognition pipeline and purpose-built review dashboard, tuned for bilingual, code-switched family conversation.

Review dashboard — demo data
Demo data shown — invented dialogue, no real family content.