Paul Miles — CLM Business Glossary Squad Terms of Reference (one-pager)

Tag: S-2026-07-11-paul-clm-glossary-squad-tor Type: own-writing Author(s): Paul Miles (Red Strata), drafted by AI agent from existing wiki/Open Brain sources Date of source: 2026-07-11 Date ingested: 2026-07-11 Authority weight: medium — a consolidation of previously sourced squad-design material into a governance document; introduces no new primary claims Raw file: S-2026-07-11-paul-clm-glossary-squad-tor.md

Superseded 2026-07-12 by Paul Miles — CLM Business Glossary Squad TOR, client-applied update — Paul’s client-applied revision of this TOR. This page is preserved unchanged per schema §6 (never delete; supersession is marked, not removed).

What it claims

A one-page Terms of Reference for the squad responsible for creating the Credit Lifecycle Management (CLM) Business Glossary, structured as exactly three sections per Paul’s brief: Squad Objectives; Key scope items (In scope / Out of scope); Key considerations / dependencies. Objectives: consolidate every Day 1 and Day 2 CLM business term into a single mastered glossary with Policy/Process/Regulatory metadata; front-load Day 1 critical terms (weeks 1–4; full baseline ~5–6 weeks); deliver the H2 2026 SREP business-glossary commitment aligned to BCBS 239/IRB/EBA; run two cross-functional squads (~6–7 core each, ~250 terms/week combined) against a ~500–1,000 term scope with the 399-term reconciled glossary as the recommended baseline; publish to the governed master via the 7-stage Build Kit process. In scope: Day 1 + Day 2 terms harvested from the Matrix, ODS, Day 1 design and Policy & Covenants; the 7-stage process including Stage 7 change governance (T-07/T-08); fast-track governance with a 3–5 working-day SME SLA and fortnightly CLM Design Sub-Committee escalation; authoring standards T1–T6/D1–D8 with C-QA. Out of scope: technical metadata/ODS mapping, DQ metric implementation, new governance bodies, the Taxonomy Knowledge Tool build, new vendor tooling, and glossary operating-model meta terms. Considerations/dependencies: SME ~2 days/week assumption, re-baselining on confirmed harvest count, the decisions currently pending on Paul (399-term adoption, tier split endorsement, POL-01..16 mapping, Industry Glossary usage pattern, CR intake channel/SLA, D9 Source Anchored), T-05 validation before hard tagging, guardrail discipline (GR-01..14, GR-BA, no numeric auto-approval), and the six known delivery risks.

Notable quotes

None — the document is a structured summary; no distinctive verbatim phrasing worth preserving beyond the raw file itself.

What’s speculative vs. asserted

Asserted: squad structure, delivery process, governance route, scope boundaries and guardrails (all restating approved squad-design sources). Speculative/planning: throughput and sizing figures (~120–140 terms/week per squad, ~500–1,000 term scope, 5–6 week baseline) are explicitly flagged as planning estimates pending the confirmed harvested term count; the 399-term baseline is a recommendation awaiting Paul’s adoption decision.

Topics this feeds

• CLM Glossary Acceleration Squad — the project this TOR formally frames.

Open questions raised

None new — the TOR’s “Decisions pending” list restates the open questions already tracked on the project page (399-term adoption, Core/Essential/Extended endorsement, POL-01..16 mapping, Industry Glossary usage pattern, CR channel + triage SLA, D9 Source Anchored).