{
  "uid": "cogitave.learn.core-model-fundamentals",
  "kind": "module",
  "href": "/modules/core-model-fundamentals/",
  "title": "The one-model architecture",
  "summary": "Explain why an AI-native organization runs on one canonical property graph that humans and agents both query, what its node/edge model and identity scheme look like, and why a labeled property graph is the right substrate. Cogitave's Core is the concrete example.",
  "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 the one-model thesis: why a single canonical graph that documentation, the IDP, governance, infrastructure, and agents all project from beats one store per domain.\n- Describe the canonical graph itself: its node and edge types, its two orthogonal identifiers (`uid` and `contentHash`), and the three materializations served from it - using Cogitave's Core as the worked instance.\n- Explain why the substrate is a labeled property graph specifically, and why the relational, RDF, and federated alternatives are rejected (the reasoning Cogitave's ADR-0001 records).\n- State accurately what such a model decides today versus what is architecture to build against, without overstating a running product.\n",
  "units": [
    "cogitave.learn.core-model-fundamentals.introduction",
    "cogitave.learn.core-model-fundamentals.the-one-model",
    "cogitave.learn.core-model-fundamentals.the-property-graph-substrate",
    "cogitave.learn.core-model-fundamentals.knowledge-check",
    "cogitave.learn.core-model-fundamentals.summary"
  ],
  "durationInMinutes": 24,
  "badge": "cogitave.learn.core-model-fundamentals.badge",
  "partOf": "cogitave.learn.paths.build-on-core"
}