Connected Product Graph
A Connected Product Graph is a single, linked structure that ties every product artifact — research, requirements, decisions, prototype, and PRD — into one graph, so a change in one place surfaces its impact everywhere it connects.
Most product work is scattered across separate documents and chat threads: a research doc here, a requirements sheet there, a PRD somewhere else. Nothing knows about anything else, so when a requirement changes, no one can tell which prototype screens or PRD sections are now stale.
A Connected Product Graph treats each artifact as a node with a stable identifier and explicit references to what it derives from. Research grounds requirements; requirements are realized by prototype screens and implemented in the PRD. Because the links are explicit, the graph can detect impact: change one requirement and it flags every downstream node that depends on it.
The key benefit of a Connected Product Graph is not generation — general assistants already generate documents — but traceability: keeping every product artifact consistent as the product evolves.
A team changes a requirement from "allow guest checkout" to "require login before checkout." In a Connected Product Graph, the two prototype screens and the PRD section that realize that requirement are immediately flagged as needing review — instead of silently drifting out of sync.
ArcPM is built around the Connected Product Graph: every stage — industry research, competitors, personas, requirements, prototype, PRD — produces nodes that link back to their sources, and changing an upstream node surfaces the affected downstream ones for review.
See ArcPM