연구소: splitting dev out of 만들다 so 만들다 means shipping the actual product
만들다 used to mean 'coding' and opened the terminal. Split it into two Areas: 🔬연구소 (dev/coding/experiments → terminal) and 🔨만들다 (the real product — app store, releases). The 7-cluster map is now 8; dev-domain nodes (code, architecture, commits) route to 연구소.
The founder's call: "터미널은 별도 개발 팀으로 따로 빼자… 만들다는 실제 앱스토어 혹은 여러 가지 실제 업무를 처리해야지… Area가 개발관련으로 하나 추가다… 연구소라고 하거나."
Right. Conflating "make the product" with "write the code" muddied 만들다 — clicking it just dropped you into the terminal, so there was no place for the actual product work (store submissions, release planning).
The split
- 🔬 연구소 (new Area) — 개발·코딩·실험. This is what now opens the terminal.
- 🔨 만들다 (repurposed) — 제품·앱스토어·릴리스. Opens its normal Area page like every other business Area; no longer the terminal.
So the cluster map went from 7 to 8. The routing flipped in one line (StartupView): if (k === "lab") onWorkspace() instead of build. The node→cluster mapping moved the dev vocabulary —
code, architecture, and the change/structure node types — onto 연구소, while product,
release, appstore stay on 만들다. Dev setup checklist items (README, deploy path) moved to
연구소 too. Tests updated and green (5/5), tsc clean.
The point: the Areas are the founder's mental model of the business. "Where the code happens" and "where the product ships" are different jobs — now they're different doors.