VectorGraph

Docs

Docs keep decisions connected to work

Create workspace
∞versionsAuto-saved revisions with full history and diff view.
↔linkedIssues, projects, and canvases reference docs both ways.
0wikis to migrateDocs live alongside the work from day one.
1permission modelSame workspace and private-team rules as everything else.

What a workspace doc is

Four properties a wiki page cannot claim

  • Versioned

    Auto-saved revisions with full diff history. Every change shows the actor, the timestamp, and what landed.

  • Bidirectionally linked

    Cite an issue in a doc, and the issue shows the doc back. The reference graph maintains itself.

  • Permissioned

    Workspace, team, and private-team rules apply. A team's runbook stays inside the team, even from agents.

  • Reviewable

    Threaded comments inline, reviewer assignment, resolve state. Approvals attach to the version, not the URL.

Bidirectional links

Reference a doc and the doc references you back

Drop a doc link in an issue, project, sprint, or canvas and the doc's sidebar shows the reference. No "broken link" rot. No quarterly cleanup. The graph maintains itself.

Versioned by default

See exactly what changed when and by whom

Auto-saved revisions. Per-version diff. Restore any prior state without leaving the doc. Useful the next time a decision brief quietly drifts away from what was approved.

v17 → v18Maya Chen · 12m ago
 ## Acceptance - Every shipped change must trace back to a linked Signal.+ Every shipped change must trace back to a linked Signal or roadmap bet.+ Reviewers block on missing evidence.  ## Rollback+ If migration verification fails, revert the rollout flag and restore from the pre-deploy snapshot.

Made for review

Inline threads resolve state and approvals attached to the version

Comments live next to the line they're about. Resolving a thread doesn't delete it, it stays in the version history, so future readers can see what the conversation was.

  1. Maya Chen12mopen

    Call the rollback plan out explicitly under Acceptance, pilot teams keep missing it.

  2. David8mresolved

    Fair. Moving it above the migration checklist and adding a callout.

  3. Karri5mopen

    Also tag this doc on the Migration readiness project so it surfaces in the launch review.

Docs your agents already read

Specs an agent can fetch with the same permissions a person has

When an agent calls read_context_bundle for an issue, the doc linked to it comes back in the response, pre-filtered to what the agent's identity is allowed to see. No copy-paste. No specs that go stale because the agent never opened them.

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.

Create workspaceSign in