Summary

You now have a working command of the patterns catalog: what it is, how to read an entry, and the loop that gets you from "I need to do X" to "I am extending a named artifact."

In this module, you:

• Saw the gap the catalog closes: reuse-first stated the principle, and the patterns catalog is the artifact that turns it into a one-hop answer to "how does Cogitave do X", recorded in ADR-0022.
• Read the five-section entry shape - Problem, The Cogitave way, Governing standard(s), Reusable artifact, Anti-pattern - in both the human doc and the machine-readable catalog.yaml, and saw several task-level intents share one canonical_pattern doc.
• Learned that the authority always lives in the governing standard - a pattern that disagrees with its standard is a bug, never the other way round.
• Ran the four-step discover-before-you-build loop: query before you generate, read the entry and follow its two links, start from the named artifact, and - if you must go off-road - record the rationale, own the maintenance, and still satisfy the Definition of Done.

Next steps

• Inherit the project baseline - how a repo scaffolded from a pattern's reusable artifact inherits the floor, the standards, the lifecycle, and the identity automatically.
• Patterns catalog - go back to the source and query it for your next real task.
• ADR-0022 - the decision record behind both the catalog and the project baseline.