docs: SR 26-2 replaces SR 11-7

[nrichers]

What and why?

Updates the docs site for SR 26-2, the April 2026 interagency guidance that supersedes SR 11-7. Adds site/about/use-cases/sr-26-2.qmd with a legacy URL alias, removes sr-11-7.qmd, and refreshes the MRM overview, glossary model definition, navigation, training tiles, cross-links, style-guide example, release copy, document-checker template, ongoing monitoring intro, and the embedded agentic AI notebook closing paragraph (SR 26-2 nuance for GenAI/agentic scope).

How to test

After the PR preview deploys, spot-check:

• SR 26-2 use case
• Legacy SR 11-7 URL redirects
• Model risk management
• MRM overview (dropped from sidebar in What could docs & training for AI governance look like? #1087)
• Homepage

Local: quarto preview from site/ if you prefer.

What needs special review?

• Wording for SR 26-2 model definition vs. regulatory text in glossary and overview.
• Training slide bubbles and compliance table links.

Dependencies, breaking changes, and deployment notes

None. External links use the official SR 26-2 letter URL.

Release notes

Documentation now reflects SR 26-2 as the current U.S. interagency MRM guidance and supersedes SR 11-7 across use cases, training references, and related pages.

Checklist

• What and why
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Documentation updated (if required)
• Tested locally

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[github-actions]

Lighthouse check results

⚠️ WARN: Average accessibility score is 0.87 (required: >0.9) — Check the workflow run

Show Lighthouse scores

Folder depth level checked: 0

Commit SHA: fa82bdb

Modify the workflow to check a different depth:

• 0: Top-level navigation only — /index.html, /guide/guides.html, ...
• 1: All first-level subdirectories — /guide/.html, /developer/.html, ...
• 2: All second-level subdirectories — /guide/attestation/*.html, ...

Page	Accessibility	Performance	Best Practices	SEO
/developer/validmind-library.html	0.85	0.68	1.00	0.82
/get-started/get-started.html	0.85	0.71	1.00	0.73
/guide/guides.html	0.85	0.69	1.00	0.82
/index.html	0.93	0.68	1.00	0.82
/releases/all-releases.html	0.86	0.69	1.00	0.73
/support/support.html	0.91	0.68	1.00	0.82
/training/training.html	0.85	0.66	0.96	0.73

[validbeck]

MRM overview (dropped from sidebar in #1087)

Where is this linked from? I think I tried to get rid of it once and got confused because it breaks some stuff. Hmm...

3 results - 3 files

site/guide/monitoring/ongoing-monitoring.qmd:
  153  
  154: [^1]: [Regulatory requirements](/about/overview-model-risk-management.qmd#regulatory-requirements)
  155  

site/releases/2024/2024-dec-06/release-notes.qmd:
  25      contents:
  26:       - path: ../../../about/overview-model-risk-management.qmd
  27          title: "Learn more — <br>{{< var validmind.platform >}}"

site/training/risk-governance-fundamentals.qmd/risk-governance-fundamentals.qmd:
  87  ::: {.tc}
  88: [Learn more ...](/about/overview-model-risk-management.qmd){.button target="_blank"}
  89  :::

Hm, I see. Should this not just be general risk management?

Important

Otherwise, I think just a note for myself, SR 11-7 is mentioned in the glossary (and now the key concepts) in these PRs and will need to be updated after your PRs merge:

• #1339
• validmind/validmind-library#517

[validbeck]

Approving on the condition that we remove the loose MRM page and replace links to it (or remove links) with something more germane. 🤞🏻

[github-actions]

PR Summary

This pull request updates the documentation to replace references to SR 11-7 with SR 26-2. Key changes include:

• Updating file paths and links in workflow files, markdown guides, and configuration files so that the documentation now points to the correct locations (e.g. changing /about/contributing/using-the-documentation to /about/using-the-documentation).
• Modifying content in multiple markdown files (e.g., AGENTS.md, glossary, style-guide, overview-model-documentation, and others) to reflect the new regulatory guidance from SR 26-2 instead of SR 11-7.
• Adjusting aliases and navigation links across the site, including the removal of the deprecated SR 11-7 use-case file and the addition of the new SR 26-2 documentation file.
• Updating release notes and training materials to align with the updated regulatory framework and to ensure consistency in references across the platform.
• Minor text adjustments in code comments and scripts to ensure that internal links and the generated documentation index are correctly updated.

Overall, these changes refocus the documentation on the current regulatory expectations provided by SR 26-2, while also ensuring that all paths and references align with the updated content structure.

Test Suggestions

• Run the GitHub workflow for documentation validation to ensure all file paths and links are correct.
• Manually review rendered pages (e.g., using a local Quarto build) to verify that updated links, aliases, and navigation items are functioning correctly.
• Check the chatbot product map and generated markdown files in the LLM output to ensure that the new paths are correctly referenced.
• Verify that the removal of SR 11-7 content and addition of SR 26-2 content do not break any existing navigation or search functionalities.

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview