{
  "uid": "cogitave.learn.apply-naming-standards.summary",
  "kind": "moduleUnit",
  "href": "/modules/apply-naming-standards/summary/",
  "title": "Summary",
  "summary": "",
  "type": null,
  "products": [],
  "roles": [],
  "levels": [],
  "subjects": [],
  "headings": [
    "Next steps"
  ],
  "source": "You can now name a new artifact the way the estate does, and tell a functional\nkeyword apart from a product codename.\n\nIn this module, you:\n\n- Learned the **cross-cutting naming principles** from the naming standard -\n  keyword-first, no redundant prefix, casing by role, immutable IDs with\n  mutable facts in metadata - and that naming is **machine-enforced** by CI\n  gates, not reviewer goodwill.\n- Named the things you touch first: repos as plain kebab-case keywords, UIDs as\n  dotted immutable IDs, code identifiers cased by role per language, files and\n  root markers by their convention, and branches as\n  `type/ISSUE-ID-kebab-description`.\n- Separated a **functional keyword** from a **product codename**: the Roots\n  lexicon, the codename-versus-public-name-versus-repo-name distinction, the rule\n  that you **never concatenate** the two, and when a codename is allowed versus\n  when a primitive is codename-exempt (ADR-0007, the codename standard).\n\n## Next steps\n\n- @cogitave.learn.commits-and-versioning - how the commit and branch *types* you\n  just used carry versioning meaning, the next standard on the engineering path.\n- The **naming standard** is the canonical, full per-domain reference (cloud\n  tags, databases, observability, events, IaC) in the estate's standards\n  repository, for when you need a rule this module did not cover.\n",
  "partOf": "cogitave.learn.apply-naming-standards",
  "durationInMinutes": 3,
  "quiz": null
}