Skip to content

docs: SR 26-2 replaces SR 11-7 (sc-16033)#1331

Open
nrichers wants to merge 3 commits into
mainfrom
nrichers/sc-16033/update-docs-for-sr-26-2-replaces
Open

docs: SR 26-2 replaces SR 11-7 (sc-16033)#1331
nrichers wants to merge 3 commits into
mainfrom
nrichers/sc-16033/update-docs-for-sr-26-2-replaces

Conversation

@nrichers
Copy link
Copy Markdown
Collaborator

@nrichers nrichers commented May 16, 2026

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:

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

Add sr-26-2 use-case page with alias for legacy URL, refresh MRM and
glossary framing, and update cross-links, training tiles, and release
copy. Align embedded agentic AI notebook closing text with SR 26-2.
@github-actions
Copy link
Copy Markdown
Contributor

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.

@nrichers nrichers added the documentation Improvements or additions to documentation label May 16, 2026
@github-actions
Copy link
Copy Markdown
Contributor

PR Summary

This PR updates the documentation and related pages by replacing references to the outdated SR 11-7 regulation with the new SR 26-2 guidance. The changes span multiple files including configuration files (like _quarto.yml), style guides, overview and use-case pages, glossary definitions, and training materials. In addition to updating the regulation label, the PR revises the related descriptive text to reflect the new regulatory requirements and supersession details for SR 26-2. Links, internal navigation, and button labels have also been updated to point to the corresponding SR 26-2 implementation guide and regulatory links. Overall, the functional change improves the accuracy of regulatory compliance documentation and aligns the content with the latest guidance from U.S. supervisory authorities.

Test Suggestions

  • Verify that all pages and links previously referencing SR 11-7 now display SR 26-2 with correct descriptions and links.
  • Check that the navigation and button labels correctly point to the new SR 26-2 implementation guide.
  • Perform a manual review of the updated pages to ensure text consistency and that no outdated references remain.
  • Test the documentation search functionality to ensure that queries for SR 26-2 return the correct results.

@nrichers nrichers requested a review from validbeck May 17, 2026 21:52
@github-actions
Copy link
Copy Markdown
Contributor

Validate docs site

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

@github-actions
Copy link
Copy Markdown
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant