{
  "uid": "cogitave.learn.navigate-the-patterns-catalog.introduction",
  "kind": "moduleUnit",
  "href": "/modules/navigate-the-patterns-catalog/introduction/",
  "title": "Introduction",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "What you will get from this module"
  ],
  "source": "\"How does your org do X?\" can go without a single answer for a long time. The\nreuse-first principle - discover before you generate - may already be stated as a\nhard rule, but an agent facing \"stand up a REST service\" still has to reconstruct\nthe golden path by hand: which standard governs it, which template to start from,\nwhich anti-pattern to avoid. Reconstructing that path every time, inconsistently,\nis exactly the divergence the reuse-first rule exists to kill, one layer up.\n\nA [patterns catalog](../../../../standards/docs/patterns/README.md) is the\nartifact that closes that gap. For every recurring build task it names the\n**one** sanctioned way to solve it and points at the authority that\nowns the rules. It is the paved road, made queryable in one hop instead of\nre-derived across dozens of standards.\n\n> [!IMPORTANT]\n> The catalog does not invent policy and it does not restate standards. Every\n> entry is a thin, honest pointer - the authority always lives in the standard\n> it cites. If you remember one sentence from this module, make it that one.\n\nThis module builds on the first module in this path,\n@cogitave.learn.reuse-first-engineering, which taught **why** discover-before-generate\nis the rule. This module teaches **how** to act on it: reading a catalog entry,\nusing the machine-readable index behind it, and running the loop that takes you\nfrom \"I need to do X\" to \"I am extending a named artifact.\" Cogitave's decision to\nadd both artifacts is recorded in\n[ADR-0022](../../../../standards/docs/decisions/0022-patterns-catalog-and-project-inheritance.md).\n\n## What you will get from this module\n\nBy the end you will be able to explain what the catalog is for, read any entry's\nfive fixed sections without confusing the pointer for the policy, find the\npattern for a task and follow its two links - the governing standard and the\nreusable artifact - and run the four-step discover-before-you-build loop,\nincluding the honest path for when nothing fits.\n",
  "partOf": "cogitave.learn.navigate-the-patterns-catalog",
  "durationInMinutes": 4,
  "quiz": null
}