Skip to content

Commit 38be049

Browse files
nrichersvalidbeckgithub-actions[bot]
authored
October 22 2024 release (#487)
* Edits up until Releases * Edits for 2024-aug-13 releases * Adjusted figcaption to center text * Edits for 2024-jul-22 releases * Edits for 2024-jun-10 releases * Edits to overview guides * Releases tweaks up to June 10 2024 * Edits to march 27 2024 wip * Final tweaks to march 27 2024 * Edited feb 14 2024 * Edited jan 26 2024 * Edited jan 18 2024 * May 22 2024 releases WIP * Edited may 22 2024 * Added _how-to-upgrade.qmd single-source * Added _how-to-upgrade.qmd to newer releases missing it * Edited nov 09 2023 * Edited oct 25 2023 * WIP Sep 27 2023 * Edited Sep 27 2023 * Tweaks to variable in buttons & links * Edited aug 15 2023 * Edited jul 24 2023 * Edited jun 22 2023 * Edited may 30 2023 * Visual tweaks * More cleanup * Some more tweaks * Final? edits * Feedback from Nik * Maybe the python docs need to be updated on remote? * Nope, just a docs-demo preview issue * Release notes to sprint 60 (#483) * Generate initial release notes * Fix LUA error * WIP edits * Initial edit pass & add images * Add new button to styles.css * Clean up styles.css * WIP more edits * WIP more edits * WIP more edits * Update button style * WIP edits * Second edit pass complete * Add button info to style guide * Minor edits * Fix broken link * Run make get-source * Final tweaks * Remove release notes notebook * Improved hover state for buttons * Adjusted style guide & README * Tweak to the convention example * Oops, I can't spell * Remove _blank guidance * Round screenshot corners more * Add fig-alt text * Address review comments from Beck * Add upgrade info and crop screencap * Ambiguous antecedents are a bad habit * Visual tweaks * Summary & final touches --------- Co-authored-by: Beck <164545837+validbeck@users.noreply.github.com> --------- Co-authored-by: Beck <164545837+validbeck@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent ac5c00d commit 38be049

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

44 files changed

+3651
-735
lines changed

README.md

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -101,14 +101,6 @@ When constructing links, refer to the `.qmd` file as Quarto will properly render
101101
|---|---|
102102
| `[Get started with JupyterHub](get-started/developer/try-with-jupyterhub.qmd)` | `[Get started with JupyterHub](get-started/developer/try-with-jupyterhub.html)` |
103103

104-
The only exceptions are within HTML, such as CSS-styled buttons which necessitate usage of `.html` href links:
105-
106-
```html
107-
<a class="btn btn-primary" role="button" style="padding: 12px;color: var(--bs-white);background: #DE257E;border-radius: 4px;margin-top: 40px;font-family: 'Inter';font-style: normal;font-weight: 700;font-size: 14px;line-height: 100%;border: 1px solid var(--bs-pink);" href="get-started/developer/try-with-jupyterhub.html">QuickStart</a>
108-
```
109-
110-
> You'll need to pay special attention to these links and manually test them to ensure that they are not broken whenever any changes to file destinations are made.
111-
112104
When constructing filepaths, including while using [Quarto's Includes](https://quarto.org/docs/authoring/includes.html) (single-sourcing feature), you'll also want start with the root directory whenever possible as this minimizes usage of unclear relative paths:
113105

114106
| Correct | Incorrect |

site/_quarto.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -112,6 +112,7 @@ website:
112112
- text: "---"
113113
- text: "RELEASES"
114114
# MAKE-RELEASE-NOTES-EMBED-MARKER
115+
- releases/2024-oct-22/release-notes.qmd
115116
- releases/2024-sep-25/release-notes.qmd
116117
- releases/2024-sep-09/release-notes.qmd
117118
- releases/2024-aug-13/release-notes.qmd

site/about/contributing/style-guide/conventions.qmd

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -119,6 +119,52 @@ Column 2, 50% wide
119119
- Keep hyperlinks in instructional text minimal — too many links can misdirect the user from the task at hand.
120120
- When possible — such as any time instructions are not single-sourced — instead of multiple inline links, make use of margin footnotes.[^5]
121121
- Whenever possible, make the link the title of the destination article. This also solves the issue of links with nebulous descriptions that do not match article titles, or links whose destinations are not clear to the user such as "Read more."
122+
- When constructing links, refer to the `.qmd` file as Quarto will properly render these into `.html` links on your behalf and check to see if the destinations are able to be resolved.
123+
- When constructing filepaths, you'll also want start with the root directory whenever possible as this minimizes usage of unclear relative paths.
124+
125+
| Correct | Incorrect |
126+
|------|-----|
127+
| `[Set up model workflows](/guide/model-workflows/set-up-model-workflows.qmd)` | `[Learn more ...](/../../set-up-model-workflows.html)` |
128+
: **Inline links** examples {.hover}
129+
130+
#### Buttons
131+
132+
Sometimes, it's helpful to highlight a call to action with a button that takes you to a topic or to a notebook on JupyterHub.
133+
134+
Change any Markdown link into a our theme-styled button by appending `{.button}`:
135+
136+
:::: {.flex .flex-wrap .justify-around}
137+
138+
::: {.w-30-ns}
139+
**Correct:**
140+
141+
[Set up model workflows](/guide/model-workflows/set-up-model-workflows.qmd){.button}
142+
143+
```markdown
144+
[Set up model workflows](/guide/model-workflows/set-up-model-workflows.qmd){.button}
145+
```
146+
147+
::: {.callout}
148+
Using a markdown button also enables you to link to to the `.qmd` path instead of the rendered `.html` file.
149+
:::
150+
151+
:::
152+
153+
::: {.w-60-ns}
154+
**Incorrect:**
155+
156+
<form method="get" action="../../../guide/model-workflows/set-up-model-workflows.html">
157+
<button type="submit" style="color: #de257e; background-color: white; border-radius: 8px; border: none; font-size: 16px; padding: 6.25px 12.5px; margin-left: 16px; margin-bottom: 20px;border: 1px solid #de257e">Set up model workflows</button>
158+
</form>
159+
160+
```html
161+
<form method="get" action="../../../guide/model-workflows/set-up-model-workflows.html">
162+
<button type="submit" style="color: white; background-color: #de257e; border-radius: 8px; border: none; font-size: 16px; padding: 6.25px 12.5px; margin-left: 16px; margin-bottom: 20px;">Set up model workflows</button>
163+
</form>
164+
```
165+
:::
166+
167+
::::
122168

123169
#### Margin footnotes
124170

site/about/overview-model-documentation.qmd

Lines changed: 19 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,16 @@ filters:
55
- tachyons
66
aliases:
77
- ../guide/overview-model-documentation.html
8+
listing:
9+
id: quickstart
10+
type: grid
11+
grid-columns: 2
12+
# image-height: 100%
13+
contents:
14+
- path: ../get-started/quickstart.qmd
15+
title: "QuickStart"
16+
description: "Our QuickStart is the quickest and easiest way to try out our product features."
17+
fields: [title, description, reading-time]
818
---
919

1020
<!---
@@ -15,17 +25,19 @@ Overview & updated graphic
1525
### Closed beta: LLM testing & documentation
1626
--->
1727

18-
The ValidMind Developer Framework streamlines the process of documenting various types of models. The {{< var vm.developer >}} automates the documentation process, ensuring that your model documentation and testing aligns with regulatory and compliance standards.
28+
The {{< var validmind.developer >}} streamlines the process of documenting various types of models. The {{< var vm.developer >}} automates the documentation process, ensuring that your model documentation and testing aligns with regulatory and compliance standards.
1929

2030
::: {.prereq}
2131

2232
## {{< fa code >}} The {{< var validmind.developer >}}
2333

24-
The {{< var validmind.developer >}} is a {{< var vm.developer >}} and documentation engine designed to streamline the process of documenting various types of models, including traditional statistical models, legacy systems, artificial intelligence/machine learning models, and large language models (LLMs). It offers model developers a systematic approach to documenting and testing risk models with repeatability and consistency, ensuring alignment with regulatory and compliance standards.
34+
The {{< var validmind.developer >}} is a {{< var vm.developer >}} and documentation engine designed to streamline the process of documenting various types of models, including traditional statistical models, legacy systems, artificial intelligence/machine learning models, and large language models (LLMs).
35+
36+
It offers model developers a systematic approach to documenting and testing risk models with repeatability and consistency, ensuring alignment with regulatory and compliance standards.
2537

2638
<!-- Using the variable in alt text messes up the image display -->
2739

28-
![](overview-developer-framework.png){width=80% fig-align="center" fig-alt="An image showing the two main components of ValidMind. The developer framework that integrates with your existing developer environment, and the ValidMind AI risk platform."}
40+
![The two main components of ValidMind. The developer framework that integrates with your existing developer environment, and the ValidMind AI risk platform.](overview-developer-framework.png){width=80% fig-align="center" fig-alt="An image showing the two main components of ValidMind. The developer framework that integrates with your existing developer environment, and the ValidMind AI risk platform."}
2941

3042
The {{< var validmind.developer >}} consists of a client-side library, API integration for models and testing, and validation tests that streamline the model development process. Implemented as a series of independent libraries in Python and R, our {{< var vm.developer >}} ensures compatibility and flexibility with diverse sets of developer environments and requirements.
3143

@@ -117,7 +129,7 @@ ValidMind imports the following artifacts into the documentation via our API end
117129
- Output from test and test suites that have been run.
118130
- Images, plots, visuals that were generated as part of extracting metrics and running tests.
119131

120-
![](fine-print/overview-api-integration.png){fig-alt="A representation of artifacts imported into the documentation via our API"}
132+
![Artifacts imported into the documentation via our SaaS API](fine-print/overview-api-integration.png){width=90% fig-alt="A representation of artifacts imported into the documentation via our SaaS API"}
121133

122134
::: {.callout-important title="ValidMind does NOT:"}
123135
- Send any personal identifiable information (PII) when generating documentation reports.
@@ -126,7 +138,9 @@ ValidMind imports the following artifacts into the documentation via our API end
126138

127139
## Ready to try out ValidMind?
128140

129-
Our [QuickStart](/get-started/quickstart.qmd) is the quickest and easiest way to try out our product features.
141+
:::{#quickstart}
142+
:::
143+
130144

131145

132146
<!-- FOOTNOTES -->

site/about/overview-model-risk-management.qmd

Lines changed: 46 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,16 @@ filters:
55
- tachyons
66
aliases:
77
- ../guide/overview-model-risk-management.html
8+
listing:
9+
id: quickstart
10+
type: grid
11+
grid-columns: 2
12+
# image-height: 100%
13+
contents:
14+
- path: ../get-started/quickstart.qmd
15+
title: "QuickStart"
16+
description: "Our QuickStart is the quickest and easiest way to try out our product features."
17+
fields: [title, description, reading-time]
818
---
919

1020
<!---
@@ -26,17 +36,17 @@ The {{< var validmind.platform >}} provides a comprehensive suite of tools, guid
2636

2737
<!-- Using the variable in alt text messes up the image display -->
2838

29-
![](overview-platform-ui.png){width=80% fig-align="center" fig-alt="An image showing the two main components of ValidMind. The developer framework that integrates with your existing developer environment, and the ValidMind AI risk platform."}
39+
![The two main components of ValidMind. The developer framework that integrates with your existing developer environment, and the ValidMind AI risk platform.](overview-platform-ui.png){width=80% fig-align="center" fig-alt="An image showing the two main components of ValidMind. The developer framework that integrates with your existing developer environment, and the ValidMind AI risk platform."}
3040

3141
The {{< var vm.platform >}} employs a multi-tenant architecture, hosting the cloud-based user interface, APIs, databases, and internal services. The design ensures efficient resource utilization and offers a highly scalable solution for organizations of varying sizes.
3242

3343
With the {{< var vm.platform >}}, you can:
3444

35-
- **Track your model inventory** — Manage the model lifecycle, track the workflow status for models, plan for upcoming validation dates, and more.
36-
- **Work on validation initiatives** — Collaborate with developers and validators to review documentation, add findings, keep track of review statuses, and generate validation reports.
37-
- **Configure workflows** — Set up ValidMind to follow your existing model risk management processes, manage statuses for different parts of the workflow, and get an end-to-end view of workflows and who is involved.
38-
- **Use, create, or edit tests, test suites, and templates** — Create and/or configure required validation tests, test suites, and documentation templates for specific model use cases, tailoring it to your own specific needs.
39-
- **Integrate with your stack** — Import and export model documentation and validation reports.
45+
- **Track your model inventory**[^1] — Manage the model lifecycle, track the workflow status for models, plan for upcoming validation dates, and more.
46+
- **Work on validation initiatives**[^2] — Collaborate with developers and validators to review documentation, add findings, keep track of review statuses, and generate validation reports.
47+
- **Configure workflows**[^3] — Set up ValidMind to follow your existing model risk management processes, manage statuses for different parts of the workflow, and get an end-to-end view of workflows and who is involved.
48+
- **Use, create, or edit tests, test suites, and templates**[^4] — Create and/or configure required validation tests, test suites, and documentation templates for specific model use cases, tailoring it to your own specific needs.
49+
- **Integrate with your stack**[^5] — Import and export model documentation and validation reports.
4050

4151
:::
4252

@@ -51,18 +61,21 @@ Examples of regulations or policies include:
5161
::: {.w-75-ns}
5262

5363
### SR 11-7: Guidance on Model Risk Management
54-
The Supervisory Guidance on model risk management issued by the Board of Governors of the Federal Reserve System and the Office of the Comptroller of the Currency in the United States in 2011. It provides comprehensive guidance to financial institutions on developing and maintaining a robust model risk management framework, covering aspects like model development, implementation, use, and validation. SR 11-7 is widely recognized and has become a benchmark in the industry for model risk management practices.
64+
65+
The Supervisory Guidance on model risk management issued by the Board of Governors of the Federal Reserve System and the Office of the Comptroller of the Currency in the United States in 2011. It provides comprehensive guidance to financial institutions on developing and maintaining a robust model risk management framework, covering aspects like model development, implementation, use, and validation.
5566

5667
:::
5768

5869
::: {.w-20-ns .content-center}
5970

60-
![](federal-reserve.svg){width=70% fig-alt="Board of Governers Federal Reserve logo"}
71+
![Board of Governors Federal Reserve logo](federal-reserve.svg){width=70% fig-alt="Board of Governors Federal Reserve logo"}
6172

6273
:::
6374

6475
::::
6576

77+
SR 11-7 is widely recognized and has become a benchmark in the industry for model risk management practices.
78+
6679
SR 11-7 outlines these core requirements:
6780

6881
Model Risk Management
@@ -89,18 +102,22 @@ The regulation also mandates ongoing monitoring and periodic reviews to ensure m
89102

90103
::: {.w-20-ns .content-center}
91104

92-
![](bank-of-england.svg){fig-alt="Bank of England logo"}
105+
![Bank of England logo](bank-of-england.svg){fig-alt="Bank of England logo"}
93106

94107
:::
95108

96109
::: {.w-75-ns}
97110

98111
### SS1/23 – Model Risk Management Principles for Banks
99-
A policy issued by the Prudential Regulation Authority (PRA) in the UK. It encapsulates the final model risk management principles following feedback on the earlier consultation paper CP6/22. The statement provides guidelines for banks in the UK on managing model risk effectively, with particular emphasis on strategic planning and technical capabilities. It outlines principles and amendments, like clarifications on model complexity factors, senior management function responsibilities, and inclusion of dynamic adjustments in model change management, aiming to standardize MRM practices across UK banks and foster the safe adoption of emerging technologies, such as machine learning, artificial intelligence, and large language models (LLMs).
112+
113+
A policy issued by the Prudential Regulation Authority (PRA) in the UK. It encapsulates the final model risk management principles following feedback on the earlier consultation paper CP6/22. The statement provides guidelines for banks in the UK on managing model risk effectively, with particular emphasis on strategic planning and technical capabilities.
114+
100115
:::
101116

102117
::::
103118

119+
It outlines principles and amendments, like clarifications on model complexity factors, senior management function responsibilities, and inclusion of dynamic adjustments in model change management, aiming to standardize MRM practices across UK banks and foster the safe adoption of emerging technologies, such as machine learning, artificial intelligence, and large language models (LLMs).
120+
104121
SS1/23 outlines these core principles:
105122

106123
Model Identification and Model Risk Classification
@@ -163,7 +180,7 @@ ValidMind, as a robust tool for implementing Model Risk Management (MRM) best pr
163180

164181
:::: {.flex .flex-wrap .justify-around}
165182

166-
::: {.w-50-ns}
183+
::: {.w-40-ns}
167184

168185
First line of defense — model developers
169186
: ValidMind offers a suite of tools for model developers, facilitating thorough documentation and rigorous testing of models, aligning with the regulatory expectations of both SR 11-7 and SS1/23, particularly for models under regulatory purview.
@@ -177,14 +194,11 @@ Third line of defense — auditors
177194
Model inventory
178195
: The Model Inventory feature encapsulates a centralized repository for all models, aiding in streamlined tracking, management, and monitoring, simplifying compliance with the inventory mandates specified in SR 11-7 and SS1/23.
179196

180-
Lifecycle management and custom workflows
181-
: ValidMind’s capabilities extend to effective model lifecycle management through configurable workflows. This structured approach to managing model risks across various lifecycle stages significantly aids in meeting the rigorous management and oversight expectations set by SR 11-7 and SS1/23.
182-
183197
:::
184198

185-
::: {.w-40-ns}
186-
187-
![](/assets/img/validmind-demo-compact.png){width=90% fig-alt="An image showing the main ValidMind UI main dashboard"}
199+
::: {.w-50-ns}
200+
Lifecycle management and custom workflows
201+
: ValidMind’s capabilities extend to effective model lifecycle management through configurable workflows. This structured approach to managing model risks across various lifecycle stages significantly aids in meeting the rigorous management and oversight expectations set by SR 11-7 and SS1/23.
188202

189203
Model documentation automation
190204
: By automating model documentation through configurable templates and test plans, ValidMind ensures consistent and accurate documentation capture, directly aligning with the documentation standards stipulated in these regulatory guidelines.
@@ -198,10 +212,22 @@ Communication and tracking
198212

199213
::::
200214

201-
202-
203215
By integrating these features, ValidMind provides a comprehensive platform that not only simplifies the path to compliance with SR 11-7 and SS1/23 but also embeds a culture of rigorous and transparent model risk management within the organization.
204216

205217
## Ready to try out ValidMind?
206218

207-
Our [QuickStart](/get-started/quickstart.qmd) is the quickest and easiest way to try out our product features.
219+
:::{#quickstart}
220+
:::
221+
222+
223+
<!-- FOOTNOTES -->
224+
225+
[^1]: [Working with the model inventory](/guide/model-inventory/working-with-model-inventory.qmd)
226+
227+
[^2]: [Preparing validation reports](/guide/model-validation/preparing-validation-reports.qmd)
228+
229+
[^3]: [Working with model workflows](/guide/model-workflows/working-with-model-workflows.qmd)
230+
231+
[^4]: [Working with documentation templates](/guide/model-documentation/working-with-documentation-templates.qmd)
232+
233+
[^5]: [Export documentation](/guide/model-documentation/export-documentation.qmd)

0 commit comments

Comments
 (0)