{
  "uid": "cogitave.learn.project-products-into-core.introduction",
  "kind": "moduleUnit",
  "href": "/modules/project-products-into-core/introduction/",
  "title": "Introduction",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "One graph, not a pile of silos",
    "What you will get from this module"
  ],
  "source": "In the first three modules of this path you learned the canonical model's node\nand edge model, how to query it, and how to reach it over MCP. This module\ncloses the loop on a different question: where does the *content* come from? A\nproduct spec, an engineering standard, an ADR, or the module you are reading\nright now - how does it end up as a node you can query, rather than a file that\nquietly drifts from whatever else says the same thing?\n\n## One graph, not a pile of silos\n\nThe pattern is one graph, not many stores: an AI-native org keeps its docs,\ninternal developer portal, governance, compliance evidence, and infra as\n**projections of a single graph** - never separate silos. Cogitave's own Core\nis the worked example, and\n[its architecture doc](../../../../core/docs/architecture.md) states that thesis\ndirectly for Cogitave's estate. A `Doc`, a `Standard`, an `ADR`, and this very\nlearning `Unit` are all typed nodes in the same property graph, addressed the\nsame way, queried through the same MCP tools a human's UI calls. There is no\nsecond copy for \"the docs system\" and a third for \"the learn platform.\"\n\nThat only works if content actually gets **into** the graph, and a fact true in\none place cannot silently go stale in another. This module covers both halves:\nhow a document becomes a node (unit 2), and how one authoritative owner per\nload-bearing fact keeps the rest of the estate citing it instead of re-typing it\nand drifting (unit 3) - shown through Cogitave's own registry.\n\n> [!IMPORTANT]\n> Cogitave Core is a **specification and architecture today**, not a running\n> product. No Core server is live yet. The mechanics in this module - the\n> pipeline, the UID/contentHash scheme, the fact registry - are the design\n> Cogitave's estate is building toward, and parts of it (the fact-drift scanner)\n> already run today as plain checks over files, ahead of any live graph.\n\n## What you will get from this module\n\nThe ability to explain, concretely, how a document becomes a queryable node,\nand why \"the estate is a second brain\" is more than a slogan: it names a real\ngap - facts restated in prose instead of linked - and a real, checkable fix.\nThis is the last module of **Build on a single canonical model**; finishing it\nearns the path's trophy.\n",
  "partOf": "cogitave.learn.project-products-into-core",
  "durationInMinutes": 4,
  "quiz": null
}