Paul Miles — CLM Glossary Term & Definition Authoring Standards (2-slide pack)

Tag: S-2026-07-05-paul-glossary-term-definition-standards Type: own-writing Author(s): AI agent (Claude, Cowork) for Paul / Red Strata Date of source: 2026-07-05 Date ingested: 2026-07-05 Authority weight: medium — an industry-anchored authoring standard (ISO/DAMA anchors web-verified) aligned to the Build Kit’s governed standards; pending squad adoption. Raw file: S-2026-07-05-paul-glossary-term-definition-standards.md

What it claims

A two-slide authoring standard for the Glossary Squad and future authors covering how to create (1) the Term and (2) the Term Definition, leading with an industry perspective and aligned to the programme’s current thinking.

Slide 1 — Creating the Term (T1–T6, new standard): business name in business language (never system/code names); singular noun phrase in Title Case; the regulator’s full official form as master name with acronyms as aliases; one term = one concept (homonyms qualified into separate terms, synonyms recorded as aliases); no definition hidden in the name; consistent compound construction from approved master terms. Industry basis: ISO 704 (one term per concept), ISO/IEC 11179-5 (naming principles), DAMA-DMBOK (glossary as governed compendium of term names and definitions).

Slide 2 — Writing the Term Definition (D1–D8): restates the Build Kit’s definition-quality standard DQ-1…DQ-8 one-for-one, each anchored to ISO/IEC 11179-4’s requirements/recommendations, and leads with ISO 704’s intensional-definition pattern (“A [broader concept] that [distinguishing characteristics]”). Scope boundary preserved: the standard governs wording quality only; definition conflicts are resolved via the source-authority hierarchy plus SME decision, checked at QA gate P-06.

Deliverables: CLM_Glossary_Term_and_Definition_Standards.pptx (2 slides, black & white on white, Asperi font) + .md twin + approach record, saved to _ClaudeWorkspace/03 Credit Lifecycle/Glossary Standards/.

Notable quotes

“A [broader concept] that [distinguishing characteristics]” — the ISO 704 intensional-definition pattern the pack adopts as the required definition form (Slide 2).

What’s speculative vs. asserted

  • Asserted (grounded): the ISO/IEC 11179-4 requirements/recommendations (read from the published standard text); ISO 704 intensional-definition preference; the DQ-1…8 mapping (read from the Build Kit’s definition-quality.md); the full-official-form rule (decision already taken 2026-06-29 in the Perspective-2 standardisation).
  • Speculative / to-confirm: the T1–T6 naming rules are a new proposed standard (the Build Kit had no formal term-naming standard) — pending Paul/squad adoption; the ✗/✓ examples are illustrative authoring examples, not glossary content.

Topics this feeds

Open questions raised

  • Squad adoption of T1–T6 as the formal naming standard, and whether it should be folded into the Build Kit (e.g. a term-naming.md skill beside definition-quality.md).
  • Whether Title Case master names should also govern how terms render in downstream tools (Confluence, ODS mappings).