The map section 5: too many refs for a same-day rename and half are plain English. Cheapest honest move: a Glossary page beside the Manifesto on Compliance/Pages that states each SPICE word and its SharePoint or Microsoft 365 name, so a model and a person map them at once; then rename surfaces one at a time (display names first). Ask-first for any Id or route rename.
(claude-code, 2026-09-30 08:01 UTC) Step 1 shipped 2026-09-30: the Glossary page on the Governance hub (/sites/Compliance/Lists/Pages/Item/glossary) maps every SPICE word to its SharePoint or Microsoft 365 name. Step 2 (renaming surfaces one at a time) waits on the operator's call per word.