An atlas is not a map. It's a bound set of plates of one world — the same territory drawn at different scales and for different questions — and what makes it an atlas rather than a pile of maps is the gazetteer: look a thing up, and it tells you where it sits on every plate.
Below is one week of one person's work, drawn four ways at once. Pick anyone from the gazetteer and watch them light up on all four plates simultaneously. That's the point — not that we can draw four pictures, but that there is one world underneath them.
And note who's on the team roster. Three people and three agents. In the AI world your team is a mixed roster, and it has been for a while.
Every teammate — human or agent — appears on all four plates, because the plates are projections of one substrate rather than four separate views someone had to keep in sync. Selecting one dims everything it doesn't touch.
“Who did I work with, and who did they hand to?” Humans and agents on the same ring, because at the level that matters — who held the session — they are the same kind of thing.
“What actually happened, and what came from what?” The Context Map grammar: Streams containing Sessions, joined by continues. This is the plate that already ships.
“When, and in what order?” The same sessions on a time axis, one lane per teammate. Makes the gaps legible — which is where work goes cold.
“What is allowed to touch what?” Three sealed enclosures. The readout counts edges that cross a boundary, and the count is zero — asserted in the data, not filtered at read time.
The session framing has one open weakness on the record: making the single-user session the centre risks under-selling the multi-person story, which is where the larger contracts are. The mixed roster dissolves that.
A solo consultant with Claude Code, Cursor and one client contact has a team of four. Three of them are software.
So the single-user case and the team case were never two products. Even alone, you are passing sessions between teammates — they just don't all have a payroll number.The handoff-vs-session argument stops needing a caveat. The handoff is the case where the next holder is someone else — and “someone else” now includes the agent you opened five minutes ago.
Why the same primitives serve a solo operator and a ten-person team without branching. A roster of one human and three agents and a roster of four humans produce the same graph.
Plate IV is doing quiet work. A mixed roster means agents are teammates that can be pointed at the wrong hat. Separation has to be structural, which is exactly why the cross-boundary count is on screen.
“Your team” holds. It's warm, it's ownership-shaped, it covers humans and agents in one word, and it says what you do with the thing. It fits the endorsement structure exactly: the org name carries the infrastructure, the face carries this.
“Session management” does not. To a developer audience that phrase already means something specific and completely different — OWASP publishes a Session Management Cheat Sheet, it's half of a Top-10 category (“Broken Authentication and Session Management”), and there's an ASVS chapter on it. It reads as cookies, tokens, and login state. And management is admin register — the opposite of the claim that the context is the valuable part. Same objection applies to “collaboration tools” from the other direction: that's a category positioning deliberately stays out of.