{
  "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 Core's node and edge model,\nhow to query it, and how to reach it over MCP. This module closes the loop on a\ndifferent question: where does the *content* come from? A product spec, an\nengineering standard, an ADR, or the module you are reading right now - how does\nit end up as a node you can query, rather than a file that quietly drifts from\nwhatever else says the same thing?\n\n## One graph, not a pile of silos\n\n[Cogitave Core's architecture](../../../../core/docs/architecture.md) states the\nthesis directly: docs, the internal developer portal, governance, compliance\nevidence, and infra are **projections of one graph** - never separate stores. A\n`Doc`, a `Standard`, an `ADR`, and this very learning `Unit` are all typed nodes\nin the same property graph, addressed the same way, queried through the same\nMCP tools a human's UI calls. There is no second copy for \"the docs system\" and\na 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 Cogitave keeps one authoritative\nowner per load-bearing fact so the rest of the estate cites it instead of\nre-typing it and drifting (unit 3).\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 the\n> estate is building toward, and parts of it (the fact-drift scanner) already\n> 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 Cogitave Core**; finishing it earns the\npath's trophy.\n",
  "partOf": "cogitave.learn.project-products-into-core",
  "durationInMinutes": 4,
  "quiz": null
}