The operating system itself: stations by type of work, not by project

The situation

Every system in this room runs on top of AI sessions doing the actual work, and at some point the way those sessions were organized became a system of its own, worth designing on purpose instead of letting it accrete. The original approach was one long-running session per project. That fails quietly: a project pin goes dead the moment the project pauses, while the type of work behind it (research, building, anything carrying a partner's name, anything involving numbers) never goes stale, because there is always more of it.

So the firm redesigned around stations by type of work rather than by project. A station holds its configuration (which tool tier it runs, how much it is allowed to think, what it can touch) permanently; the conversation inside it does not need to survive and is not meant to, because the actual work product lives on disk, not in the transcript. Alongside that, the firm measured what a session actually costs before a single word of new work gets typed, and built a review chain that any unattended, scheduled change has to clear before it ships.