{
  "uid": "cogitave.learn.inherit-the-project-baseline",
  "kind": "module",
  "href": "/modules/inherit-the-project-baseline/",
  "title": "Inherit the project baseline",
  "summary": "How a new repository is born on the paved road with its whole ruleset already inherited, how to tell always-on standards from the ones a product type pulls in, and how to find an existing pattern before writing anything new.",
  "type": null,
  "products": [
    "cogitave-core"
  ],
  "roles": [
    "developer",
    "solution-architect"
  ],
  "levels": [
    "beginner"
  ],
  "subjects": [
    "software-engineering"
  ],
  "headings": [],
  "source": "By the end of this module, you'll be able to:\n- Explain how a new repository inherits its complete ruleset automatically - the floor, the standards, the scaffold, the lifecycle, and the identity - instead of re-deciding the rules.\n- Scaffold a repo from `templates/base` plus its per-type template so the baseline is baked in from birth.\n- Distinguish always-on standards from the conditional standards a product type additionally pulls in.\n- Apply reuse-first / discover-before-generate: query the patterns catalog and start from a named artifact before writing new code.\n- State honestly what is enforced today versus what turns on at cutover.\n",
  "units": [
    "cogitave.learn.inherit-the-project-baseline.introduction",
    "cogitave.learn.inherit-the-project-baseline.what-the-baseline-gives-you",
    "cogitave.learn.inherit-the-project-baseline.reuse-first-discover-before-you-build",
    "cogitave.learn.inherit-the-project-baseline.knowledge-check",
    "cogitave.learn.inherit-the-project-baseline.summary"
  ],
  "durationInMinutes": 23,
  "badge": "cogitave.learn.inherit-the-project-baseline.badge",
  "partOf": "cogitave.learn.paths.contributor-onboarding"
}