Every other practice in the catalogue inherits design from .Studio. Typography, palette, the 4×6 print envelope, the labeling system, the format conventions that make a CELL legible and a CODEX recognizable. .Studio doesn't make food, doesn't build shelves, doesn't write essays — it operates the substrate that everything else builds on. Sister practice to KEEP. New as of catalogue v0.7.
The studio has been operating with a coherent design system for months. Typography (Space Grotesk + Inter + EB Garamond + IBM Plex Mono). A locked palette (paper, ink, hanko, per-practice accents). The 1646 cell envelope. The CODEX format spec. The label slot on every cell. All of this has been distributed across practices without an explicit owner.
Each practice has been using the design system; no practice has owned maintaining it. This worked when the system was small enough to live in everyone's head. It is no longer that small. The catalogue now has 9 practices, 4 sub-lines, the CODEX format, the booklet format, the labeling spec, and a typography stack that touches every page.
.Studio is the practice that owns the system as a system. Not the practice that uses it (every practice does). Not the practice that ships its products (every practice does). The practice that defines, maintains, evolves, and documents the substrate.
.Studio's first formal design standard is the 4×6 print envelope — the universal dimension that every printed surface in the catalogue conforms to. One envelope serves the entire catalogue. One paper stock (Oxford 4×6 ruled/blank, Made in Mexico, sourced through the standard office-supply channel) supplies it.
Every page in the catalogue uses these four typefaces in disciplined combinations. Display for hierarchy, serif for body web, classical for editorial book-typography, mono for technical and labels.
Three foundation colors carry every page (paper, ink, hanko). Nine per-practice accents distinguish the practices. .Studio's own accent is the dark olive-green seen in this page's eyebrows — chosen to read as system/foundation rather than any content domain.
.Studio's customers are the studio's other practices. Each one inherits typography, palette, and format conventions from the substrate. Practices can override (CODEX uses EB Garamond at editorial scale where most practices use Inter at web scale) but the substrate is constant.
.Studio's first product line under the 4×6 envelope is the folded-card booklet — a transformation of existing 4×6 cards into Field Notes-style pocket notebooks. A 100-pack of cards becomes 2 standard booklets (50 pages each) OR 4 mini notebooks (25 pages each). Same cards; new use.
The format opens a content surface that didn't previously exist in the catalogue: studio editorial work that's too long for a single card and too short for a CODEX. The 5,000-word manual range — the KEEP 1646 Mods Manual, the BXBX Hako Owner's Manual, the Studio Almanac. All of these become real physical products instead of just web pages.
The hardest unresolved question in the studio's catalogue: how does a customer who's filled 20-30 cells in a Wowlive shelf find any specific thing again? The current answer is "label the cell." That works at small scale and breaks at any scale beyond ~20 cells, and breaks completely for cells the customer fills without explicit itemization.
.Studio's working architectural answer: the cell remembers itself, the customer doesn't have to. Three layered approaches under one architecture.
Every 1646 cell ships with a pre-printed QR sticker on the label slot, encoding a unique cell ID. The customer doesn't print this; .Studio does. Cell IDs are sequential per-customer but globally unique. The sticker is the customer's permanent handle on that physical cell.
Each customer has a personal account at keep.m1nd.co/me (working URL spec). The app holds a record for each cell, keyed by QR ID. The customer chooses how much effort to put in at filling time:
Customer searches their KEEP library by what they remember about content, when they put it away, where on the shelf it lives, photos they took, voice memos they recorded.
The key insight: tiny cost at filling time → large benefit at retrieval time. Most labeling systems get this backwards — they require effort up front and offer marginal benefit later. The studio's pattern asks for ~5 seconds of effort per cell and returns full-library search later. The pattern degrades gracefully — a customer who scans nothing still has cells with unique IDs.
CELL-001-AB47 or similar. Customer can write the ID in a paper register or notes app. When the web app launches, the IDs already exist on the customer's cells and migrate cleanly.
Working name: KEEP Cards — the personal KEEP web app that tracks the customer's cells. Each cell ID is a "card" in the database (the term doubles back to the studio's card-and-cell language).
.Studio's product line begins with the booklet format. The labeling system, the cell-comparison essay, and the eventual KEEP Cards web app follow.
KEEP and .Studio are the studio's two infrastructure practices. The split: KEEP owns the physical envelope (the 1646 cell as an object, the Wowlive shelf as an object, the mod kit as physical accessory). .Studio owns the design system that the envelope inhabits (typography, palette, label format, the visual register that makes a labeled cell legible).
The two practices complete each other. KEEP without .Studio = unlabeled boxes on shelves. .Studio without KEEP = a beautiful design system with nothing to design for. Together, they form the substrate everything else in the catalogue inherits from.
A naming convention worth establishing: infrastructure practices use full uppercase (KEEP); design practice uses leading-dot notation (.Studio). This subtle typographic signal communicates that .Studio operates at a different layer — meta to the other practices rather than peer with them — while still being a real practice with its own surface area and products.