18. What happens across many products?

Each product has one knowledge graph, shared by every team that works on that product. Graphs are kept to one product because queries slow down as a graph grows. A portfolio adopts the methodology one product at a time. The first product builds its graph, sets up the process, and hands its repeatable work to agents, and after a few months the next product follows. Some knowledge belongs to the whole enterprise: compliance and security rules, infrastructure preferences, shared deployment pipelines, and an enterprise design system. Enterprise knowledge is defined once, and every product's agents read it according to their access rights. Where products integrate, impact analysis follows the integration points into the other products' graphs. Every quarter, an agent looks across the product graphs for capabilities that are duplicated or no longer used.

On the site: Partition by Product · What Decides It · One Graph for All of a Product's Teams