Paul Miles — Glossary Build Kit Reference Usage Guidance (T-05 references & Industry Glossary as source)

Tag: S-2026-07-09-paul-glossary-reference-usage-guidance Type: own-writing Author(s): AI agent (Claude, Cowork) for Paul / Red Strata Date of source: 2026-07-09 Date ingested: 2026-07-09 Authority weight: medium — an operational guidance record derived strictly from the governed Build Kit v1.2 artefacts (prompts, skills, guardrails, T-05, procedures); it interprets existing controls rather than creating new ones. The A/B/C usage-pattern options are proposals pending a squad decision. Raw file: S-2026-07-09-paul-glossary-reference-usage-guidance.md

What it claims

Records the delivery of Glossary Build Kit — How Regulatory, Policy and Process References Are Used (docx + md, saved to 09 Taxonomy Tool\), answering two questions from Paul.

On the Regulatory references (T-05): the kit uses regulatory material in two distinct roles — a tagging reference (a T-05 metadata row: Ref ID, family, instrument, scope description) and a harvest source (an actual document registered in T-01 and extracted via P-01). T-05 rows are pointers, not documents: no source file containing the regulation is required for P-04 tagging to work, and the prompt does not search online — GR-05 confines it to the supplied T-06 rows + T-05 workbook and GR-07 forbids introducing outside content; the web research behind starter rows REG-001…009 happened once, at kit build time, flagged for Regulatory/Risk SME validation. Hard tags require an exact T-05 match (validated sheet); soft tags are disclosed inferences routed to review; missing references go to a gap list, never invented. If a regulation is listed with no source file (the normal case): tagging is unaffected, but the regulation’s own definitions never enter the glossary unless the instrument or a governed extract is separately harvested at Tier 1/2 — and consolidation can only anchor to wording actually harvested.

On Policy and Process references: identical mechanics with three differences — the T-05 Policy/Process sheets ship empty and are populated at Stage 0 (task 0.6) from the bank’s policy register and process taxonomy; a policy may need both a T-01 registration (content) and a T-05 row (tagging), which are separate; process references have no harvestable document at all. Any Regulatory or Policy tag removes bulk-approval eligibility (GR-BA).

On the Industry Business Glossary as a co-source: six pros (regulatory-action completeness, prioritised scoping baseline, systematic bank-vs-industry divergence detection, drafting acceleration, T-06-shaped frictionless ingestion, documented provenance) against six cons/risks (it is Tier-6 business documentation whose definitions paraphrase — not reproduce — regulatory wording, so consolidation must not anchor to it over governed bank policy; its POL-01…16 and REG-010…013 tags do not resolve to T-05 V1.1 and must be remapped or demoted to soft; +140-term workload and GR-BA review load; no governance short-cut — all rows Drafted; currency/ownership; GR-14 discipline on later batches). Three usage patterns offered: A seed master (recommended by the file’s own design — load first, run bank sources incrementally against it), B ordinary co-source, C benchmark only; the choice is left to Paul/the squad.

Notable quotes

“A T-05 row is a pointer, not a document.” (Guidance, §1.1.)

What’s speculative vs. asserted

• Asserted (grounded in kit artefacts): the two-role model, the P-04 input list and matching rule, the no-online-lookup behaviour (GR-05/GR-07), the empty-ships state of the Policy/Process sheets and Stage 0 task 0.6, the GR-BA consequence, the industry file’s characteristics (140 terms, tag counts, Drafted status, POL/REG extensions).
• Speculative / judgement: the Tier-6 (vs Tier-7) placement of the industry file pending SME review; the A/B/C pattern trade-offs and the recommendation to prefer A — these apply the kit’s controls but the decision is the squad’s.

Topics this feeds

• CLM Glossary Acceleration Squad — operational guidance for the squad on populating/using T-05 and on whether to feed the industry reference glossary into the pipeline.

Open questions raised

• Which usage pattern (A seed master / B co-source / C benchmark) the squad adopts for the industry glossary, and at what confirmed Source Authority Tier.
• Extension + SME validation of T-05 (REG-010…013; POL-01…16 mapping to the bank’s governed policy register) before any hard tags carried by the industry file are accepted.