Building the studio's own operating system
The first TwelveApart engagement was TwelveApart — a monorepo, a corpus, and a site that renders it.
Problem
The studio had a venture brief and a design system, but both were internal files. They could not show anyone outside the studio what the founders had built or learned.
Approach
One monorepo. The corpus lives at the repository root as typed Markdown rather than inside the web app, because the site is one consumer of it and the thesis graph and the agents are others. Every artifact declares an author and its relations to theses, so the graph is derived rather than maintained.
Result
A static site rendering ideas, experiments, case studies, and founder pages from the corpus, deployed through Vercel. ADRs record the design decisions; a provenance log records every borrowed design move.
What we learned
The key structural decisions concerned where content lives and what gets written down. Recording why a decision was made costs minutes at the time. Reconstructing that reasoning later takes longer and is less reliable.
This site is TwelveApart’s first internal product: a monorepo that turns the studio’s brief, design system, decisions, and published work into one public system. The work is ongoing; this record covers its first deployment.