Atelier-Salon

A framework for portfolios that want to show both the finished work and the workbench it came from, without collapsing the two into one view.

The two layers

Atelier. The operator workbench. Atomic ideas, sources, notes, the cognitive metadata behind every artifact. This is where the raw material lives: clippings, half-formed thoughts, links between projects, the scaffolding that made the finished room possible. A small library, addressable and searchable.

Salon. The finished room the visitor walks into. Role-aware, hospitable, quiet. No scaffolding on the walls. The visitor sees only what has been prepared for them, tailored to why they came.

Kernel Pass. The pipeline that turns raw input into atomic units shared across both layers. One capture, two renderings. The Atelier shows the unit with all its context. The Salon shows the unit composed into a room.

Why it matters

Standard portfolios pick one mode or the other. Case studies get buried in a CMS, or operator notes stay hidden in Notion. Neither visitor gets the full picture: hiring managers see only the finished copy, and the people who care about how the sausage is made cannot see the workbench.

Atelier-Salon refuses the binary. The finished room stays clean because the workbench exists somewhere else, linked and visible on request. The workbench stays useful because it does not have to perform for a visitor. Both layers are first-class.

What the visitor sees

In the Salon, a case study renders as a hospitality-first role router. The visitor picks the angle they care about, recruiter, investor, engineer, human, or other, and gets a view cut to that need. Nothing else. No path crumbs, no debug chrome, no internal links. The room is finished.

Behind the wall, in the Atelier, the same case decomposes into atomic units: the problem statement, the capability map, the build contract, the competitive analysis, the system prompts. Each atom is addressable on its own URL. Each atom carries its sources, its dependencies, and the trail of decisions that produced it.

What the operator sees

The same atoms, arranged for search and recombination. When a new case starts, the operator does not begin from scratch: they query the Atelier for atoms that apply, recompose them, and ship a new Salon room on the other side. Atoms accumulate. Rooms get faster to build.

Applications

Silent Witness. The first test case. The Salon room is the case study with its role router. The Atelier exposes the eight atoms behind it: the deployment-lock insight, the seven-filter framework, the killer-assumption test, the capability matrix, the build contract, the competitive brief, the system prompts, and the artifact chain. A hiring manager can scan the Salon. A fellow PM can browse the Atelier. Nobody gets the wrong abstraction.

Studio principles. Each principle is an atom that gets composed into rooms. This page is one. Vectorless RAG is another. New principles slot in without rebuilding the site.

Tradeoffs

The pattern asks for discipline. If the Kernel Pass is sloppy, atoms drift out of sync with their Salon rendering, and the visitor notices the seams. If the Atelier is not genuinely useful on its own, it becomes dead inventory that nobody visits.

The test, always: can the atom stand alone with its sources, and can the room stand alone without them. If either fails, rework the pass.

Why I build it this way

Portfolios usually force one truth: here is the highlight reel, take it or leave it. I do not want to pretend the workbench does not exist. The decisions behind each case are as much of the work as the case itself, and hiding them shortchanges the people who want to understand the method. Atelier-Salon lets both truths coexist. The room is finished. The workbench is open. You pick which door.