Knowledge is the accumulated output of every agent interaction: research reports, roadmaps, specs, decision logs, and more. It compounds over time, making each cycle faster and better informed.

Ideally, product knowledge base is version-controlled using Git, treating PM artifacts the same way engineers treat code. The folder structure should mirror the topic taxonomy: Strategy, Generation, Analysis, Delivery, and People, with additional folders for project-specific contexts such as operations and product data.
Artifacts should be stored in plain text, LLM-friendly formats like Markdown or CSV, so agents can read, reference, and build on them across every cycle.