Docs · Docs
Concepts
Closure Platform is a runtime for semantic applications: UI, workflows, AI, integrations, and governance in one product graph. The product exists as governed data; code is the runtime around it.
Start with Everything is JSON-LD, then the Pillars.
Why that works: The Product Graph.
Four pillars
| Pillar | Role |
|---|---|
| Experiences | Hostable web apps rendered from the graph |
| Workflows | Forms, agents, human review — one process |
| Knowledge | Skills, files, live data, and tools for AI |
| Integrations | Connectors that import, write (seal), and trigger |
Your IDE (via Platform MCP) and the Platform APIs author the graph. Events are organizational memory.
Vocabulary
| Term | Meaning |
|---|---|
| Product graph | Typed objects for UI, process, knowledge, integrations, and activity |
| Experience | Hostable web app (pages → components) on that graph |
| Workflow Graph | Process source of truth — forms / chat / agents as interfaces |
| Seal | Write structured results into a system of record under policy |
| Knowledge | Data (live objects) · Skills (playbooks) · Files (corpus RAG) · Tools (schema:tool packs) |
| Events | What happened — the audit trail that feeds heal and Goal-driven evolution |
Your IDE
Closure doesn’t replace your IDE. It gives your IDE a product model.
Author from Cursor, Claude Code, or VS Code via Platform MCP; review and approve in the Closure console. Secrets collect through vaulted forms — Build in your IDE.