tradecraft

Architecture writeups for production systems I've built. One case study so far.

Live page

jstottlemyer.github.io/tradecraft

What's here

• index.html — standalone landing page. Mermaid diagrams via CDN, Fraunces + JetBrains Mono via Google Fonts, no build step. Reflects the live state of the Red Rabbit Production OS as of late April 2026.

What it documents

• A canonical-source-of-truth architecture for a creative production (TV/film franchise)
• Two write surfaces (Pages Router endpoint + App Router Server Action) terminating in one canon-core engine
• Two MCP transports (stdio + hosted) backed by one MCP server package
• The /spec → /spec-review → /plan → /check → /build → /code-review workflow used to ship features through a multi-agent pipeline

Why a writeup site

The architecture is genuinely portable — you could swap Red Rabbit canon for a SaaS knowledge graph, a game-design wiki, an organization's policy database, or any other domain that wants AI-mediated authoring with PR-level review gates. Documenting it this way makes it easier to reference, easier to teach from, and easier to extract patterns for future systems.

Stack used by the case-study system

• TypeScript pnpm monorepo
• Next.js 14 (App Router + Pages Router hybrid)
• Vercel hosting + Upstash KV
• Octokit + GitHub App for canon writes
• zod schemas with .describe() as humanization registry
• MCP (Model Context Protocol) for chat-tool surface
• Claude Code agent pipeline for the spec-to-ship workflow

— Justin Stottlemyer