Closure
Request access

Docs · Build paths

Build paths

One product graph. Three first-class paths.

Closure Platform is the runtime for semantic applications — UI, process, AI, and integrations as governed data. Pick the path that matches how your team already works. For most teams, the IDE is where the loop starts.

A — Your IDE (Cursor, Claude Code, VS Code)

Your coding agent gets a real product model — not file trees.

  1. Sign in to Closure SaaS (closureapps.com/console) — no local platform process required.
  2. Install Platform MCP pointed at that console URL and pull Closure-way skills.
  3. Ask the agent to scaffold Experiences / start builds / pull knowledge. It grounds itself on the runtime (platform_docs_search, platform_taxonomy), dry-runs before writing (platform_validate), and completes secrets via platform_collect_start in the browser.
  4. Preview in Closure on SaaS — Closure remains the source of truth, and platform_experience_verify must pass before anything ships.

Regulated teams on a private or on-prem install use the same steps with their console URL. Full setup: Build in your IDE. SDK for host apps: JavaScript SDK.

B — External application

Use Closure as the process + data + Forms backbone behind your product UI.

  1. Authenticate to Closure (SaaS social / org login in production; demo credentials only for sandboxes).
  2. Query product data via GraphQL (/api/graphql).
  3. Start and advance workflow runs.
  4. Optionally embed Forms with @closure-sdk/react (or @closure-platform/client) through your BFF — never put vault secrets in the browser.

Best when you already have a host app and need governed collect → seal → agent steps.

C — Closure console

Work the graph directly in Closure:

  1. Open the console and pick a pillar — Experiences, Workflows, Knowledge, or Integrations.
  2. Edit pages, components, and process graphs in the workbench; preview Dev / Test / Prod.
  3. Governed build workflows mutate the graph under quality gates; approvals and review live here.
  4. Preview / run; ship embeds or host paths.

Best for review, approvals, and hands-on editing when the UI itself lives on the graph.

Agents & orchestration

  • Hybrid orchestration — gateways, waits, multi-agent teams as one node.
  • Tool packs and executors remain available at /docs/tools and /docs/agent-executors (deep links; not on the main sidebar).

Decision tree

  • Prefer Cursor / Claude Code / VS Code? → Path A (the Phase-1 default)
  • Need Closure inside an existing React/Next app? → Path B
  • Need to review, approve, or hand-edit the graph in a UI? → Path C
  • Need both? Common: IDE builds the Experience; external app embeds Forms for one journey