Project products into Core
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.
Units5
Duration25 min
Levelintermediate
By the end of this module, you'll be able to:
- Explain why Cogitave treats docs, standards, and learn content as projections of one graph rather than separate stores.
- 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.
- State the fact registry's cite-not-restate rule - one owner per fact, everything else points - and what the fact-drift scanner checks for.
- 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.
Prerequisites
- Completion of the first three modules in this path (the Core node/edge model, Cogitave Query, and the native MCP interface) is recommended but not required.
- No prior graph-database experience needed.