Skip to content
Unified Product GraphBeta
Get Started
Unified Product Graph

The open specification for product knowledge.
312 types. 36 domains.
MIT Licensed

Understand
The SpecBlog
Explore
Graph ExplorerEntitiesEdgesLifecyclesFrameworksPlaybooksApproaches
Adopt
MCP ServerSDKCLISkillsIntegrationsGitHub ↗
© 2026 Unified Product Graph · MIT License · Privacy · TermsBuilt by The Product Creator

Adopt

5 surfaces

Surfaces

MCP Server
SDK

Compare

1
MCP vs SDK vs CLI

Guides

8
Building a DocumentImplementing an AdapterValidationMigrationsDriving an LLMRendering UIsBootstrapping a GraphJSDoc Cascade

Cookbook

10
All recipesFind all nodes of a given typeWalk the graph: persona → jobs → featuresSearch the graph by title or descriptionCreate a node with an auto-parent edgeUpdate a node: status transition or partial patchValidate before persisting a batch writeGate CI on graph healthWrite a minimal adapter (Markdown vault → UPG)Feed a typed graph slice to Claude (RAG-style context)Wire UPGClient into a Claude agent (tool use)

Playground

1
Try the SDK

Client API

4
UPGClientclient.nodesclient.edgeshealth / search / verify

Core primitives

10
CatalogShapesRegistryGrammarPropertiesPresentationIntelligencePlaybooksApproachesRegions
CLI
Skills
Integrations
SDK›Guides›JSDoc Cascade

SDK Guide

JSDoc Cascade

How the SDK reference pages on this site stay in lockstep with the source. JSDoc in packages/upg-spec extracts at build time and feeds both the TypeScript language server and unifiedproductgraph.org.

The pipeline

Every type, constant, and function in @unified-product-graph/core is documented with JSDoc @example blocks. The site documentation at /sdk/reference and the TypeScript language server surface are generated from the same source: the spec package's TSDoc. No separate documentation files.

The pipeline: JSDoc in packages/upg-spec/src/** is extracted at build time by the TypeScript Compiler API (the same tool that generates UPG_PROPERTY_SCHEMA). The extraction output feeds the unifiedproductgraph.org documentation renderer. When a property shape or edge definition changes in the spec, the site docs update at the next build — documentation drift is structurally impossible.

Adapter-author experience

Adapter authors writing against the SDK see live @example blocks in their editor for every exported symbol. The @example patterns shown across this site are the same examples in the source — they are verified by the spec's property-schema-coverage regression test (UPG-448).