2026 — 04
K.01
/knowledge
The thinking behind the systems.
A small library of articles and operating frameworks. Not a content marketing engine — a record of the ideas we actually work from. Read what's useful; ignore what isn't yet.
A studio's knowledge base is its second product. The first is the work; the second is the language used to describe how the work is done.
.02 / Categories
Four lines of inquiry.
Each category is a question we keep returning to. Articles are filed under the question they help answer.
-
K.01
What does it mean to design a system, not a product?
Articles on structural design, separating model from surface, and the discipline of editorial governance inside a design system.
-
K.02
How does AI act inside an operating workflow?
Frameworks for placing AI in real work — guardrails, evaluation, hand-off points — and field notes from the workflows we operate ourselves.
-
K.03
What is a brief actually for?
Brief diagnosis, scope structuring, the questions a senior would ask before saying yes — including the frameworks we use in our own engagements.
-
K.04
How does an organization remember?
Knowledge architecture, taxonomies, retrieval, the editorial discipline that keeps internal documentation useful at month six.
.03 / Articles
Recent.
2026 — 03
K.02
AI without an evaluation harness is not an AI workflow. It is a guess.
2026 — 02
K.03
The brief is not the brief. Five questions before saying yes.
2026 — 01
K.04
An onboarding doc nobody reads is a memory the organization is losing.
2025 — 12
K.01
Three layers of naming: primitive, semantic, component.
2025 — 11
K.02
An AI co-operator earns its place by passing the same review a junior does.
.06 / Invitation