Experiences
Pages, components, themes, and binds compose a real product. Preview Dev / Test / Prod in the workbench — hostable Experiences rendered from the graph.
Experiences in depth →Platform
The pillars
Pages, components, themes, and binds compose a real product. Preview Dev / Test / Prod in the workbench — hostable Experiences rendered from the graph.
Experiences in depth →Executable process graphs with shared runtime and audit. Parallel forks, waits, compensation — plus an orchestration node that runs a supervised agent team (hosted or LangGraph) inside the same governed run.
Four citizens — Data, Skills, Files, and Tools — tuned for how models use context. Skills ground AI agents; files retrieve when documents matter; live graph data stays queryable; tool packs drive workflow allowlists.
Import, write, and trigger against systems you already run. When a journey completes, Closure seals — writes the governed result into your system of record.
Partners & ecosystem →Across every pillar
One org graph is the product source of truth — Experiences, Workflows, Knowledge, Integrations, and Events. Query and mutate through Platform APIs; Closure and partners share the same contracts.
Start in Cursor, Claude Code, or VS Code — Platform MCP gives your IDE a product model. The Closure console covers review, approvals, and visual editing. Forms, agents, and human review share one Workflow Graph.
Build in your IDE →Identity, policy, vault, and audit cut across every pillar. Events are organizational memory — the trail that makes people and AI co-evolution auditable.
How Closure earns trust →Drift scans open Issues on the graph and tiered heal repairs them under approval; promotion gates on what's still open. Versions, Dev → Test → Prod promotion, and rollback live in Ops. Goals read Events and propose evolutions — the product improves itself, governed.
Drift, heal & the gate →Build in your IDE with Platform MCP — Closure gives your IDE a product model. Review, approve, and visually edit in the console.