{
  "uid": "cogitave.learn.project-products-into-core",
  "kind": "module",
  "href": "/modules/project-products-into-core/",
  "title": "Project products into Core",
  "summary": "See how content projects into Cogitave Core as typed, content-addressed nodes rather than separate silos, and how the fact registry's cite-not-restate rule and fact-drift scanner keep one owner per fact across the estate.",
  "type": null,
  "products": [
    "cogitave-core"
  ],
  "roles": [
    "developer"
  ],
  "levels": [
    "intermediate"
  ],
  "subjects": [
    "software-engineering"
  ],
  "headings": [],
  "source": "By the end of this module, you'll be able to:\n- Explain why Cogitave treats docs, standards, and learn content as projections of one graph rather than separate stores.\n- Describe how a source document becomes a queryable node: the ACQUIRE-to-PUBLISH pipeline, its UID and content-addressed contentHash, and the closed edge set that links it in.\n- State the fact registry's cite-not-restate rule - one owner per fact, everything else points - and what the fact-drift scanner checks for.\n- Read Core's Day-0 status accurately: the registry and scanner run on the mirror as plain files today, and full graph projection lands when Core runs.\n",
  "units": [
    "cogitave.learn.project-products-into-core.introduction",
    "cogitave.learn.project-products-into-core.how-content-projects-into-core",
    "cogitave.learn.project-products-into-core.the-fact-registry",
    "cogitave.learn.project-products-into-core.knowledge-check",
    "cogitave.learn.project-products-into-core.summary"
  ],
  "durationInMinutes": 25,
  "badge": "cogitave.learn.project-products-into-core.badge",
  "partOf": "cogitave.learn.paths.build-on-core"
}