Diagrams as workspace data
Whiteboards with strokes tied to the work
A workspace record
Shares permissions, version history, search, and audit with the rest of the graph. Not a separate app you forget to invite people to.
Pinned to work
Every node, sticky, and edge can attach to an issue, project, doc, or NorthGraph effect. The diagram cannot drift from what's shipping.
Made for review
Threaded comments, request changes, resolve. Diagram reviews look like code reviews, and live in the same audit log.
What teams draw here
Four canvases that earn their place in the workspace
Permission map
Sketch how workspaces, teams, agents, and context bundles share access. Pin to the security review.
Roadmap board
Quarterly bets as cards. Each card linked to a project, when the project ships, the card knows.
System sketch
Services, queues, datastores, partners, annotated with NorthGraph effect classes so risk lives on the diagram.
Decision tree
Branch the options. Each leaf links to the ADR or doc that explains the choice, and links back from there.
Pinned to records
Every node sticky and edge can link to the thing it describes
Pins are bidirectional. The issue knows the canvas referenced it; the canvas highlights the node the issue closed against.
- Node
"Checkout service"→Project · Checkout v2 - Sticky
"Block on auth review"→Issue · ENG-2188 - Edge
"DB writes from /checkout"→NorthGraph effect · db_write
Reviewed in place
Comments pin to nodes edges and stickies instead of a sidebar thread
Relabeled the edge to read 'orders + audit'. Saved as v12.
Worker was split into stripe-worker and email-worker last week. Want me to break the node into two?
Get started
Bring your team onto the shared work graph
Create an account, name a workspace, invite your team, connect your code, and point your agents at MCP. Start turning company context into shipped work from one shared workspace.
This edge doesn't say the audit table we added last sprint also writes here. Label it?