Opening a workspace lands you here. It answers one question - what is in here, and where do I start - which is the question a newcomer, a returning colleague, and you-on-a-Monday all have.
It is not a feed. The timeline is still there, at its own page, and still the right surface for "what has happened lately". But a timeline is publish-centric by design: it deliberately excludes memories. On a workspace where most of the value is memory, that meant the front door showed a few percent of the content and gave no sense of the shape of the rest.
Three panels
Projects, largest first. Every project in the workspace with a count of its memories and its collections, biggest at the top, plus the workspace totals. This is the map: it tells you the corpus is 400 notes across six projects and that two of them hold most of it, which is the thing you cannot learn from any number of individual pages. Empty projects are left out - on an orientation surface they are noise.
Recent activity, both kinds. The last few things produced in the workspace, memories and collections together, each labelled with which it is, when, and which instance produced it. This is the Artifacts list's blind spot filled in: a workspace where the team is mostly writing memory looks dead on Artifacts and busy here, and the second reading is the true one.
Most-referenced notes. The memories the rest of the graph leans on most, by inbound [[wikilink]] count. It is a decent proxy for "what does this team actually run on", and the best entry point into the link graph for someone new. Only notes you can open are counted, so a private memory never shows up as a hub to someone who cannot read it.
Using it well
- Point a new joiner at it, not at Artifacts. Projects tell them where the work lives; most-referenced tells them what to read first.
- Watch the project counts for sprawl. A long tail of projects with two notes each usually means instances are inventing tags rather than reusing them, which the workspace guide is the fix for.
- A memory-heavy workspace is normal. Most teams end up with far more memories than published collections, because most of what you learn is not a deliverable.