Workspace Graph

Most repository tools build a code graph:

That is useful, but it is not enough for Workspace Intelligence.

The product direction is a graph of the software system:

Graph layers

The layers below are a target model, not a claim that every edge type is already extracted by the current CLI. The current implementation has a project-level dependency graph used by model, impact, verify, graph, and watch. Deeper code, ownership, runtime, intent, and agent-history edges remain progressive product work unless a synced contract marks them available.

Structural graph

Shows how the workspace is organized:

Dependency graph

Shows what depends on what:

Ownership graph

Shows who is responsible:

Runtime graph

Shows how the system behaves when running:

Change graph

Shows what a diff means:

Evidence graph

Shows how trust is produced:

Agent graph

Shows which AI-facing surfaces have been grounded:

Current commands

npx workspai workspace graph mermaid
npx workspai workspace graph dot
npx workspai workspace impact --from .workspai/reports/workspace-model-diff-last-run.json --json
npx workspai workspace verify --strict --json

Today these commands inspect project dependencies, transitive impact, graph integrity, freshness, and verification evidence. They do not yet constitute a complete code-symbol graph or a complete organizational ownership graph.

Product direction

The goal is not to compete on a better repository graph alone. The goal is a living workspace model where graph edges are explainable and evidence-backed.