{
  "uid": "cogitave.learn.navigate-the-patterns-catalog.summary",
  "kind": "moduleUnit",
  "href": "/modules/navigate-the-patterns-catalog/summary/",
  "title": "Summary",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "Next steps"
  ],
  "source": "You now have a working command of the patterns catalog: what it is, how to read\nan entry, and the loop that gets you from \"I need to do X\" to \"I am extending a\nnamed artifact.\"\n\nIn this module, you:\n\n- Saw the gap the catalog closes: reuse-first stated the principle, and the\n  patterns catalog is the artifact that turns it into a one-hop answer to\n  \"how does Cogitave do X\", recorded in ADR-0022.\n- Read the **five-section entry shape** - Problem, The Cogitave way, Governing\n  standard(s), Reusable artifact, Anti-pattern - in both the human doc and the\n  machine-readable `catalog.yaml`, and saw several task-level intents share\n  one `canonical_pattern` doc.\n- Learned that **the authority always lives in the governing standard** - a\n  pattern that disagrees with its standard is a bug, never the other way round.\n- Ran the **four-step discover-before-you-build loop**: query before you\n  generate, read the entry and follow its two links, start from the named\n  artifact, and - if you must go off-road - record the rationale, own the\n  maintenance, and still satisfy the Definition of Done.\n\n## Next steps\n\n- @cogitave.learn.inherit-the-project-baseline - how a repo scaffolded from a\n  pattern's reusable artifact inherits the floor, the standards, the lifecycle,\n  and the identity automatically.\n- The **patterns catalog**, in the estate's standards repository, is the\n  source - go back and query it for your next real task.\n- **ADR-0022** is the decision record behind both the catalog and the\n  project baseline.\n",
  "partOf": "cogitave.learn.navigate-the-patterns-catalog",
  "durationInMinutes": 3,
  "quiz": null
}