Docs · Docs

Architecture

How Closure fits together. For why the product is a graph, read The Product Graph.

Closure
      │
 ┌────┴────┐
 Workflow   Experience (UI)
 Graph         │
      │        │
 Runtime       Renderer
      │        │
 Forms · Chat · Agents
      │
 Connectors → ServiceNow | HubSpot | Form.io | Salesforce | …
      │
 Events → audit · Activity · evolution

Piece	Role
Runtime	Executes workflows — state, durable runs, policy gates
Product data API	GraphQL over org objects (Knowledge → Data)
Knowledge	Skills + files ground AI agents; live data via GraphQL; Tools (`schema:tool` packs) for allowlists — Tools
Events	Organizational memory across the four pillars
IDE MCP	Your IDE authors the same graph on SaaS — Build in your IDE

Boundaries

Connectors are the system-of-record bus; MCP is for IDE authorship
Experiences are graph objects — Closure is the product UI source of truth
Evolution is versioned — drafts you approve