Summary and the knowledge graph

Summary is the surface that answers "what is actually in this workspace, and what has it been doing". It is the one place in Studio that looks at the whole thing rather than at the work in front of you.

What it shows

Two independent column stacks, so every card is the size of its own content rather than stretched to match a neighbour:

• Context injection over the period, and what it consisted of: how many rules were surfaced, how many memories, how many risky actions were stopped before they ran.
• The knowledge base, counted by kind, with what changed this month.
• Activity over time, with its peak marked, because the shape of a month is the thing a number cannot say.
• A domain and action matrix, so you can see where the work happened rather than only how much of it there was.
• Contributors, and what each person has taught the workspace.

There is no readiness score and no health gauge. A single invented number that grades your workspace is a number nobody can act on.

The knowledge graph

The graph is the workspace as a shape: every memory, rule and skill as a node, and the links between them as edges. Paths pull their own knowledge together, and an item that a dozen unrelated things depend on looks different from one that stands alone, because it is drawn differently.

It is the fastest way to see two things that a list cannot show you:

• Where the knowledge is dense, which is usually where the product is complicated.
• What is isolated, which is usually something that was written once and never connected to the work it was about.

Selecting a node previews it in place, so you can move through the graph without leaving it, and filters narrow the graph by kind of link rather than hiding nodes at random.

The renderer is built once and paused when you leave the tab, so opening the graph does not cost you anything for the rest of the session.