diff --git a/README.md b/README.md
index 775542ed9a..d35a5c978f 100644
--- a/README.md
+++ b/README.md
@@ -174,6 +174,19 @@ The script reads from:
Output: Content is injected directly into `site/guide/templates/customize-document-templates.qmd` between marker comments.
+#### Chatbot product map and LLM corpus
+
+The in-app assistant (Valerie) uses generated files under `site/llm/`, including `chatbot-product-map.md` (platform routes mapped to docs URLs and section headings). CI regenerates that map and fails if it is out of date with your changes.
+
+If you edit `.qmd` files that affect linked docs or headings (for example FAQ or guide pages referenced from the product UI), regenerate and commit the map before opening or updating a pull request:
+
+```bash
+cd site
+make generate-chatbot-product-map
+```
+
+If product routes or in-app help links changed, use `make refresh-chatbot-product-map` instead (requires a local `validmind/frontend` checkout). See [`site/llm/README.md`](site/llm/README.md) for the full LLM render pipeline, snapshot maintenance, and when to refresh each artifact.
+
#### Stylesheet organization (IN PROGRESS)
The site uses a modular stylesheet architecture to maintain organized and maintainable styles:
diff --git a/site/_quarto.yml b/site/_quarto.yml
index eba558917b..977562cd82 100644
--- a/site/_quarto.yml
+++ b/site/_quarto.yml
@@ -103,7 +103,7 @@ website:
- text: "Library and platform"
file: about/library-and-platform.qmd
contents:
- - about/overview-model-documentation.qmd
+ - about/overview-documentation.qmd
- about/overview-llm-features.qmd
- text: "Deployment options"
file: about/deployment/deployment-options.qmd
diff --git a/site/about/contributing/style-guide/conventions.qmd b/site/about/contributing/style-guide/conventions.qmd
index b9656e55f7..17fc6e2c78 100644
--- a/site/about/contributing/style-guide/conventions.qmd
+++ b/site/about/contributing/style-guide/conventions.qmd
@@ -125,7 +125,7 @@ Column 2, 50% wide
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.
-Change any Markdown link into a our theme-styled button by appending `{.button}`:
+Change any Markdown link into one of our theme-styled buttons by appending `{.button}`:
:::: {.flex .flex-wrap .justify-around}
@@ -167,8 +167,8 @@ Using a markdown button also enables you to link to to the `.qmd` path instead o
```markdown
- The record is registered in the inventory.[^1]
- - You've already customized your model lifecycle statuses for use in workflows.[^2]
- - Workflows have already been set up for use with your models.[^3]
+ - You've already customized your record stages for use in workflows.[^2]
+ - Workflows have already been set up for use with your records.[^3]
- You are assigned a role that has access to complete actions set up by workflows.[^5]
@@ -344,7 +344,7 @@ Use backticks to enclose keyboard commands, parameters, field values, and file n
| Correct | Incorrect |
|------|-----|
-| Learn how to store model identifier credentials in a `.env` file instead of using inline credentials. | Learn how to store model identifier credentials in a ".env" file instead of using inline credentials. |
+| Learn how to store record identifier credentials in a `.env` file instead of using inline credentials. | Learn how to store record identifier credentials in a ".env" file instead of using inline credentials. |
| For example, the `classifier_full_suite` test suite runs tests from the `tabular_dataset` and `classifier` test suites to fully document the data and model sections for binary classification model use cases. | For example, the "classifier_full_suite" test suite runs tests from the "tabular_dataset" and "classifier" test suites to fully document the data and model sections for binary classification model use cases. |
| Under When these conditions are met, you are able to set both `AND` and `OR` conditions. | Under When these conditions are met, you are able to set both "AND" and "OR" conditions.|
: **Backtick** examples {.hover}
@@ -380,7 +380,7 @@ Within our documentation (`https://docs.validmind.ai/`), you are able to referen
| Product Name | Variable Key | Description |
|---:|---|---|
-| {{< var validmind.product >}} | `{{{< var validmind.product >}}}` | Comphrensive suite of tools with a {{< var vm.developer >}} for documenting and testing models, alongside a {{< var vm.platform >}} hosting cloud-based tools, APIs, databases, and validation engines. |
+| {{< var validmind.product >}} | `{{{< var validmind.product >}}}` | Comprehensive suite of tools with a {{< var vm.developer >}} for documenting and testing records (such as models), alongside a {{< var vm.platform >}} hosting cloud-based tools, APIs, databases, and validation engines. |
| {{< var validmind.developer >}} | `{{{< var validmind.developer >}}}` | Open-source library that connects to the {{< var validmind.platform >}}. |
| {{< var validmind.platform >}} | `{{{< var validmind.platform >}}}` | Hosted multi-tenant architecture that includes a cloud-based web interface. |
| {{< var validmind.api >}} | `{{{< var validmind.api >}}}` | Used to make calls to the {{< var validmind.developer >}}.[^21] |
@@ -438,7 +438,7 @@ From **{{< fa gear >}} Settings** in the {{< var validmind.platform >}},
yo
- Set up your organization
- Onboard new users
- Manage roles, groups and
permissions
-- Configure the model inventory
+- Configure the inventory
- Manage templates and workflows
- And much more!
diff --git a/site/about/contributing/style-guide/voice-and-tone.qmd b/site/about/contributing/style-guide/voice-and-tone.qmd
index 60b20dcbd4..f43495e50b 100644
--- a/site/about/contributing/style-guide/voice-and-tone.qmd
+++ b/site/about/contributing/style-guide/voice-and-tone.qmd
@@ -47,7 +47,7 @@ Behind every page, there’s a person. In every word, lies an opportunity to win
| Correct | Incorrect |
|------|-----|
| **User acknowledgement:** Documenting artifacts can be difficult and tedious for even the most seasoned of validators. | **User dismissal:** For experienced validators, documenting artifacts is a breeze. |
-| **Success toast:** Nice work — you’ve successfully registered your first model! | **Inappropriate humor:** We lost your model documentation, oops! Here, have a pony! (e.g. error message for serious issue) |
+| **Success toast:** Nice work — you’ve successfully registered your first record! | **Inappropriate humor:** We lost your documentation, oops! Here, have a pony! (e.g. error message for serious issue) |
: **Empathy & humor** examples {.hover}
### Be positive
@@ -82,7 +82,7 @@ Address the reader directly by using the second person.
| Correct | Incorrect |
|------|-----|
-| After completing this quickstart, you will be able to view your test results as part of your model documentation right in the {{< var validmind.platform >}}. | After completing this quickstart, the model developer will be able to view the test results as part of the model documentation right in the {{< var validmind.platform >}}. |
+| After completing this quickstart, you will be able to view your test results as part of your documentation right in the {{< var validmind.platform >}}. | After completing this quickstart, the developer will be able to view the test results as part of the documentation right in the {{< var validmind.platform >}}. |
: **2nd person** examples {.hover}
### Avoid stiff formality
@@ -92,7 +92,7 @@ Address the reader directly by using the second person.
| Correct | Incorrect |
|------|-----|
-| Once you’ve registered the model, you can then grab the unique code snippet that will have been generated for you to use in the next step. | First, you must register the model as this will generate a unique code snippet that needs to be copied. Then, you need to retrieve the code snippet so that you can make use of it in the following step. |
+| Once you’ve registered the record, you can then grab the unique code snippet that will have been generated for you to use in the next step. | First, you must register the record as this will generate a unique code snippet that needs to be copied. Then, you need to retrieve the code snippet so that you can make use of it in the following step. |
: **Informal language** examples {.hover}
### Focus on teamwork
diff --git a/site/about/contributing/validmind-community.qmd b/site/about/contributing/validmind-community.qmd
index bc0996e66b..8dc36167ef 100644
--- a/site/about/contributing/validmind-community.qmd
+++ b/site/about/contributing/validmind-community.qmd
@@ -11,7 +11,7 @@ aliases:
- /about/join-community.html
---
-Work with financial models, in model risk management (MRM), or are simply enthusiastic about artificial intelligence (AI) and machine learning and how these tools are actively shaping our futures within the finance industry and beyond? Congratulations — you're already part of the {{< var vm.product >}} community! Come learn and play with us.
+Work with financial models, in model risk management (MRM), in AI governance, or are simply enthusiastic about artificial intelligence (AI) and machine learning and how these tools are actively shaping our futures within the finance industry and beyond? Congratulations — you're already part of the {{< var vm.product >}} community! Come learn and play with us.
::: {.callout}
diff --git a/site/about/deployment/deployment-options.qmd b/site/about/deployment/deployment-options.qmd
index 9dab1db881..acb49defa8 100644
--- a/site/about/deployment/deployment-options.qmd
+++ b/site/about/deployment/deployment-options.qmd
@@ -26,23 +26,23 @@ Choose the {{< var vm.product >}} deployment option that best suits your organiz
{fig-alt="An image showing the ValidMind architecture"}
-In your own environment, model developers can continue to run models using your existing tools for data science and model development, such as Python, Jupyter Notebooks, and R, accessing data from sources such as Google Cloud Storage, Amazon S3, and Snowflake.
+In your own environment, developers can continue to run records (such as models) using your existing tools for data science and development, such as Python, Jupyter Notebooks, and R, accessing data from sources such as Google Cloud Storage, Amazon S3, and Snowflake.
-These models are then integrated with the {{< var validmind.developer >}}, which communicates with the {{< var validmind.platform >}} via our {{< var validmind.api >}}.
+These records are then integrated with the {{< var validmind.developer >}}, which communicates with the {{< var validmind.platform >}} via our {{< var validmind.api >}}.
The {{< var validmind.platform >}} provides:
-- **Model inventory** — Centralized tracking and organization of models, accessible by developers, validators, and executives.
+- **Inventory** — Centralized tracking and organization of records, accessible by developers, validators, and executives.
- **Documentation & validation engine** — Automated testing and documentation, with validation processes, ensuring compliance with regulations and internal policies.
- **Template management** — Allows for easy creation, customization, and reuse of document templates.
-- **{{< var vm.product >}} dashboard** — A user-friendly interface providing insights, status updates, and governance reporting for model risk.
+- **{{< var vm.product >}} dashboard** — A user-friendly interface providing insights, status updates, and governance reporting for risk.
## Security & data privacy
-We ensure data security through strong data isolation, encryption, and role-based access controls.[^1] Personal identifiable information and customer data are not stored in model documentation. For more information, see our data privacy policy.[^2]
+We ensure data security through strong data isolation, encryption, and role-based access controls.[^1] Personal identifiable information and customer data are not stored in documentation. For more information, see our data privacy policy.[^2]
## Secure access
diff --git a/site/about/deployment/system-access-requirements.qmd b/site/about/deployment/system-access-requirements.qmd
index 9e0275968d..37586d99bf 100644
--- a/site/about/deployment/system-access-requirements.qmd
+++ b/site/about/deployment/system-access-requirements.qmd
@@ -10,7 +10,7 @@ Allow list the following domains in your organization’s firewall to ensure you
## ValidMind Library Python API access
-To use our documentation automation tools and test suites for model developers and validators:
+To use our documentation automation tools and test suites for developers and validators:
```html
*.validmind.ai
diff --git a/site/about/fine-print/data-privacy-policy.qmd b/site/about/fine-print/data-privacy-policy.qmd
index 734d2c7f6a..2bb274fdc2 100644
--- a/site/about/fine-print/data-privacy-policy.qmd
+++ b/site/about/fine-print/data-privacy-policy.qmd
@@ -38,16 +38,16 @@ Understanding our policies shouldn’t feel like deciphering code, so we’ve ma
The key points of our data privacy policy include:
-- **No personal identifiable information in documentation** — When the {{< var validmind.developer >}} generates documentation, it ensures that no personally identifiable information (PII) is included. This practice is a critical part of our commitment to protecting your privacy and maintaining the confidentiality of your data.
+- **No personally identifiable information in documentation** — When the {{< var validmind.developer >}} generates documentation, it ensures that no personally identifiable information (PII) is included. This practice is a critical part of our commitment to protecting your privacy and maintaining the confidentiality of your data.
-- **No storage of customer data** — {{< var vm.product >}} does not retain any customer datasets or models. This policy is in place in order to protect your data privacy and security. By not storing this information, {{< var vm.product >}} minimizes the risk of unauthorized access or data breaches.
+- **No storage of customer data** — {{< var vm.product >}} does not retain any customer datasets or records (models). This policy is in place in order to protect your data privacy and security. By not storing this information, {{< var vm.product >}} minimizes the risk of unauthorized access or data breaches.
We believe it is important for users of {{< var vm.product >}}'s products to understand these practices as they reflect our dedication to data security and privacy.
::: {.callout-important}
## {{< var vm.product >}} does NOT:
-- Include any personal identifiable information (PII) when generating documentation reports.
-- Store any customer datasets or models.
+- Include any personally identifiable information (PII) when generating documentation reports.
+- Store any customer datasets or records (models).
:::
## Do you comply with the SOC 2 security standard?
@@ -64,13 +64,13 @@ The {{< var validmind.vpv >}} option provides all our features and services but
Access is available through AWS PrivateLink, Azure Private Link, or GCP Private Service Connect, all of which provide private connectivity between {{< var vm.product >}} and your on-premises network without exposing your traffic to the public internet.
-## What model assets are imported into documentation?
+## What record (model) assets are imported into documentation?
When you generate documentation or run tests, {{< var vm.product >}} imports the following assets into the documentation via our {{< var validmind.api >}} endpoint integration:
{width=80% fig-alt="A representation of assets imported into the documentation via our Python API"}
-- Metadata about datasets and models, used to look up programmatic documentation content, such as the stored definition for _common logistic regression limitations_ when a logistic regression model has been passed to the {{< var vm.product >}} test suite to be run.
+- Metadata about datasets and records, used to look up programmatic documentation content, such as the stored definition for _common logistic regression limitations_ when a logistic regression model has been passed to the {{< var vm.product >}} test suite to be run.
- Quality and performance metrics collected from datasets and models.
- Output from tests and test suites that have been run.
- Images, plots, visuals that were generated as part of extracting metrics and running tests.
diff --git a/site/about/glossary/_ai-governance.qmd b/site/about/glossary/_ai-governance.qmd
new file mode 100644
index 0000000000..4b9324e7c6
--- /dev/null
+++ b/site/about/glossary/_ai-governance.qmd
@@ -0,0 +1,42 @@
+
+
+AI ethics
+: A set of principles and practices guiding the responsible design, development, and deployment of AI systems. Common tenets include fairness, transparency, accountability, privacy, and human well-being.
+
+AI lifecycle
+: The end-to-end stages an AI system progresses through, including problem framing, data collection, model development, validation, deployment, monitoring, and retirement. Each stage carries distinct governance requirements.
+
+AI risk
+: The potential for adverse outcomes — financial, reputational, ethical, regulatory, or societal — arising from the design, deployment, or use of AI systems. AI risk extends beyond traditional model risk to include concerns such as bias, opacity, misuse, and unintended consequences.
+
+algorithmic accountability
+: The principle that organizations must take responsibility for the outcomes of the AI systems they deploy, including documenting decisions, monitoring performance, and providing mechanisms to identify and remediate harm.
+
+bias, algorithmic bias
+: Systematic errors or unfair outcomes in AI system results that disproportionately affect specific groups. Sources include unrepresentative training data, flawed assumptions in system design, or feedback loops introduced during deployment. Detecting and mitigating bias is a core AI governance activity.
+
+EU AI Act
+: A regulatory framework introduced by the European Union that classifies AI systems by risk tier^[**European Union:** [Regulation (EU) 2024/1689: Artificial Intelligence Act](https://eur-lex.europa.eu/eli/reg/2024/1689/oj)] — prohibited, high-risk, limited-risk, and minimal-risk — and imposes proportionate obligations such as risk management, data governance, transparency, human oversight, and conformity assessment.
+
+explainability
+: The degree to which the internal mechanics or outputs of an AI system can be understood by humans. Explainability is a core requirement for high-risk AI systems and supports accountability, debugging, and regulatory review.
+
+fairness
+: The principle that AI systems should produce equitable outcomes across individuals and groups. Fairness assessments are a routine part of bias evaluation and impact assessment within AI governance programs.
+
+ISO/IEC 42001
+: An international management system standard for artificial intelligence published by the International Organization for Standardization. Provides requirements for establishing, implementing, maintaining, and continually improving an AI management system within an organization.
+
+model card, system card
+: A standardized document that summarizes an AI system's intended use, training data, performance characteristics, limitations, and ethical considerations. Model and system cards support transparency and informed deployment decisions.^[**Refer also to:** [documentation](#documentation)]
+
+NIST AI Risk Management Framework (AI RMF)
+: A voluntary framework published by the U.S. National Institute of Standards and Technology to help organizations manage risks associated with AI. Organized around four core functions: govern, map, measure, and manage.
+
+responsible AI
+: An umbrella approach to designing, building, and deploying AI systems in ways that are ethical, transparent, accountable, fair, and aligned with human values and societal expectations.
+
+transparency
+: The disclosure of meaningful information about an AI system's design, data, capabilities, limitations, and decision-making processes to relevant stakeholders. Transparency supports trust, accountability, and informed oversight.
diff --git a/site/about/glossary/_ai.qmd b/site/about/glossary/_ai.qmd
index 5ef7bba2ff..b2b90b0106 100644
--- a/site/about/glossary/_ai.qmd
+++ b/site/about/glossary/_ai.qmd
@@ -5,40 +5,48 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
Refer to [IBM's series on artificial intelligence](https://www.ibm.com/think/artificial-intelligence) for more in-depth resources.
AI governance
-: The organizational framework for directing and overseeing how AI is designed, deployed, and used. It sets policy, accountability, and decision rights, covering ethics, compliance, risk appetite, lifecycle controls, and ongoing oversight across people, process, and technology.
+: The organizational framework for directing and overseeing how AI is designed, deployed, and used. It sets policy, accountability, and decision rights, covering ethics, compliance, risk appetite, lifecycle controls, and ongoing oversight across people, process, and technology.^[**Refer also to:** [AI governance](#ai-governance)]
AI system
-: A combination of software, algorithms, and data designed to perform tasks that typically require human intelligence. In AI governance, an AI system is the primary unit of management, distinct from individual models.
+: A combination of software, algorithms, and data designed to perform tasks that typically require human intelligence. In AI governance, an AI system is the primary unit of management, distinct from individual records (such as models).[^ai-system]
AI use case
: A specific application or deployment of AI technology to solve a business problem or achieve an objective. Use cases are often the unit of oversight in AI governance frameworks.
artificial intelligence (AI)
-: Artificial intelligence is a broad term used to classify machines that mimic human intelligence and human cognitive functions like problem-solving and learning.
+: Artificial intelligence is a broad term used to classify machines that mimic human intelligence and human cognitive functions like problem-solving and learning.
deep-learning
-: A subset of machine learning that uses multi-layered neural networks (deep neural networks) to simulate the complex decision-making power of the human brain.
+: A subset of machine learning that uses multi-layered neural networks (deep neural networks) to simulate the complex decision-making power of the human brain.
generative AI (GenAI)
: Generative AI refers to deep-learning models that can generate high-quality text, images, and other content based on the data they were trained on.
human oversight
-: Controls and processes ensuring human involvement in AI-driven decisions. Required by regulations like the EU AI Act for high-risk AI systems to enable human intervention and override capabilities.
+: Controls and processes ensuring human involvement in AI-driven decisions. Required by regulations like the EU AI Act for high-risk AI systems to enable human intervention and override capabilities.^[**Refer also to:** [EU AI Act](./glossary.qmd#eu-ai-act)]
impact assessment
: An evaluation of the potential risks, harms, and consequences associated with deploying an AI system. Impact assessments are a core artifact in AI governance programs.
large language model (LLM)
-: Advanced types of artificial intelligence models designed to understand, generate, and interact with human language at a sophisticated level, such as ChatGPT.^[[ChatGPT](https://chat.openai.com)]
+: An advanced type of artificial intelligence model designed to understand, generate, and interact with human language at a sophisticated level, such as ChatGPT.^[[ChatGPT](https://chat.openai.com)]
-machine learning
-: Machine learning is a subset of artificial intelligence that allows for optimization. It helps make predictions that minimize the errors that arise from merely guessing.
+machine learning (ML)
+: Machine learning is a subset of artificial intelligence that allows for optimization. It helps make predictions that minimize the errors that arise from merely guessing.
risk tier
-: A classification level assigned to an AI system based on its potential impact and risk. The EU AI Act defines tiers including prohibited, high-risk, limited-risk, and minimal-risk categories.
+: A classification level assigned to an AI system based on its potential impact and risk. The EU AI Act defines tiers including prohibited, high-risk, limited-risk, and minimal-risk categories.^[**Refer also to:** [EU AI Act](./glossary.qmd#eu-ai-act)]
-traditional statistical models
-: Mathematical frameworks used to analyze and make inferences from data. These models are foundational in statistics and serve to explain relationships, predict outcomes, and guide decision-making across various fields, such as economics, biology, engineering, and social sciences.
+traditional statistical model
+: A mathematical framework used to analyze and make inferences from data. Traditional statistical models are foundational in statistics and serve to explain relationships, predict outcomes, and guide decision-making across various fields, such as economics, biology, engineering, and social sciences.
use case owner
: The individual accountable for an AI use case within an organization. Responsible for decisions about AI deployment, compliance, and ongoing oversight.
+
+
+
+
+[^ai-system]: **Refer to:**
+
+ - [record](#records)
+ - [model](#models)
diff --git a/site/about/glossary/_attestation.qmd b/site/about/glossary/_attestation.qmd
index 2ca29bdacf..75271ae84e 100644
--- a/site/about/glossary/_attestation.qmd
+++ b/site/about/glossary/_attestation.qmd
@@ -2,29 +2,29 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-attestation
-: A formal process where attestation participants certify key model information at a specific time. Attestation is part of your audit trail and confirms that governance, documentation, and control requirements are met.
+attestation
+: A formal process where attestation participants certify key record (model) information at a specific time. Attestation is part of your audit trail and confirms that governance, documentation, and control requirements are met.
attestation instance
-: The invocation of the attestation process on the {{< var validmind.platform >}}. Created when the attestation is triggered by the schedule you set up, it includes a snapshot with record activity and artifacts, questionnaire responses and review status, forming a full record of the review and approval process.
+: The invocation of the attestation process on the {{< var validmind.platform >}}. Created when the attestation is triggered by the schedule you set up, it includes a snapshot with record activity and artifacts, questionnaire responses and review status, forming a full record of the review and approval process.
attestation participant
-: A user who participates in the attestation workflow as a submitter, reviewer, or approver. Submitters are assigned from model stakeholders; reviewers and approvers are assigned from organizational roles.
+: A user who participates in the attestation workflow as a submitter, reviewer, or approver. Submitters are assigned from inventory record stakeholders; reviewers and approvers are assigned from organizational roles.
-attestation period
-: The time window during which attestation is active, with fixed start and end dates. Each period creates an unchanging model snapshot. Periods are usually scheduled quarterly or annually and can align with regulatory or internal cycles.
+attestation period
+: The time window during which attestation is active, with fixed start and end dates. Each period creates an unchanging record (model) snapshot. Periods are usually scheduled quarterly or annually and can align with regulatory or internal cycles.
-attestation questionnaire
-: A structured form that submitters use to confirm model status, documentation and compliance. It supports formatted inputs like checkboxes and text fields, serving as both a compliance check and formal review record.
+attestation questionnaire
+: A structured form that submitters use to confirm record (model) status, documentation and compliance. It supports formatted inputs like checkboxes and text fields, serving as both a compliance check and formal review record.
-execution schedule
+execution schedule
: The mechanism, manual or automated, that starts the attestation process based on set periods. It creates attestation instances, triggers snapshots and begins the workflow for attestation participants.
group
-: An organizational unit that associates models with specific teams or functions. When reviewers or approvers are assigned by role, they can only act on models within groups they belong to — resulting in one attestation submission per model owner per group.
+: An organizational unit that associates records (models) with specific teams or functions. When reviewers or approvers are assigned by role, they can only act on records within groups they belong to — resulting in one attestation submission per owner per group.
inventory scope
-: The filter conditions that define which models are included in an attestation. Scope can be set using rules based on model fields, stages, or custom attributes.
+: The filter conditions that define which records (models) are included in an attestation. Scope can be set using rules based on fields, stages, or custom attributes.
-snapshot
-: A fixed capture of model data at a specific time. It includes optional custom fields and related artifacts and stays unchanged throughout the attestation, ensuring historical accuracy.
\ No newline at end of file
+snapshot
+: A fixed capture of record (model) data at a specific time. It includes optional custom fields and related artifacts and stays unchanged throughout the attestation, ensuring historical accuracy.
\ No newline at end of file
diff --git a/site/about/glossary/_developer-tools.qmd b/site/about/glossary/_developer-tools.qmd
index 0381ba6ff1..9dd5cb07bd 100644
--- a/site/about/glossary/_developer-tools.qmd
+++ b/site/about/glossary/_developer-tools.qmd
@@ -14,9 +14,9 @@ Decorators are a simpler way for users to run their own code as a {{< var vm.pro
{{< include key_concepts/_parameters.qmd >}}
pip
-: A package manager for Python, used to install and manage software packages written in the Python programming language.
+: A package manager for Python, used to install and manage software packages written in the Python programming language.
-{{< var vm.product >}} uses the `pip` command to install the Python client library that is part of the {{< var validmind.developer >}} so that model developers can make use of its features.
+{{< var vm.product >}} uses the `pip` command to install the Python client library that is part of the {{< var validmind.developer >}} so that developers can make use of its features.
JupyterHub
: A multi-user server provides a platform for users to interactively work with data science and scientific computing tools in a collaborative environment.
@@ -33,4 +33,4 @@ Jupyter Notebook
GitHub
: A cloud-based platform that provides hosting for software development and version control using Git. GitHub^[[GitHub](https://github.com/)] offers collaboration tools such as bug tracking, feature requests, task management, and continuous integration pipelines.
-{{< var vm.product >}} uses GitHub to share [pen-source software^[**GitHub:** [validmind](https://github.com/validmind/)] with you.
+{{< var vm.product >}} uses GitHub to share open-source software^[**GitHub:** [validmind](https://github.com/validmind/)] with you.
diff --git a/site/about/glossary/_documentation.qmd b/site/about/glossary/_documentation.qmd
new file mode 100644
index 0000000000..fc4a038cd3
--- /dev/null
+++ b/site/about/glossary/_documentation.qmd
@@ -0,0 +1,23 @@
+
+
+
+
+{{< include documentation/_doc-intro.qmd >}}
+
+{{< include documentation/_conceptual-soundness.qmd >}}
+
+{{< include documentation/_data-preparation.qmd >}}
+
+{{< include documentation/_model-development.qmd >}}
+
+{{< include documentation/_monitoring-governance.qmd >}}
+
diff --git a/site/about/glossary/_model-documentation.qmd b/site/about/glossary/_model-documentation.qmd
deleted file mode 100644
index b0c983236b..0000000000
--- a/site/about/glossary/_model-documentation.qmd
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
-
-{{< include model_documentation/_doc-intro.qmd >}}
-
-{{< include model_documentation/_conceptual-soundness.qmd >}}
-
-{{< include model_documentation/_data-preparation.qmd >}}
-
-{{< include model_documentation/_model-development.qmd >}}
-
-{{< include model_documentation/_monitoring-governance.qmd >}}
-
diff --git a/site/about/glossary/_models.qmd b/site/about/glossary/_models.qmd
index b3a72d4e68..8c9ce74f80 100644
--- a/site/about/glossary/_models.qmd
+++ b/site/about/glossary/_models.qmd
@@ -4,14 +4,13 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
#### Models
-model
-: Under SR 26-2^[[SR 26-2: Interagency Guidance on Model Risk Management for Banking Organizations](https://www.federalreserve.gov/supervisionreg/srletters/SR2602.htm)] (which supersedes SR 11-7), banking organizations focus MRM on *complex quantitative methods* that apply statistical, economic, or financial theories, techniques, and assumptions to produce estimates or inferences that inform business decisions. Simple arithmetic, purely deterministic rules without substantive quantitative theory, or software that does not apply such theories are generally outside the guidance’s model definition.
+{{< include /about/glossary/key_concepts/_docs.qmd >}}
+
+{{< include /about/glossary/key_concepts/_models.qmd >}}
model development
: An iterative process in which many models are derived, tested, and built upon until a model fitting the desired criteria is achieved.
-{{< include key_concepts/_docs.qmd >}}
-
:::: {.content-visible when-format="html" when-meta="includes.glossary"}
-model inventory^[**Refer also to:** [{{< var vm.product >}} model inventory](./glossary.qmd#platform-model-inventory)]
+model inventory^[**Refer also to:** [inventory](./glossary.qmd#inventory)]
: A systematic and organized record of all quantitative and qualitative models used within an organization. This inventory facilitates oversight, tracking, and assessment by listing each model's purpose, characteristics, owners, validation status, and associated risks.
::::
diff --git a/site/about/glossary/_mrm.qmd b/site/about/glossary/_mrm.qmd
index 4872d9f341..31835071a4 100644
--- a/site/about/glossary/_mrm.qmd
+++ b/site/about/glossary/_mrm.qmd
@@ -13,27 +13,27 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
3rd line of defense
: Typically an internal audit function responsible for providing an independent and comprehensive review of the risk management processes and controls that the first two lines have implemented.
-model developer
+model developer, developer
: Responsible for the design, implementation, and maintenance of models to ensure they are fit-for-purpose, accurate, and aligned with business requirements. As subject matter experts, they collaborate with model validators and other business units, ensuring the models are conceptually sound and robust.
-model governance
+model governance, governance
: A framework of policies, procedures, and standards established to oversee the lifecycle of models within an organization. Ensures that models are developed, validated, implemented, and retired in a controlled and consistent manner, promoting accountability, transparency, and adherence to regulatory requirements.
-model implementation
+model implementation, implementation
: A collaborative effort among model developers and model owners. Model implementation includes a formalized implementation plan and associated procedures, a review of results, and a record of model change procedures.
-model owner
+model owner, owner
: Responsible for coordinating model development, model implementation, ongoing model monitoring and maintaining the model’s administration, such as model documentation and model risk reporting.
-model user
+model user, user
: Those who rely on the model’s outputs to inform business decisions.
-model validation
+model validation, validation
: A systematic process to evaluate and verify that a model is performing as intended, accurately represents the phenomena it is designed to capture, and is appropriate for its specified purpose. This assessment encompasses a review of the model's conceptual soundness, data integrity, calibration, and performance outcomes, as well as testing against out-of-sample datasets.
Within model risk management, model validation ensures that potential risks associated with model errors, misuse, or misunderstanding are identified and mitigated.
-model validator
+model validator, validator
: Responsible for conducting independent assessments of models to ensure their accuracy, reliability, and appropriateness for intended purposes. The role involves evaluating a model's conceptual soundness, data integrity, calibration methods, and overall performance, typically using out-of-sample datasets.
Model validators identify potential risks and weaknesses, ensuring that models within an organization meet established standards and regulatory requirements, and provide recommendations to model developers for improvements or modifications.
diff --git a/site/about/glossary/_validmind-features.qmd b/site/about/glossary/_validmind-features.qmd
index 2be12d5923..4d3cc46369 100644
--- a/site/about/glossary/_validmind-features.qmd
+++ b/site/about/glossary/_validmind-features.qmd
@@ -8,16 +8,26 @@ client library, Python client library
: Enables the interaction of your development environment with the {{< var validmind.platform >}} as part of the {{< var validmind.developer >}}.
content block
-: Content blocks provide you with sections that are part of a template, and are used in model documentation, validation reports, ongoing monitoring reports, and custom document types.^[[Work with content blocks](/guide/documentation/work-with-content-blocks.qmd)]
+: A modular document template component. Content blocks are used to populate text and test results in documentation, validation reports, ongoing monitoring reports, and custom document types.^[[Work with content blocks](/guide/documentation/work-with-content-blocks.qmd)]
documentation automation
-: A core benefit of {{< var vm.product >}} that allows for the automatic creation of model documentation using predefined templates and test suites.
+: A core benefit of {{< var vm.product >}} that allows for the automatic creation of documentation using predefined templates and test suites.[^test-suite]
-model inventory
-: A feature of the {{< var validmind.platform >}} where you can track, manage, and oversee the lifecycle of models. Covers the full model lifecycle, including customizable approval workflows for different user roles, status and activity tracking, and periodic revalidation.
+inventory
+: A feature of the {{< var validmind.platform >}} where you can track, manage, and oversee the lifecycle of your records (such as models). Covers the full record lifecycle, including customizable approval workflows for different user roles, status and activity tracking, and periodic revalidation.
+
+{{< include key_concepts/_records.qmd >}}
{{< include key_concepts/_template.qmd >}}
{{< include key_concepts/_test.qmd >}}
-{{< include key_concepts/_test-suite.qmd >}}
\ No newline at end of file
+{{< include key_concepts/_test-suite.qmd >}}
+
+
+
+
+[^test-suite]: **Refer to:**
+
+ - [document template](/about/glossary/glossary.qmd#document-template)
+ - [test suite](/about/glossary/glossary.qmd#test-suite)
\ No newline at end of file
diff --git a/site/about/glossary/_validmind.qmd b/site/about/glossary/_validmind.qmd
index fcba5f96cc..b9d29c8ff5 100644
--- a/site/about/glossary/_validmind.qmd
+++ b/site/about/glossary/_validmind.qmd
@@ -4,10 +4,10 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
#### {{< var validmind.product >}}
-These two features are intertwined and work in tandem to help streamline your model lifecycle.
+These two features are intertwined and work in tandem to help streamline your risk management lifecycles.
{{< var validmind.developer >}} ({{< var vm.developer >}})
-: An open-source^[**{{< var vm.product >}} GitHub:** [`validmind-library`](https://github.com/validmind/validmind-library/)] suite of documentation tools and test suites designed to document models, test models for weaknesses, and identify overfit areas. Enables automating the generation of model documentation by uploading documentation and test results to the {{< var validmind.platform >}}.
+: An open-source^[**{{< var vm.product >}} GitHub:** [`validmind-library`](https://github.com/validmind/validmind-library/)] suite of documentation tools and test suites designed to document records (such as models), test records for weaknesses, and identify overfit areas. Enables automating the generation of documentation by uploading documentation and test results to the {{< var validmind.platform >}}.
{{< var validmind.platform >}} ({{< var vm.platform >}})
-: A hosted multi-tenant architecture^[[Log into {{< var vm.product >}}](/guide/access/log-in-to-validmind.qmd)] that includes the {{< var vm.product >}} cloud-based web interface, APIs, databases, documentation and validation engine, and various internal services.
+: A hosted multi-tenant architecture^[[Log into {{< var vm.product >}}](/guide/access/log-in-to-validmind.qmd)] that includes the {{< var vm.product >}} cloud-based web interface, APIs, databases, documentation and validation engine, and various internal services.
diff --git a/site/about/glossary/documentation/_conceptual-soundness.qmd b/site/about/glossary/documentation/_conceptual-soundness.qmd
new file mode 100644
index 0000000000..1dae64104f
--- /dev/null
+++ b/site/about/glossary/documentation/_conceptual-soundness.qmd
@@ -0,0 +1,6 @@
+
+
+conceptual soundness
+: Establishes the foundation of a selected record (such as a model), covering the overview, intended use and business use case, regulatory requirements, limitations, and the rationale behind selection. It emphasizes purpose, scope, and constraints, which are crucial for stakeholders to understand applicability and limitations.
diff --git a/site/about/glossary/model_documentation/_data-preparation.qmd b/site/about/glossary/documentation/_data-preparation.qmd
similarity index 88%
rename from site/about/glossary/model_documentation/_data-preparation.qmd
rename to site/about/glossary/documentation/_data-preparation.qmd
index 9a5b539e85..84646b6c75 100644
--- a/site/about/glossary/model_documentation/_data-preparation.qmd
+++ b/site/about/glossary/documentation/_data-preparation.qmd
@@ -3,4 +3,4 @@ Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
data preparation
-: Details the data description, including dataset summary, data quality tests, descriptive statistics, correlations and interactions, and feature selection and engineering. It provides transparency into the data used for training, ensuring that the record such as a model is built on a solid and relevant dataset.
\ No newline at end of file
+: Details the data description, including dataset summary, data quality tests, descriptive statistics, correlations and interactions, and feature selection and engineering. It provides transparency into the data used for training, ensuring that the record (such as a model) is built on a solid and relevant dataset.
\ No newline at end of file
diff --git a/site/about/glossary/model_documentation/_doc-intro.qmd b/site/about/glossary/documentation/_doc-intro.qmd
similarity index 100%
rename from site/about/glossary/model_documentation/_doc-intro.qmd
rename to site/about/glossary/documentation/_doc-intro.qmd
diff --git a/site/about/glossary/model_documentation/_model-development.qmd b/site/about/glossary/documentation/_model-development.qmd
similarity index 81%
rename from site/about/glossary/model_documentation/_model-development.qmd
rename to site/about/glossary/documentation/_model-development.qmd
index 5acf1242eb..1c7eafc727 100644
--- a/site/about/glossary/model_documentation/_model-development.qmd
+++ b/site/about/glossary/documentation/_model-development.qmd
@@ -3,4 +3,4 @@ Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
model development, development
-: Discusses the training, evaluation, explainability, interpretability, and diagnosis, including weak spots, overfit regions, and robustness. This section is vital for understanding how the record such as a model was developed, how it performs, and its areas of strength and weakness.
+: Discusses the training, evaluation, explainability, interpretability, and diagnosis, including weak spots, overfit regions, and robustness. This section is vital for understanding how the record (such as a model) was developed, how it performs, and its areas of strength and weakness.
diff --git a/site/about/glossary/documentation/_monitoring-governance.qmd b/site/about/glossary/documentation/_monitoring-governance.qmd
new file mode 100644
index 0000000000..05ccf5390e
--- /dev/null
+++ b/site/about/glossary/documentation/_monitoring-governance.qmd
@@ -0,0 +1,6 @@
+
+
+monitoring and governance
+: Focuses on the record (such as a model)’s ongoing monitoring plan, implementation, and governance plan. It outlines strategies for maintaining the performance over time and ensuring that it remains compliant with regulatory requirements and ethical standards.
\ No newline at end of file
diff --git a/site/about/glossary/glossary.qmd b/site/about/glossary/glossary.qmd
index cbf0c8ab03..43167cf368 100644
--- a/site/about/glossary/glossary.qmd
+++ b/site/about/glossary/glossary.qmd
@@ -17,32 +17,39 @@ includes:
This glossary of terms provides short definitions for technical terms you find commonly used in our product documentation grouped by terms related to:
- [{{< var vm.product >}}](#validmind)
-- [Artificial intelligence](#artificial-intelligence)
-- [Models and model risk management](#models-and-model-risk-management)
-- [Model documentation](#model-documentation)
+- [Artificial intelligence (AI) governance](#artificial-intelligence-ai-governance)
+- [Model risk management](#model-risk-management)
+- [Documentation](#documentation)
- [Validation reports](#validation-reports)
- [Ongoing monitoring](#ongoing-monitoring)
- [Attestations](#attestations)
- [Integrations](#integrations)
- [Developer tools](#developer-tools)
+
## {{< var vm.product >}}
{{< include _validmind.qmd >}}
{{< include _validmind-features.qmd >}}
-## Artificial intelligence
+## Artificial intelligence (AI) governance
+
+#### AI
{{< include _ai.qmd >}}
-## Models and model risk management
+#### AI governance
+
+{{< include _ai-governance.qmd >}}
+
+## Model risk management
{{< include _models.qmd >}}
{{< include _mrm.qmd >}}
-## Model documentation
+## Documentation
-{{< include _model-documentation.qmd >}}
+{{< include _documentation.qmd >}}
## Validation reports
diff --git a/site/about/glossary/key_concepts/_docs.qmd b/site/about/glossary/key_concepts/_docs.qmd
index 0ff2fa8d76..886d9f2f20 100644
--- a/site/about/glossary/key_concepts/_docs.qmd
+++ b/site/about/glossary/key_concepts/_docs.qmd
@@ -2,7 +2,12 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-model documentation
-: A structured and detailed record pertaining to a model, encompassing key components such as its underlying assumptions, methodologies, data sources, inputs, performance metrics, evaluations, limitations, and intended uses.
-
-Within the realm of model risk management, this documentation serves to ensure transparency, adherence to regulatory requirements, and a clear understanding of potential risks associated with the model's application.
\ No newline at end of file
+
+
+documentation, model documentation
+: A structured and detailed record pertaining to a record (such as a model), encompassing key components such as its underlying assumptions, methodologies, data sources, inputs, performance metrics, evaluations, limitations, and intended uses.
+
+:::: {.content-visible when-format="html" when-meta="includes.glossary"}
+Within the realm of risk management, this documentation serves to ensure transparency, adherence to regulatory requirements, and a clear understanding of potential risks associated with the record's application.
+
+::::
\ No newline at end of file
diff --git a/site/about/glossary/key_concepts/_inputs.qmd b/site/about/glossary/key_concepts/_inputs.qmd
index 0c45358b5e..bc148ade75 100644
--- a/site/about/glossary/key_concepts/_inputs.qmd
+++ b/site/about/glossary/key_concepts/_inputs.qmd
@@ -5,7 +5,19 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
inputs
: Objects to be evaluated and documented in the {{< var validmind.developer >}}. They can be any of the following:
- - **model**: A single model that has been initialized in {{< var vm.product >}}. Refer to the [`vm.init_model()` function](/validmind/validmind.qmd#init_model){target="_blank"} for more information.
- - **dataset**: Single dataset that has been initialized in {{< var vm.product >}}. Refer to the [`vm.init_dataset()` function](/validmind/validmind.qmd#init_dataset){target="_blank"} for more information.
- - **models**: A list of {{< var vm.product >}} models - usually this is used when you want to compare multiple models in your custom tests.
- - **datasets**: A list of {{< var vm.product >}} datasets - usually this is used when you want to compare multiple datasets in your custom tests. (Learn more: [Run tests with multiple datasets](/notebooks/how_to/tests/run_tests/configure_tests/run_tests_that_require_multiple_datasets.ipynb))
\ No newline at end of file
+:::: {.content-visible when-format="html" when-meta="includes.glossary"}
+ - **model**: A single record (such as a model) that has been initialized in {{< var vm.product >}}. Despite the naming convention, model objects can be any type of record you want to test, document, validate, or monitor with {{< var vm.product >}}.^[**Refer to:** [`init_model()`](/validmind/validmind.qmd#init_model){target="_blank"}]
+ - **dataset**: A single dataset that has been initialized in {{< var vm.product >}}.^[**Refer to:** [`init_dataset()`](/validmind/validmind.qmd#init_dataset){target="_blank"}]
+ - **models**: A list of {{< var vm.product >}} records — usually this is used when you want to compare multiple records in your custom tests.
+ - **datasets**: A list of {{< var vm.product >}} datasets — usually this is used when you want to compare multiple datasets in your custom tests.^[**Learn more:** [Run tests with multiple datasets](/notebooks/how_to/tests/run_tests/configure_tests/run_tests_that_require_multiple_datasets.ipynb)]
+
+::::
+
+:::: {.content-visible when-format="html" unless-meta="includes.glossary"}
+ - **model**: A single record (such as a model) that has been initialized in {{< var vm.product >}}. Despite the naming convention, model objects can be any type of record you want to test, document, validate, or monitor with {{< var vm.product >}}. Refer to the [`vm.init_model()` function](/validmind/validmind.qmd#init_model){target="_blank"} for more information.
+ - **dataset**: A single dataset that has been initialized in {{< var vm.product >}}. Refer to the [`vm.init_dataset()` function](/validmind/validmind.qmd#init_dataset){target="_blank"} for more information.
+ - **models**: A list of {{< var vm.product >}} records — usually this is used when you want to compare multiple records in your custom tests.
+ - **datasets**: A list of {{< var vm.product >}} datasets — usually this is used when you want to compare multiple datasets in your custom tests. (Learn more: [Run tests with multiple datasets](/notebooks/how_to/tests/run_tests/configure_tests/run_tests_that_require_multiple_datasets.ipynb))
+
+::::
+
diff --git a/site/about/glossary/key_concepts/_key-concepts.qmd b/site/about/glossary/key_concepts/_key-concepts.qmd
index 4e2fe9c64d..73a4f68bab 100644
--- a/site/about/glossary/key_concepts/_key-concepts.qmd
+++ b/site/about/glossary/key_concepts/_key-concepts.qmd
@@ -6,20 +6,28 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
1. Create a new file under the `about/glossary/key_concepts` folder with the following structure `_concept.qmd` (the `_` is mandatory for Quarto to retrieve the file as a single-source embed: https://quarto.org/docs/authoring/includes.html)
2. Include it below with the structure `{{< include /about/glossary/key_concepts/_concept.qmd >}}`
-3. In the `about/glossary` folder, locate the correct section file it belongs to (e.g. `_ai.qmd`) and embed it there as well in ABC order with the structure `{{< include key_concepts/_concept.qmd >}}`
+3. In the `about/glossary` folder, locate the correct section file it belongs to (e.g. `_ai.qmd`) and embed it there as well in ABC order with the structure `{{< include key_concepts/_concept.qmd >}}`
These instructions update the key concept on anywhere the key concepts are reference as well as within the glossary.
-->
+{{< include /about/glossary/key_concepts/_records.qmd >}}
+
+{{< include /about/glossary/key_concepts/_models.qmd >}}
+
{{< include /about/glossary/key_concepts/_docs.qmd >}}
{{< include /about/glossary/key_concepts/_report.qmd >}}
+{{< include /about/glossary/monitoring/_ongoing-monitoring.qmd >}}
+
{{< include /about/glossary/key_concepts/_template.qmd >}}
{{< include /about/glossary/key_concepts/_test.qmd >}}
+{{< include /about/glossary/key_concepts/_test-suite.qmd >}}
+
{{< include /about/glossary/key_concepts/_metrics.qmd >}}
{{< include /about/glossary/key_concepts/_inputs.qmd >}}
@@ -28,4 +36,3 @@ These instructions update the key concept on anywhere the key concepts are refer
{{< include /about/glossary/key_concepts/_outputs.qmd >}}
-{{< include /about/glossary/key_concepts/_test-suite.qmd >}}
\ No newline at end of file
diff --git a/site/about/glossary/key_concepts/_metrics.qmd b/site/about/glossary/key_concepts/_metrics.qmd
index 53dd1223f7..d95bb3588d 100644
--- a/site/about/glossary/key_concepts/_metrics.qmd
+++ b/site/about/glossary/key_concepts/_metrics.qmd
@@ -2,7 +2,16 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
+:::: {.content-visible when-format="html" when-meta="includes.glossary"}
metrics, custom metrics
-: Metrics are a subset of tests that do not have thresholds. Custom metrics are functions that you define to evaluate your model or dataset. These functions can be registered via the {{< var validmind.developer >}} to be used with the {{< var validmind.platform >}}.
+: Metrics are a subset of tests that do not have thresholds. Custom metrics are functions that you define to evaluate your record (such as a model) or dataset. These functions can be registered via the {{< var validmind.developer >}} to be used with the {{< var validmind.platform >}}.
-In the context of {{< var vm.product >}}'s Jupyter Notebooks, metrics and tests can be thought of as interchangeable concepts.
\ No newline at end of file
+In the context of {{< var vm.product >}}'s Jupyter Notebooks, metrics and tests can be thought of as interchangeable concepts.^[**Refer also to:** [test](/about/glossary/glossary.qmd#tests)]
+::::
+
+:::: {.content-visible when-format="html" unless-meta="includes.glossary"}
+metrics, custom metrics
+: Metrics are a subset of tests that do not have thresholds. Custom metrics are functions that you define to evaluate your record (such as a model) or dataset. These functions can be registered via the {{< var validmind.developer >}} to be used with the {{< var validmind.platform >}}.
+
+In the context of {{< var vm.product >}}'s Jupyter Notebooks, metrics and tests can be thought of as interchangeable concepts.
+::::
\ No newline at end of file
diff --git a/site/about/glossary/key_concepts/_models.qmd b/site/about/glossary/key_concepts/_models.qmd
new file mode 100644
index 0000000000..15bdf932df
--- /dev/null
+++ b/site/about/glossary/key_concepts/_models.qmd
@@ -0,0 +1,17 @@
+
+
+:::: {.content-visible when-format="html" when-meta="includes.glossary"}
+model
+: SR 26-2^[[SR 26-2: Interagency Guidance on Model Risk Management for Banking Organizations](https://www.federalreserve.gov/supervisionreg/srletters/SR2602.htm)] (which supersedes SR 11-7) defines a model as a "complex quantitative method, system, or approach that applies statistical, economic, or financial theories to process input data into quantitative estimates." Simple arithmetic, deterministic rule-based processes, or software without statistical, economic, or financial theories underpinning their design or use are generally outside SR 26-2’s definition of a model.
+
+Within {{< var vm.product >}}, a model is a type of record tracked in the inventory.^[**Refer also to:** [record](/about/glossary/glossary.qmd#records)]
+::::
+
+:::: {.content-visible when-format="html" unless-meta="includes.glossary"}
+model
+: SR 26-2 (which supersedes SR 11-7) defines a model as a "complex quantitative method, system, or approach that applies statistical, economic, or financial theories to process input data into quantitative estimates." Simple arithmetic, deterministic rule-based processes, or software without statistical, economic, or financial theories underpinning their design or use are generally outside SR 26-2’s definition of a model.
+
+Within {{< var vm.product >}}, a model is a type of record tracked in the inventory.
+::::
\ No newline at end of file
diff --git a/site/about/glossary/key_concepts/_records.qmd b/site/about/glossary/key_concepts/_records.qmd
new file mode 100644
index 0000000000..174f514997
--- /dev/null
+++ b/site/about/glossary/key_concepts/_records.qmd
@@ -0,0 +1,16 @@
+
+
+:::: {.content-visible when-format="html" when-meta="includes.glossary"}
+record
+: A tool tracked in the {{< var validmind.platform >}} inventory,^[**Refer to:** [model](/about/glossary/glossary.qmd#models)] such as a model. Records include traditional statistical models, legacy systems, artificial intelligence/machine learning models, large language models (LLMs), agentic AI systems, and other documentable items that benefit from oversight, testing, and lifecycle management.
+
+::::
+
+:::: {.content-visible when-format="html" unless-meta="includes.glossary"}
+record
+: A tool tracked in the {{< var validmind.platform >}} inventory, such as a model. Records include traditional statistical models, legacy systems, artificial intelligence/machine learning models, large language models (LLMs), agentic AI systems, and other documentable items that benefit from oversight, testing, and lifecycle management.
+::::
+
+
diff --git a/site/about/glossary/key_concepts/_report.qmd b/site/about/glossary/key_concepts/_report.qmd
index 42157729e9..c5bf7b6960 100644
--- a/site/about/glossary/key_concepts/_report.qmd
+++ b/site/about/glossary/key_concepts/_report.qmd
@@ -5,4 +5,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
validation report
: A formal document produced after a model validation process, outlining the artifacts, assessments, and recommendations related to a specific model's performance, appropriateness, and limitations. Provides a comprehensive review of the model's conceptual framework, data sources and integrity, calibration methods, and performance outcomes.
-Within model risk management, the validation report is crucial for ensuring transparency, demonstrating regulatory compliance, and offering actionable insights for model refinement or adjustments.
\ No newline at end of file
+:::: {.content-visible when-format="html" when-meta="includes.glossary"}
+Within model risk management, the validation report is crucial for ensuring transparency, demonstrating regulatory compliance, and offering actionable insights for model refinement or adjustments.
+
+::::
\ No newline at end of file
diff --git a/site/about/glossary/key_concepts/_template.qmd b/site/about/glossary/key_concepts/_template.qmd
index 6a47859219..7c035e586b 100644
--- a/site/about/glossary/key_concepts/_template.qmd
+++ b/site/about/glossary/key_concepts/_template.qmd
@@ -10,16 +10,18 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
:::: {.content-visible when-format="html" when-meta="includes.glossary"}
document template
-: Lays out the structure of model documents, segmented into various sections and sub-sections, and function as test suites to help automate your development, validation, monitoring, and other risk management processes. Document templates are available for default {{< var vm.product >}} document types[^default-documents] as well as custom document types.
+: Lays out the structure of documents, segmented into various sections and sub-sections, and functions as a test suite to help automate your development, validation, monitoring, and other risk management processes. Document templates are available for default {{< var vm.product >}} document types[^default-documents] as well as custom document types.
-documentation template^[**Refer also to:** [Model documentation](/about/glossary/glossary.qmd#model-documentation)]
-: A default {{< var vm.product >}} document type that serves as a standardized framework for developing and documenting models, including sections designated for model details, data descriptions, test results, and performance metrics. By outlining required documentation and recommended analyses, document templates ensure consistency and completeness across model documentation and help guide developers through a systematic development process while promoting comparability and traceability of development outcomes.
+documentation template^[**Refer also to:** [documentation](/about/glossary/glossary.qmd#documentation)]
+: A default {{< var vm.product >}} document template that serves as a standardized framework for developing and documenting records (such as models), including sections designated for record details, data descriptions, test results, and performance metrics. By outlining required documentation and recommended analyses, documentation templates ensure consistency and completeness across documentation and help guide developers through a systematic development process while promoting comparability and traceability of development outcomes.
-validation report template^[**Refer also to:** [Validation reports](/about/glossary/glossary.qmd#validation-reports)]
-: A default {{< var vm.product >}} document type that serves as a standardized framework for conducting and documenting model validation, including sections designated for attaching test results, evidence, or artifacts (findings). By outlining required documentation, recommended analyses, and expected validation tests, validation report templates ensure consistency and completeness across validation reports and help guide validators through a systematic review process while promoting comparability and traceability of validation outcomes.
+{{< var vm.product >}} documentation templates function as test suites by defining the structure of your documentation, specifying the tests that should be run, and how the results should be displayed.
-monitoring template, monitoring report template^[**Refer also to:** [Ongoing monitoring](/about/glossary/glossary.qmd#ongoing-monitoring)]
-: A default {{< var vm.product >}} document type that serves as a standardized framework for ongoing model monitoring, including sections designated for test results, performance metrics, and drift analyses. By outlining required monitoring checks and expected routine tests, monitoring templates ensure consistency and completeness across monitoring reports and help guide model owners through a systematic monitoring process while promoting early detection of model performance degradation.
+validation report template^[**Refer also to:** [validation reports](/about/glossary/glossary.qmd#validation-reports)]
+: A default {{< var vm.product >}} document template that serves as a standardized framework for conducting and documenting validation, including sections designated for attaching test results, evidence, or artifacts (findings). By outlining required documentation, recommended analyses, and expected validation tests, validation report templates ensure consistency and completeness across validation reports and help guide validators through a systematic review process while promoting comparability and traceability of validation outcomes.
+
+monitoring template, monitoring report template^[**Refer also to:** [ongoing monitoring](/about/glossary/glossary.qmd#ongoing-monitoring)]
+: A default {{< var vm.product >}} document template that serves as a standardized framework for ongoing monitoring, including sections designated for test results, performance metrics, and drift analyses. By outlining required monitoring checks and expected routine tests, monitoring templates ensure consistency and completeness across monitoring reports and help guide owners through a systematic monitoring process while promoting early detection of performance degradation.
::::
@@ -31,16 +33,16 @@ document template
:::: {.content-visible when-format="html" unless-meta="includes.glossary"}
document template
-: Lays out the structure of model documents, segmented into various sections and sub-sections, and function as test suites to help automate your development, validation, monitoring, and other risk management processes. Document templates are available for default {{< var vm.product >}} document types as well as custom document types.
+: Lays out the structure of documents, segmented into various sections and sub-sections, and functions as a test suite to help automate your development, validation, monitoring, and other risk management processes. Document templates are available for default {{< var vm.product >}} document types as well as custom document types.
-documentation template
-: A default {{< var vm.product >}} document type that serves as a standardized framework for developing and documenting models, including sections designated for model details, data descriptions, test results, and performance metrics. By outlining required documentation and recommended analyses, document templates ensure consistency and completeness across model documentation and help guide developers through a systematic development process while promoting comparability and traceability of development outcomes.
+documentation template
+: A default {{< var vm.product >}} document type that serves as a standardized framework for developing and documenting records (such as models), including sections designated for record details, data descriptions, test results, and performance metrics. By outlining required documentation and recommended analyses, documentation templates ensure consistency and completeness across documentation and help guide developers through a systematic development process while promoting comparability and traceability of development outcomes.
-validation report template
-: A default {{< var vm.product >}} document type that serves as a standardized framework for conducting and documenting model validation, including sections designated for attaching test results, evidence, or artifacts (findings). By outlining required documentation, recommended analyses, and expected validation tests, validation report templates ensure consistency and completeness across validation reports and help guide validators through a systematic review process while promoting comparability and traceability of validation outcomes.
+validation report template
+: A default {{< var vm.product >}} document type that serves as a standardized framework for conducting and documenting validation, including sections designated for attaching test results, evidence, or artifacts (findings). By outlining required documentation, recommended analyses, and expected validation tests, validation report templates ensure consistency and completeness across validation reports and help guide validators through a systematic review process while promoting comparability and traceability of validation outcomes.
-monitoring template, monitoring report template
-: A default {{< var vm.product >}} document type that serves as a standardized framework for ongoing model monitoring, including sections designated for test results, performance metrics, and drift analyses. By outlining required monitoring checks and expected routine tests, monitoring templates ensure consistency and completeness across monitoring reports and help guide model owners through a systematic monitoring process while promoting early detection of model performance degradation.
+monitoring template, monitoring report template
+: A default {{< var vm.product >}} document type that serves as a standardized framework for ongoing monitoring, including sections designated for test results, performance metrics, and drift analyses. By outlining required monitoring checks and expected routine tests, monitoring templates ensure consistency and completeness across monitoring reports and help guide owners through a systematic monitoring process while promoting early detection of performance degradation.
::::
diff --git a/site/about/glossary/key_concepts/_test-suite.qmd b/site/about/glossary/key_concepts/_test-suite.qmd
index b1d2289365..59024193bc 100644
--- a/site/about/glossary/key_concepts/_test-suite.qmd
+++ b/site/about/glossary/key_concepts/_test-suite.qmd
@@ -2,7 +2,13 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-test suite
-: A collection of tests which are run together to generate model documentation end-to-end for specific use cases.
+:::: {.content-visible when-format="html" when-meta="includes.glossary"}
+
+test suite
+: A collection of tests designed to run together to automate and generate documentation end-to-end for specific use cases.^[**Learn more:** [test_suites](/validmind/validmind/test_suites.qmd)]
+::::
-For example, the [`classifier_full_suite`](/validmind/validmind/test_suites/classifier.qmd#classifierfullsuite){target="_blank"} test suite runs tests from the [`tabular_dataset`](/validmind/validmind/test_suites/tabular_datasets.qmd){target="_blank"} and [`classifier`](/validmind/validmind/test_suites/classifier.qmd){target="_blank"} test suites to fully document the data and model sections for binary classification model use cases.
\ No newline at end of file
+:::: {.content-visible when-format="html" unless-meta="includes.glossary"}
+test suite
+: A collection of tests designed to run together to automate and generate documentation end-to-end for specific use cases. (Learn more: [test_suites](/validmind/validmind/test_suites.qmd))
+::::
\ No newline at end of file
diff --git a/site/about/glossary/key_concepts/_test.qmd b/site/about/glossary/key_concepts/_test.qmd
index 6708c16a77..c4ead6e4b3 100644
--- a/site/about/glossary/key_concepts/_test.qmd
+++ b/site/about/glossary/key_concepts/_test.qmd
@@ -2,7 +2,7 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-test
-: A function contained in the {{< var vm.developer >}}, designed to run a specific quantitative test on the dataset or model. Test results are sent to the {{< var validmind.platform >}} to generate the model documentation according to the template that is associated with the documentation.
+test
+: A function contained in the {{< var vm.developer >}}, designed to run a specific quantitative test on the dataset or record (such as a model). Test results are logged to the {{< var validmind.platform >}}, where they are attached to documents.
-Tests are the building blocks of {{< var vm.product >}}, used to evaluate and document models and datasets, and can be run individually or as part of a suite defined by your model documentation template.
\ No newline at end of file
+Tests are the building blocks of {{< var vm.product >}}, used to evaluate and document records and datasets, and can be run individually or as part of a suite defined by your templates.
\ No newline at end of file
diff --git a/site/about/glossary/model_documentation/_conceptual-soundness.qmd b/site/about/glossary/model_documentation/_conceptual-soundness.qmd
deleted file mode 100644
index b173ee9f63..0000000000
--- a/site/about/glossary/model_documentation/_conceptual-soundness.qmd
+++ /dev/null
@@ -1,6 +0,0 @@
-
-
-conceptual soundness
-: Establishes the foundation of a selected record such as a model, covering the overview, intended use and business use case, regulatory requirements, limitations, and the rationale behind selection. It emphasizes purpose, scope, and constraints, which are crucial for stakeholders to understand applicability and limitations.
diff --git a/site/about/glossary/model_documentation/_monitoring-governance.qmd b/site/about/glossary/model_documentation/_monitoring-governance.qmd
deleted file mode 100644
index 9d6426d097..0000000000
--- a/site/about/glossary/model_documentation/_monitoring-governance.qmd
+++ /dev/null
@@ -1,6 +0,0 @@
-
-
-monitoring and governance
-: Focuses on the record such as a model’s ongoing monitoring plan, implementation, and governance plan. It outlines strategies for maintaining the performance over time and ensuring that it remains compliant with regulatory requirements and ethical standards.
\ No newline at end of file
diff --git a/site/about/glossary/monitoring/_backtesting.qmd b/site/about/glossary/monitoring/_backtesting.qmd
index 77a7e5cfe5..e642f0cef0 100644
--- a/site/about/glossary/monitoring/_backtesting.qmd
+++ b/site/about/glossary/monitoring/_backtesting.qmd
@@ -2,5 +2,5 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-backtesting
-: Comparing a model's predictions against actual outcomes to verify its predictive power and reliability.
+backtesting
+: Comparing a record's predictions against actual outcomes to verify its predictive power and reliability.
diff --git a/site/about/glossary/monitoring/_compliance-and-regulatory-adherence.qmd b/site/about/glossary/monitoring/_compliance-and-regulatory-adherence.qmd
index 2f1b50ff63..a0b9e89f71 100644
--- a/site/about/glossary/monitoring/_compliance-and-regulatory-adherence.qmd
+++ b/site/about/glossary/monitoring/_compliance-and-regulatory-adherence.qmd
@@ -3,4 +3,4 @@ Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
compliance and regulatory adherence
-: Ensuring that the model continues to meet evolving regulatory requirements and standards.
\ No newline at end of file
+: Ensuring that the record (model) continues to meet evolving regulatory requirements and standards.
\ No newline at end of file
diff --git a/site/about/glossary/monitoring/_model-drift.qmd b/site/about/glossary/monitoring/_model-drift.qmd
index 3023bc8ffc..84272e38da 100644
--- a/site/about/glossary/monitoring/_model-drift.qmd
+++ b/site/about/glossary/monitoring/_model-drift.qmd
@@ -2,5 +2,5 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-model drift
-: Changes in data patterns, input distributions, or model behavior that may indicate a degradation in model performance over time.
+model drift, drift
+: Changes in data patterns, input distributions, or record (such as a model) behavior that may indicate a degradation in performance over time.
diff --git a/site/about/glossary/monitoring/_model-performance.qmd b/site/about/glossary/monitoring/_model-performance.qmd
index 90d343f912..bf3dd4c6cb 100644
--- a/site/about/glossary/monitoring/_model-performance.qmd
+++ b/site/about/glossary/monitoring/_model-performance.qmd
@@ -2,5 +2,5 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-model performance
-: The measure of a model's accuracy, stability, and robustness in achieving its intended outcomes, which is regularly evaluated through monitoring after deployment to ensure ongoing reliability.
\ No newline at end of file
+model performance, performance
+: The measure of a record's accuracy, stability, and robustness in achieving its intended outcomes, which is regularly evaluated through monitoring after deployment to ensure ongoing reliability.
\ No newline at end of file
diff --git a/site/about/glossary/monitoring/_ongoing-monitoring.qmd b/site/about/glossary/monitoring/_ongoing-monitoring.qmd
index 818f5ac5f9..da04e6c99d 100644
--- a/site/about/glossary/monitoring/_ongoing-monitoring.qmd
+++ b/site/about/glossary/monitoring/_ongoing-monitoring.qmd
@@ -2,5 +2,5 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-ongoing monitoring
-: A periodic report assessing the tool such as a model's performance and compliance over time, ensuring it remains valid under changing conditions.
\ No newline at end of file
+ongoing monitoring, ongoing monitoring report, ongoing monitoring plan, monitoring plan
+: A comprehensive and structured periodic report assessing the record's performance and compliance over time, ensuring it remains valid under changing conditions. Monitoring includes key elements such as data sources, inputs, performance metrics, and periodic evaluations, ensuring transparency and visibility of the record's performance in the production environment.
\ No newline at end of file
diff --git a/site/about/glossary/monitoring/_recalibrating-models.qmd b/site/about/glossary/monitoring/_recalibrating-models.qmd
index 252a8ac653..9c1f2285d9 100644
--- a/site/about/glossary/monitoring/_recalibrating-models.qmd
+++ b/site/about/glossary/monitoring/_recalibrating-models.qmd
@@ -2,5 +2,5 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-recalibrating models
-: The process of adjusting a model to account for detected drift or changes in the underlying data or environment.
+recalibrating models, recalibrating
+: The process of adjusting a record (such as a model) to account for detected drift or changes in the underlying data or environment.
diff --git a/site/about/glossary/monitoring/_reporting-and-governance.qmd b/site/about/glossary/monitoring/_reporting-and-governance.qmd
index e0908f6ce2..d0152b7056 100644
--- a/site/about/glossary/monitoring/_reporting-and-governance.qmd
+++ b/site/about/glossary/monitoring/_reporting-and-governance.qmd
@@ -2,5 +2,5 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-reporting and governance
+reporting and governance
: The documentation of monitoring artifacts and communication to stakeholders to support decision-making and maintain transparency.
diff --git a/site/about/glossary/validation_reports/_artifacts.qmd b/site/about/glossary/validation_reports/_artifacts.qmd
index fc3c7cfe8b..5f27365aef 100644
--- a/site/about/glossary/validation_reports/_artifacts.qmd
+++ b/site/about/glossary/validation_reports/_artifacts.qmd
@@ -3,4 +3,4 @@ Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
artifacts (previously findings)
-: Observations or issues identified during validation, including any deviations from expected performance or standards. Artifacts are organized by type — default types include Validation Issue, Policy Exception, and Limitation. Custom artifact types such as Change Management Record can be created to track other categories relevant to your organization.
\ No newline at end of file
+: Observations or issues identified during validation, including any deviations from expected performance or standards. Artifacts are organized by type — default types provided by {{< var vm.product >}} include Validation Issue, Policy Exception, and Limitation. Custom artifact types can be created to track other categories relevant to your organization.
\ No newline at end of file
diff --git a/site/about/glossary/validation_reports/_report-intro.qmd b/site/about/glossary/validation_reports/_report-intro.qmd
index ed19217e3a..3525a01e55 100644
--- a/site/about/glossary/validation_reports/_report-intro.qmd
+++ b/site/about/glossary/validation_reports/_report-intro.qmd
@@ -2,4 +2,4 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-A validation report is a comprehensive review that evaluates a record's accuracy, performance, and suitability for its intended purpose. It encompasses the process of risk assessment, identifying areas of potential error or risk within the record's components, such as data inputs and algorithms. The report follows established validation guidelines to ensure consistency and adherence to internal and regulatory standards.
\ No newline at end of file
+A validation report is a comprehensive and structured review evaluating a record's accuracy, performance, and suitability for its intended purpose. A report follows established validation guidelines to ensure consistency and adherence to internal and regulatory standards — encompassing the process of risk assessment, identifying areas of potential error or risk within the record's components, supporting transparency, regulatory compliance, and informed decision-making by documenting the validator’s independent review and conclusions.
\ No newline at end of file
diff --git a/site/about/glossary/validation_reports/_risk-areas.qmd b/site/about/glossary/validation_reports/_risk-areas.qmd
index 34169742e5..323a642ca1 100644
--- a/site/about/glossary/validation_reports/_risk-areas.qmd
+++ b/site/about/glossary/validation_reports/_risk-areas.qmd
@@ -3,4 +3,4 @@ Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
model risk areas, risk areas
-: Specific components or aspects of a record such as a model where risk might be present, such as data inputs, algorithms, or implementation.
\ No newline at end of file
+: Specific components or aspects of a record (such as a model) where risk might be present, such as data inputs, algorithms, or implementation.
\ No newline at end of file
diff --git a/site/about/glossary/validation_reports/_risk-assessment.qmd b/site/about/glossary/validation_reports/_risk-assessment.qmd
index b862511921..39ec545370 100644
--- a/site/about/glossary/validation_reports/_risk-assessment.qmd
+++ b/site/about/glossary/validation_reports/_risk-assessment.qmd
@@ -3,4 +3,4 @@ Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
model risk assessment, risk assessment
-: The process of identifying and evaluating risks associated with the use and potential errors in a record such as a model.
\ No newline at end of file
+: The process of identifying and evaluating risks associated with the use and potential errors in a record (such as a model).
\ No newline at end of file
diff --git a/site/about/glossary/validation_reports/_validation-guidelines.qmd b/site/about/glossary/validation_reports/_validation-guidelines.qmd
index 77930799af..2ac7b8baf0 100644
--- a/site/about/glossary/validation_reports/_validation-guidelines.qmd
+++ b/site/about/glossary/validation_reports/_validation-guidelines.qmd
@@ -3,4 +3,4 @@ Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
validation guidelines
-: Established standards or procedures for conducting thorough and consistent validations, usually aligned with principles within specific tools such as models or AI risk frameworks.
\ No newline at end of file
+: Established standards or procedures for conducting thorough and consistent validations, usually aligned with principles within specific records (such as models) or AI risk frameworks.
\ No newline at end of file
diff --git a/site/about/library-and-platform.qmd b/site/about/library-and-platform.qmd
index 7f776107c8..ed0bcf2cf9 100644
--- a/site/about/library-and-platform.qmd
+++ b/site/about/library-and-platform.qmd
@@ -12,7 +12,7 @@ listing:
sort: false
fields: [title, description]
contents:
- - overview-model-documentation.qmd
+ - overview-documentation.qmd
- overview-llm-features.qmd
- deployment-options.qmd
- system-access-requirements.qmd
@@ -24,21 +24,21 @@ listing:
#### 1. {{< var validmind.developer >}}
-The *{{< var validmind.developer >}}* is a Python library of tools and methods designed to automate generating model documentation and running validation tests. The {{< var vm.developer >}} is designed to be platform agnostic and integrates with your existing development environment.
+The *{{< var validmind.developer >}}* is a Python library of tools and methods designed to automate generating documentation and running validation tests. The {{< var vm.developer >}} is designed to be platform agnostic and integrates with your existing development environment.
For Python developers, a single installation command provides access to all the functions:
-
+
```python
%pip install validmind
```
#### 2. {{< var validmind.platform >}}
-The *{{< var validmind.platform >}}* is an easy-to-use web-based interface that enables you to track the model lifecycle:
+The *{{< var validmind.platform >}}* is an easy-to-use web-based interface that enables you to track your risk management lifecycles:
- Customize workflows to adhere to and oversee your governance processes.
- Review and edit the documentation and test metrics generated by the {{< var vm.developer >}}.
-- Collaborate with and capture feedback from model developers and model validators.
+- Collaborate with and capture feedback from developers and validators.
- Generate validation reports and approvals.
:::
diff --git a/site/about/overview-model-documentation.qmd b/site/about/overview-documentation.qmd
similarity index 65%
rename from site/about/overview-model-documentation.qmd
rename to site/about/overview-documentation.qmd
index 2edacee030..7954b36a9e 100644
--- a/site/about/overview-model-documentation.qmd
+++ b/site/about/overview-documentation.qmd
@@ -2,10 +2,11 @@
# Copyright © 2023-2026 ValidMind Inc. All rights reserved.
# Refer to the LICENSE file in the root of this repository for details.
# SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial
-title: "Automated model testing & documentation"
+title: "Automated testing & documentation"
date: last-modified
aliases:
- /guide/overview-model-documentation.html
+ - /about/overview-model-documentation.html
listing:
id: quickstart
type: grid
@@ -17,40 +18,40 @@ listing:
- path: ../developer/validmind-library.qmd
# INVISIBLE SPACE REQUIRED TO ENSURE THAT THE DESCRIPTION DOESN'T HAVE EXTRA PADDING DUE TO THE VARIABLE
title: "{{< var validmind.developer >}}"
- description: "The {{< var validmind.developer >}} streamlines model development and validation by automating testing."
+ description: "The {{< var validmind.developer >}} streamlines development and validation by automating testing."
fields: [title, description]
---
-The {{< var validmind.developer >}} streamlines the process of documenting various types of models. {{< var vm.product >}} automates the documentation process, ensuring that your model documentation and testing aligns with regulatory and compliance standards.
+The {{< var validmind.developer >}} streamlines the process of documenting various types of records, such as models. {{< var vm.product >}} automates the documentation process, ensuring that your documentation and testing aligns with regulatory and compliance standards.
::: {.attn}
## {{< fa code >}} The {{< var validmind.developer >}}
-The {{< var validmind.developer >}} is a Python library 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).
+The {{< var validmind.developer >}} is a Python library and documentation engine designed to streamline the process of documenting various types of records, including traditional statistical models, legacy systems, artificial intelligence/machine learning models, large language models (LLMs), agentic AI systems, and more.
-It offers model developers a systematic approach to documenting and testing risk models with repeatability and consistency, ensuring alignment with regulatory and compliance standards.
+It offers developers a systematic approach to documenting and testing with repeatability and consistency, ensuring alignment with regulatory and compliance standards.
{fig-alt="An image showing the two main components of ValidMind: the ValidMind Library that integrates with your existing developer environment, and the ValidMind Platform"}
-The {{< var validmind.developer >}} consists of a client-side library, a {{< var vm.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.
+The {{< var validmind.developer >}} consists of a client-side library, a {{< var vm.api >}} integration for records (models) and testing, and validation tests that streamline the 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.
With the {{< var validmind.developer >}}, you can:
-- **Automate documentation** — Add comprehensive documentation as metadata while you build models to be shared with model validators, streamlining and speeding up the process.
+- **Automate documentation** — Add comprehensive documentation as metadata while you build records to be shared with validators, streamlining and speeding up the process.
- **Run test suites** — Identify potential risks for a diverse range of statistical and AI/LLM/ML models by assessing data quality, model outcomes, robustness, and explainability.
-- **Integrate with your development environment** — Seamlessly incorporate the {{< var validmind.developer >}} into your existing model development environment, connecting to your existing model code and data sets.
-- **Upload documentation data** — Send qualitative and quantitative test data to the {{< var validmind.platform >}}[^1] to generate the model documentation for review and approval, fostering effective collaboration with model reviewers and validators.
+- **Integrate with your development environment** — Seamlessly incorporate the {{< var validmind.developer >}} into your existing development environment, connecting to your existing code and data sets.
+- **Upload documentation data** — Send qualitative and quantitative test data to the {{< var validmind.platform >}}[^1] to generate the documentation for review and approval, fostering effective collaboration with reviewers and validators.
:::
## Simple installation
-Install the {{< var vm.developer >}} with:
+Install the {{< var vm.developer >}} with:
```python
%pip install validmind
@@ -64,8 +65,8 @@ Install the {{< var vm.developer >}} with:
What the {{< var validmind.developer >}} offers:
-- Generates documentation artifacts utilizing the context of the model and dataset, the model's metadata, and the chosen documentation template.
-- Can be easily imported into your local model development environment. The supported platforms include Python and R.
+- Generates documentation artifacts utilizing the context of the record (such as a model) and dataset, the record's metadata, and the chosen documentation template.
+- Can be easily imported into your local development environment. The supported platforms include Python and R.
- Dual-licensed — The {{< var vm.developer >}} is available as open-source under AGPL v3 license and also with a commercial software license.
:::
@@ -79,18 +80,18 @@ vm.init(model="MODEL_IDENTIFIER")
```
```python
-vm_dataset = vm. log_dataset(
+vm_dataset = vm.log_dataset(
df,
"training",
targets=targets,
)
-vm. run_dataset_tests(df, vm_dataset=vm_dataset)
+vm.run_dataset_tests(df, vm_dataset=vm_dataset)
```
```python
-vm. Log_model (model)
-vm. log_training_metrics (model, x_train, y_train)
-vm. run_model_tests (model, x_test, y_test)
+vm.log_model (model)
+vm.log_training_metrics (model, x_train, y_train)
+vm.run_model_tests (model, x_test, y_test)
```
:::
@@ -100,12 +101,12 @@ vm. run_model_tests (model, x_test, y_test)
How the {{< var validmind.developer >}} works:
-- The tests and functions are executed automatically, following pre-configured templates tailored for specific model use cases. This ensures that minimum documentation requirements are consistently fulfilled.
+- The tests and functions are executed automatically, following pre-configured templates tailored for specific use cases. This ensures that minimum documentation requirements are consistently fulfilled.
- The {{< var vm.developer >}} integrates with ETL/data processing pipelines using connector interfaces. This enables the extraction of relationships between raw data sources and their corresponding post-processed datasets, such as those preloaded session instances received from platforms like Spark and Snowflake.
## Extensible by design
-{{< var vm.product >}} supports various model types, including:[^2]
+{{< var vm.product >}} supports various record (model) types, including:[^2]
- Traditional machine learning models (ML) such as tree-based models and neural network models.
- Natural language processing models (NLP) for text analysis and understanding.
@@ -114,25 +115,25 @@ How the {{< var validmind.developer >}} works:
{{< var vm.product >}} is designed to be highly extensible to cater to our customers' specific requirements. You can expand its functionality in the following ways:
-- You can easily add support for new models and data types by defining new classes within the {{< var validmind.developer >}}. We provide templates to guide you through this process.[^3]
-- To include custom tests in the library, you can define new functions. We offer templates to help you create these custom tests.[^4]
-- You have the flexibility to integrate third-party test libraries seamlessly. These libraries can be hosted either locally within your infrastructure or remotely, for example, on GitHub. Leverage additional testing capabilities and resources as needed.[^5]
+- You can easily add support for new records and data types by defining new classes within the {{< var validmind.developer >}}. We provide templates to guide you through this process.[^3]
+- To include custom tests in the library, you can define new functions. We offer templates to help you create these custom tests.[^4]
+- You have the flexibility to integrate third-party test libraries seamlessly. These libraries can be hosted either locally within your infrastructure or remotely, for example, on GitHub. Leverage additional testing capabilities and resources as needed.[^5]
## {{< var validmind.api >}} integration
{{< var vm.product >}} imports the following artifacts into the documentation via our {{< var validmind.api >}} integration:
-- Metadata about datasets and models, used to lookup programmatic documentation content, such as the stored definition for _common logistic regression limitations_ when a logistic regression model has been passed to the {{< var vm.product >}} test plan to be run.
-- Quality and performance metrics collected from datasets and models.
-- Output from test and test suites that have been run.
+- Metadata about datasets and records (models), used to look up programmatic documentation content, such as the stored definition for _common logistic regression limitations_ when a logistic regression model has been passed to the {{< var vm.product >}} test plan to be run.
+- Quality and performance metrics collected from datasets and records.
+- Output from tests and test suites that have been run.
- Images, plots, visuals that were generated as part of extracting metrics and running tests.
{width=90% fig-alt="A representation of artifacts imported into the documentation via our Python API"}
::: {.callout-important}
-## {{< var vm.product >}} does NOT:
-- Send any personal identifiable information (PII) when generating documentation reports.
-- Store any customer datasets or models.
+## {{< var vm.product >}} does NOT:
+- Send any personally identifiable information (PII) when generating documentation reports.
+- Store any customer datasets or records.
:::
## Ready to try out {{< var vm.product >}}?
diff --git a/site/about/overview-llm-features.qmd b/site/about/overview-llm-features.qmd
index 2dc6c1d19d..202c7e1217 100644
--- a/site/about/overview-llm-features.qmd
+++ b/site/about/overview-llm-features.qmd
@@ -6,7 +6,7 @@ title: "Large language model features"
date: last-modified
---
-{{< var vm.product >}} offers several specialized features that use large language models (LLMs) to streamline model risk management and ensure regulatory compliance. Here's how we approach these features and what you need to know.
+{{< var vm.product >}} offers several specialized features that use large language models (LLMs) to streamline risk management and ensure regulatory compliance. Here's how we approach these features and what you need to know.
::: {.attn}
## {{< fa list-check >}} Our philosophy
@@ -30,7 +30,7 @@ Our testing methodologies and philosophy around testing are readily available, a
## Our features
-{{< var vm.product >}} enhances model documentation, testing, and compliance workflows, providing your team with tools for effective model governance.
+{{< var vm.product >}} enhances documentation, testing, and compliance workflows, providing your team with tools for effective risk governance.
::: {.column-margin .pl3 .pt6}
@@ -54,13 +54,13 @@ Why it matters
::: {.w-50-ns .pl2 .pr2}
### Qualitative checks
-Leverages metadata from the model inventory, test outcomes, and additional data provided to create qualitative sections within model documentation.
+Leverages metadata from the inventory, test outcomes, and additional data provided to create qualitative sections within documentation.
::: {.feature}
Why it matters
-: Qualitative checks ensure that essential contextual information is accurately documented and aligned with the model's purpose and scope.
+: Qualitative checks ensure that essential contextual information is accurately documented and aligned with the record's purpose and scope.
:::
:::
@@ -72,7 +72,7 @@ Why it matters
::: {.w-50-ns .pr2}
### Risk assessment
-Using data from test results, generates a tailored risk assessment for each section of model documentation. This feature aids in identifying potential risks based on the model’s performance and results.
+Using data from test results, generates a tailored risk assessment for each section of documentation. This feature aids in identifying potential risks based on the record's performance and results.
::: {.feature}
Why it matters
@@ -85,7 +85,7 @@ Why it matters
::: {.w-50-ns .pl2 .pr2}
### {{< var validmind.checker >}}
-Reviews documents such as model documentation or validation reports to ensure documents aligns with relevant regulatory requirements.
+Reviews documents such as documentation or validation reports to ensure documents align with relevant regulatory requirements.
@@ -97,7 +97,7 @@ Why it matters
+Assesses each part of the documentation for adherence to internal guidelines and policies. This tool supports consistent documentation standards across the organization, promoting uniformity in compliance practices. -->
:::
::::
@@ -120,7 +120,7 @@ These documents detail our [AI usage policy](https://validmind.com/about/legal/a
::: {.w-50-ns .pr3}
### Try it yourself
-Discover how {{< var vm.product >}}’s LLM-powered platform, purpose-built for model risk management teams, enables streamlined and confident testing, documentation, validation, and governance of generative AI models and processes.
+Discover how {{< var vm.product >}}’s LLM-powered platform, purpose-built for risk management teams, enables streamlined and confident testing, documentation, validation, and governance of generative AI systems and processes.
[Request a Demo](https://validmind.com/request-demo/){.button .button-green}
diff --git a/site/about/overview.qmd b/site/about/overview.qmd
index 8b1ef72853..af7f860745 100644
--- a/site/about/overview.qmd
+++ b/site/about/overview.qmd
@@ -32,7 +32,7 @@ aliases:
- /about.html
---
-{{< var vm.product >}} is the system of record for AI governance. You use {{< var vm.product >}} to model the full lifecycle of AI systems, models, use cases, and tools, along with their dependencies, and automates the governance and documentation you build on top.
+{{< var vm.product >}} is the system of record for AI governance. You use {{< var vm.product >}} to model the full lifecycle of AI systems, records (such as models), use cases, and tools, along with their dependencies, and automates the governance and documentation you build on top.
Flexible by design, the {{< var vm.platform >}} lets you define your own inventory hierarchy, dependencies, and governance rules, powered by {{< var vm.product >}}’s documentation automation, workflows, and analytics.
@@ -40,7 +40,7 @@ Flexible by design, the {{< var vm.platform >}} lets you define your own invento
::: {.column-margin}
::: {.image-container}
-
+



@@ -56,7 +56,8 @@ Flexible by design, the {{< var vm.platform >}} lets you define your own invento
## {{< fa hand-point-right >}} Ready to try out {{< var vm.product >}}?
+:::{#validmind-next-steps}
:::
-:::{#validmind-next-steps}
:::
+
diff --git a/site/about/using-the-documentation.qmd b/site/about/using-the-documentation.qmd
index ca5dee30ad..39f59870e6 100644
--- a/site/about/using-the-documentation.qmd
+++ b/site/about/using-the-documentation.qmd
@@ -8,7 +8,7 @@ aliases:
- /about/contributing/using-the-documentation.html
---
-This documentation site helps you learn {{< var vm.product >}}, implement it in your organization, govern your AI/ML models, and operate the platform day to day.
+This documentation site helps you learn {{< var vm.product >}}, implement it in your organization, govern your AI/ML records (models), and operate the platform day to day.
## How to use this site
@@ -37,7 +37,7 @@ Introduces the platform, its use cases, and deployment options.
Role-based quickstarts to help you begin using {{< var vm.product >}} quickly.
-- [Developer quickstart](/get-started/developer/quickstart-developer.qmd) — Set up your environment and document your first model
+- [Developer quickstart](/get-started/developer/quickstart-developer.qmd) — Set up your environment and document your first record (model)
- [Validator quickstart](/get-started/validator/quickstart-validator.qmd) — Review documentation and prepare validation reports
- [Administrator quickstart](/get-started/administrator/quickstart-administrator.qmd) — Configure users, roles, and organization settings
@@ -51,14 +51,14 @@ Step-by-step instructions for platform tasks, organized by feature area.
|---------|--------|---------------|
| [Access](/guide/guides.qmd#access) | Signing up for and logging into {{< var vm.product >}} | Register, sign in via SSO, recover access |
| [Configuration](/guide/guides.qmd#configuration) | Setting up your organization and users | Add users, create groups, assign roles and permissions |
-| [Integrations](/guide/integrations/managing-integrations.qmd) | Connecting {{< var vm.product >}} to external systems | Manage secrets, configure connections, link external models |
-| [Workflows](/guide/guides.qmd#workflows) | Automating model lifecycle processes | Configure workflow steps, manage transitions, set up approvals |
-| [Inventory](/guide/guides.qmd#inventory) | Managing your model and record inventory | Register records, edit fields, configure interdependencies |
+| [Integrations](/guide/integrations/managing-integrations.qmd) | Connecting {{< var vm.product >}} to external systems | Manage secrets, configure connections, link external records (models) |
+| [Workflows](/guide/guides.qmd#workflows) | Automating lifecycle processes | Configure workflow steps, manage transitions, set up approvals |
+| [Inventory](/guide/guides.qmd#inventory) | Managing your records (models) and record inventory | Register records, edit fields, configure interdependencies |
| [Documents & templates](/guide/templates/working-with-documents.qmd) | Creating and customizing documentation | Manage document types, customize templates, use the text block library |
-| [Model documentation](/guide/guides.qmd#model-documentation) | Authoring and collaborating on model docs | Edit content blocks, add test results, manage versions, submit for approval |
-| [Model validation](/guide/guides.qmd#model-validation) | Reviewing and validating models | Review documentation, assess compliance, manage findings and artifacts |
+| [Documentation](/guide/guides.qmd#documentation) | Authoring and collaborating on documents | Edit content blocks, add test results, manage versions, submit for approval |
+| [Validation](/guide/guides.qmd#validation) | Reviewing and validating records (models) | Review documentation, assess compliance, manage findings and artifacts |
| [Reporting](/guide/guides.qmd#reporting) | Analyzing and exporting data | View reports, create custom analytics, export inventory and documents |
-| [Monitoring](/guide/guides.qmd#monitoring) | Tracking model performance over time | Enable monitoring, review results, set thresholds and alerts |
+| [Monitoring](/guide/guides.qmd#monitoring) | Tracking record (model) performance over time | Enable monitoring, review results, set thresholds and alerts |
| [Attestation](/guide/guides.qmd#attestation) | Managing formal attestations | Create, submit, review, and approve attestations |
### [{{< var validmind.developer >}}](/developer/validmind-library.qmd)
diff --git a/site/developer/how-to/testing-overview.qmd b/site/developer/how-to/testing-overview.qmd
index d21a1c3f5d..129c428de9 100644
--- a/site/developer/how-to/testing-overview.qmd
+++ b/site/developer/how-to/testing-overview.qmd
@@ -138,7 +138,7 @@ listing:
## Explore tests
-Start by exploring the {{< var validmind.developer >}}'s available tests and tests suites:
+Start by exploring the {{< var validmind.developer >}}'s available tests and test suites:
::: {.panel-tabset}
diff --git a/site/faq/_faq-activity.qmd b/site/faq/_faq-activity.qmd
index b950ebeccd..42dee4c34c 100644
--- a/site/faq/_faq-activity.qmd
+++ b/site/faq/_faq-activity.qmd
@@ -2,7 +2,7 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-## Is activity on models, documents, etc. logged?
+## Is activity on records, documents, etc. logged?
-- Yes, the {{< var validmind.platform >}}^[[Accessing {{< var vm.product >}}](/guide/access/accessing-validmind.qmd)] provides an audit trail functionality, enabling you to track or audit all the events associated with a specific model.
-- You can review a full record of comments, workflow status changes, and any other updates made to the model, including modifications to documents or test results.
\ No newline at end of file
+- Yes, the {{< var validmind.platform >}}^[[Accessing {{< var vm.product >}}](/guide/access/accessing-validmind.qmd)] provides an audit trail functionality, enabling you to track or audit all the events associated with a specific record (such as a model).
+- You can review a full record of comments, workflow status changes, and any other updates made to the record, including modifications to documents or test results.
\ No newline at end of file
diff --git a/site/faq/_faq-attachments.qmd b/site/faq/_faq-attachments.qmd
index a37ad2d71b..625f325a92 100644
--- a/site/faq/_faq-attachments.qmd
+++ b/site/faq/_faq-attachments.qmd
@@ -2,11 +2,11 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-## Can we attach files to models, artifacts, or documents?
+## Can we attach files to records, artifacts, or documents?
-Yes, attachment type inventory fields are available for custom use.^[[Manage inventory fields](/guide/inventory/manage-inventory-fields.qmd)] Once created, attachment type fields allow you to upload supporting files to your model.
+Yes, attachment type inventory fields are available for custom use.^[[Manage inventory fields](/guide/inventory/manage-inventory-fields.qmd)] Once created, attachment type fields allow you to upload supporting files to your record (model).
-- Out-of-the-box functionality is included for attaching files to model artifacts.
+- Out-of-the-box functionality is included for attaching files to artifacts.
- You can also attach images to document content blocks and comments.
-By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to manage model inventory fields.
\ No newline at end of file
+By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to manage inventory fields.
\ No newline at end of file
diff --git a/site/faq/_faq-explainability.qmd b/site/faq/_faq-explainability.qmd
index 7381f1fd9e..f4fc4bcb68 100644
--- a/site/faq/_faq-explainability.qmd
+++ b/site/faq/_faq-explainability.qmd
@@ -2,11 +2,11 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-## Do you include explainability-related testing and documentation?
-
-Yes, {{< var vm.product >}} includes explainability-related testing and documentation as part of our offerings. Our approach incorporates a comprehensive suite of tests designed to evaluate model interpretability and identify potential risks, ensuring transparency and reliability in model outcomes.
+## Do you include explainability-related testing and documentation?
+
+Yes, {{< var vm.product >}} includes explainability-related testing and documentation as part of our offerings. Our approach incorporates a comprehensive suite of tests designed to evaluate interpretability and identify potential risks, ensuring transparency and reliability in outcomes.
-Below is an overview of our key explainability-related tests (browse names and descriptions in the [{{< var vm.product >}} test sandbox](/developer/how-to/test-sandbox.qmd)):
+Below is an overview of our key explainability-related tests^[[{{< var vm.product >}} test sandbox](/developer/how-to/test-sandbox.qmd)] with models as an example:
- **Features AUC** — Assesses the discriminatory power of individual features in binary classification models, providing insights into how well each feature differentiates between classes. This test supports explainability by isolating the contribution of each feature to the classification task.
- **Feature Importance** — Generates feature importance scores to identify and compare impactful features across different models and datasets. By highlighting the relative significance of features, this test clarifies how inputs influence model predictions.
diff --git a/site/faq/_faq-images.qmd b/site/faq/_faq-images.qmd
index 2d36be4758..c84d874f14 100644
--- a/site/faq/_faq-images.qmd
+++ b/site/faq/_faq-images.qmd
@@ -2,7 +2,7 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-## Do you support including images in model documents?
+## Do you support including images in documents?
Yes, as long as you can produce the image with Python or open the image from a file, you can include it in your documents with {{< var vm.product >}}:^[[Implement custom tests](/notebooks/how_to/tests/custom_tests/implement_custom_tests.ipynb#custom-test-images)]
diff --git a/site/faq/_faq-model-updates.qmd b/site/faq/_faq-model-updates.qmd
deleted file mode 100644
index a9a23c7325..0000000000
--- a/site/faq/_faq-model-updates.qmd
+++ /dev/null
@@ -1,9 +0,0 @@
-
-
-## How does {{< var vm.product >}} manage updates to models?
-
-1. {{< var vm.product >}} allows model developers to re-run documentation functions with the {{< var validmind.developer >}}^[[{{< var validmind.developer >}}](/developer/validmind-library.qmd)] to capture changes in the model, such as changes in the number of features or hyperparameters.
-2. After a model developer has made a change in their development environment, such as to a Jupyter Notebook,^[[Code samples](/developer/samples-jupyter-notebooks.qmd)] they can execute the relevant {{< var vm.product >}} documentation function to update the corresponding documentation section.
-3. {{< var vm.product >}} will then automatically recreate the relevant figures and tables and update them in the online documentation.
\ No newline at end of file
diff --git a/site/faq/_faq-monitoring.qmd b/site/faq/_faq-monitoring.qmd
index 76d6b43827..372ac8f510 100644
--- a/site/faq/_faq-monitoring.qmd
+++ b/site/faq/_faq-monitoring.qmd
@@ -2,11 +2,11 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-## Does {{< var vm.product >}} support monitoring models after deployment?
+## Does {{< var vm.product >}} support monitoring records after deployment?
-Yes, {{< var vm.product >}} offers ongoing monitoring support to help you regularly assess a model’s accuracy, stability, and robustness to ensure it remains reliable after deployment:
+Yes, {{< var vm.product >}} offers ongoing monitoring support to help you regularly assess a record’s accuracy, stability, and robustness to ensure it remains reliable after deployment:
-- You can enable monitoring for both new and existing models.^[[Enable monitoring](/guide/monitoring/enable-monitoring.qmd)]
-- You use the {{< var validmind.developer >}} to automatically populate the monitoring template for your model with data, providing a comprehensive view of your model’s performance over time.
+- You can enable monitoring for both new and existing records.^[[Enable monitoring](/guide/monitoring/enable-monitoring.qmd)]
+- You use the {{< var validmind.developer >}} to automatically populate the monitoring template for your record with data, providing a comprehensive view of your record’s performance over time.
- You then access and examine these results within the {{< var validmind.platform >}}, allowing you to identify any deviations from expected performance and take corrective actions as needed.^[[Review monitoring results](/guide/monitoring/review-monitoring-results.qmd)]
- Once generated via the {{< var validmind.developer >}}, view and add metrics over time to your ongoing monitoring reports in the {{< var validmind.platform >}}.^[[Work with metrics over time](/guide/monitoring/work-with-metrics-over-time.qmd)]
\ No newline at end of file
diff --git a/site/faq/_faq-progress-model.qmd b/site/faq/_faq-progress-workflow.qmd
similarity index 53%
rename from site/faq/_faq-progress-model.qmd
rename to site/faq/_faq-progress-workflow.qmd
index aebd3a98eb..dd9e0f62b3 100644
--- a/site/faq/_faq-progress-model.qmd
+++ b/site/faq/_faq-progress-workflow.qmd
@@ -2,8 +2,8 @@
Refer to the LICENSE file in the root of this repository for details.
SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
-## How do I progress a model along in its lifecycle within {{< var vm.product >}}?
+## How do I progress a record along in its lifecycle within {{< var vm.product >}}?
-Transition a model along in the workflow, for example for review with the next set of stakeholders, by changing a model's status.
+Transition a record (such as a model) along in the workflow, for example for review with the next set of stakeholders, by changing a record's status.
{{< include /guide/workflows/_transition-workflow-examples.qmd >}}
\ No newline at end of file
diff --git a/site/faq/_faq-record-updates.qmd b/site/faq/_faq-record-updates.qmd
new file mode 100644
index 0000000000..739040675e
--- /dev/null
+++ b/site/faq/_faq-record-updates.qmd
@@ -0,0 +1,9 @@
+
+
+## How does {{< var vm.product >}} manage updates to records?
+
+1. {{< var vm.product >}} allows developers to re-run documentation functions with the {{< var validmind.developer >}}^[[{{< var validmind.developer >}}](/developer/validmind-library.qmd)] to capture changes in the record (such as a model), such as changes in the number of features or hyperparameters.
+2. After a developer has made a change in their development environment, such as to a Jupyter Notebook,^[[Code samples](/developer/samples-jupyter-notebooks.qmd)] they can execute the relevant {{< var vm.product >}} documentation function to update the corresponding documentation section.
+3. {{< var vm.product >}} will then automatically recreate the relevant figures and tables and update them in the online documentation.
\ No newline at end of file
diff --git a/site/faq/_faq-tracking.qmd b/site/faq/_faq-tracking.qmd
index 82ae4cc508..2a8c460248 100644
--- a/site/faq/_faq-tracking.qmd
+++ b/site/faq/_faq-tracking.qmd
@@ -4,5 +4,5 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
## Can I use {{< var vm.product >}} to track milestone dates?
-- Yes, the {{< var validmind.platform >}} includes support for custom inventory fields, including those for dates and date time — allowing you to track important dates throughout the model risk management lifecycle unique to your workflow.
+- Yes, the {{< var validmind.platform >}} includes support for custom inventory fields, including those for dates and date time — allowing you to track important dates throughout the risk management lifecycle unique to your workflow.
- In addition, calculation type custom inventory fields can draw upon date and date time values, allowing you to automatically calculate next review, revalidation, ongoing monitoring deadlines, or any other desired date.
diff --git a/site/faq/faq-collaboration.qmd b/site/faq/faq-collaboration.qmd
index c1901b8180..76e1dd16ac 100644
--- a/site/faq/faq-collaboration.qmd
+++ b/site/faq/faq-collaboration.qmd
@@ -4,8 +4,6 @@
# SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial
title: "Collaboration"
date: last-modified
-aliases:
- - /guide/faq-workflows.html
listing:
- id: faq-collaboration
type: grid
@@ -17,15 +15,15 @@ listing:
- ../guide/inventory/view-record-activity.qmd
- ../guide/documentation/collaborate-with-others.qmd
- ../guide/workflows/working-with-workflows.qmd
-categories: ["real-time collaboration", "documents","documentation", "record activity", "auditing", "workflows", "model lifecycle", "validmind platform"]
+categories: ["real-time collaboration", "documents","documentation", "record activity", "auditing", "workflows", "lifecycle", "validmind platform"]
---
{{< include _faq-activity.qmd >}}
## What real-time collaboration features does {{< var vm.product >}} offer?
-- You can simultaneously edit model documents, leave and respond to comments or suggestions all within the {{< var validmind.platform >}}.
-- You can also saved named versions of edits to retain specific revisions, and any changes to model documents are automatically logged on your model's activity feed.
+- You can simultaneously edit documents, leave and respond to comments or suggestions all within the {{< var validmind.platform >}}.
+- You can also save named versions of edits to retain specific revisions, and any changes to documents are automatically logged on your record's activity feed.
::: {.callout}
## Multiple users are able to simultaneously edit documents in the {{< var validmind.platform >}}.
@@ -33,7 +31,7 @@ categories: ["real-time collaboration", "documents","documentation", "record act
If two users are editing the same cell within {{< var vm.platform >}}, the most recently saved version of the content will prevail.
:::
-{{< include _faq-progress-model.qmd >}}
+{{< include _faq-progress-workflow.qmd >}}
@@ -45,6 +43,6 @@ If two users are editing the same cell within {{< var vm.platform >}}, the most
## Learn more
-:::{#faq-validation}
+:::{#faq-collaboration}
:::
diff --git a/site/faq/faq-documentation.qmd b/site/faq/faq-documentation.qmd
index 244940cf56..bd78fd0859 100644
--- a/site/faq/faq-documentation.qmd
+++ b/site/faq/faq-documentation.qmd
@@ -2,7 +2,7 @@
# Copyright © 2023-2026 ValidMind Inc. All rights reserved.
# Refer to the LICENSE file in the root of this repository for details.
# SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial
-title: "Model documents and templates"
+title: "Documents and templates"
date: last-modified
aliases:
- /guide/faq-documentation.html
@@ -23,7 +23,7 @@ categories: ["templates", "documents", "documentation","customization", "images"
{{< var vm.product >}} provides the following default template types:[^1]
-- Development (model documentation)
+- Development (documentation)
- Validation (validation reports)
- Monitoring (ongoing monitoring reports)
@@ -31,7 +31,7 @@ You can also create custom document types and associated templates to suit your
## Can templates be customized for our use cases?
-Yes, the {{< var validmind.platform >}}[^2] allows you to configure versioned templates based on document requirements for each model or lifecycle use case.
+Yes, the {{< var validmind.platform >}}[^2] allows you to configure versioned templates based on document requirements for each record (such as a model) or lifecycle use case.
- {{< var vm.product >}}'s templates are fully customizable,[^3] and are complemented by the ability to manage validation guidelines.
- You can swap between different versions of templates or apply another version of the current template.[^4]
@@ -41,17 +41,17 @@ By default, the [{{< fa hand >}} Customer Admin]{.bubble} role[^5] has sufficien
## Can documents be created right in the {{< var validmind.platform >}}?
-Yes, you can work with model documentation, validation reports, ongoing monitoring reports, or any other document type directly in the {{< var validmind.platform >}}, without having to first generate anything using the {{< var validmind.developer >}}.[^6]
+Yes, you can work with documentation, validation reports, ongoing monitoring reports, or any other document type directly in the {{< var validmind.platform >}}, without having to first generate anything using the {{< var validmind.developer >}}.[^6]
1. Add and edit text on any document within the {{< var vm.platform >}} using our content editing toolbar.[^7]
2. Using the {{< var vm.developer >}}, execute test suites and generate the corresponding supporting results. These results can then be added to your documents within the {{< var vm.platform >}}.[^8]
-## Can I run tests and log documentation without a model?
-
-Yes! If you do not have a model ready, or your model can't be loaded directly, or you only have access to model predictions, you can still run tests and log documentation using the {{< var validmind.developer >}} as long as you're able to load the model predictions.
+## Can I run tests and log documentation without a record?
+
+Yes! If you do not have a record (such as a model) ready, or your record can't be loaded directly, or you only have access to predictions, you can still run tests and log documentation using the {{< var validmind.developer >}} as long as you're able to load the predictions.
- Use `assign_predictions()`[^9] to load predictions from a separate file or a dataset with predictions.
-- Call `init_model()`[^10] but instead of a trained model instance, pass an `input_id` and model metadata. `ModelMetadata()`[^11] will use the provided metadata instead of trying to calculate it from the model's library.
+- Call `init_model()`[^10] to create a model object, but instead of a trained instance, pass an `input_id` and model metadata. `ModelMetadata()`[^11] will use the provided metadata instead of trying to calculate it from the model's library.
::: {.column-margin}
@@ -65,8 +65,10 @@ Yes! If you do not have a model ready, or your model can't be loaded directly, o
```
:::
-::: {.callout title="If neither a trained model instance nor metadata is provided, `init_model()` will return an error. "}
-However, tests that need a trained model will not work with "empty" models.
+::: {.callout title="If neither a trained instance nor metadata is provided, `init_model()` will return an error."}
+- However, tests that need a trained model will not work with "empty" models.
+- Despite the naming convention, model objects can be any type of record you want to test, document, validate, or monitor with {{< var vm.product >}}.
+
:::
{{< include _faq-attachments.qmd >}}
diff --git a/site/faq/faq-integrations.qmd b/site/faq/faq-integrations.qmd
index dd1d65314c..e1be635668 100644
--- a/site/faq/faq-integrations.qmd
+++ b/site/faq/faq-integrations.qmd
@@ -22,7 +22,7 @@ categories: ["supported libraries", "supported languages", "integrations", "imag
## Which languages, libraries, and environments do you support?
-- The {{< var validmind.developer >}}[^1] is designed to be platform-agnostic and compatible with most popular open-source programming languages and model development environments in Python and R,[^2] from XGBoost to more sophisticated libraries such as Pytorch and TensorFlow — and many more.
+- The {{< var validmind.developer >}}[^1] is designed to be platform-agnostic and compatible with most popular open-source programming languages and development environments in Python and R,[^2] from XGBoost to more sophisticated libraries such as Pytorch and TensorFlow — and many more.
- We directly support Matplotlib[^3] and Plotly[^4] plotting libraries for visual representations, and you're able to return images from other libraries as bytes-like objects.[^5]
::: {.callout}
@@ -35,18 +35,18 @@ Support for commercial and closed-source programming languages such as SAS and M
## What test ingestion or modeling techniques are supported?
- {{< var vm.product >}} supports ingesting test results from your training and evaluation pipeline, such as using batch prediction or online prediction mechanisms.[^6]
-- We are also offer standard documentation via the {{< var vm.developer >}} for additional modeling techniques.[^7]
+- We also offer standard documentation via the {{< var vm.developer >}} for additional modeling techniques.[^7]
{{< include _faq-images.qmd >}}
## What large language model (LLM) features are offered?
-{{< var vm.product >}} offers several specialized features that use large language models (LLMs) to streamline model risk management and ensure regulatory compliance:
+{{< var vm.product >}} offers several specialized features that use large language models (LLMs) to streamline risk management and ensure regulatory compliance:
- **Test interpretation** — Interprets results from tests run within {{< var vm.product >}}.
-- **Qualitative checks** — Leverages metadata from the model inventory, test outcomes, and additional data provided to create qualitative sections within model documentation.
-- **Risk assessment** — Using data from test results, generates a tailored risk assessment for each section of model documentation.
-- **{{< var validmind.checker >}}**[^8] — Reviews documents such as model documentation or validation reports to ensure documents aligns with relevant regulatory requirements.
+- **Qualitative checks** — Leverages metadata from the inventory, test outcomes, and additional data provided to create qualitative sections within documentation.
+- **Risk assessment** — Using data from test results, generates a tailored risk assessment for each section of documentation.
+- **{{< var validmind.checker >}}**[^8] — Reviews documents such as documentation or validation reports to ensure they align with relevant regulatory requirements.
{{< include _faq-explainability.qmd >}}
@@ -54,24 +54,6 @@ Support for commercial and closed-source programming languages such as SAS and M
{{< include /about/deployment/_deployment-available-options.qmd >}}
-
-
-
-
-
-
-
-
-
-
## Learn more
:::{#faq-integrations}
@@ -88,10 +70,10 @@ We will be implementing connector interfaces allowing extraction of relationship
[^4]: [Plotly](https://plotly.com/)
-[^5]: [Do you support including images in model documents?](#images)
+[^5]: [Do you support including images in documents?](#images)
[^6]: [Load dataset predictions](/notebooks/how_to/data_and_datasets/dataset_inputs/load_datasets_predictions.ipynb)
-[^7]: [Do you include explainability-related testing and documentation?](#explanability)
+[^7]: [Do you include explainability-related testing and documentation?](#explainability)
[^8]: [Customize {{< var validmind.checker >}}](/guide/templates/customize-document-checker.qmd)
\ No newline at end of file
diff --git a/site/faq/faq-inventory.qmd b/site/faq/faq-inventory.qmd
index 1aa5bf9ccc..3cb987a699 100644
--- a/site/faq/faq-inventory.qmd
+++ b/site/faq/faq-inventory.qmd
@@ -2,7 +2,7 @@
# Copyright © 2023-2026 ValidMind Inc. All rights reserved.
# Refer to the LICENSE file in the root of this repository for details.
# SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial
-title: "Model inventory and activity"
+title: "Inventory and activity"
date: last-modified
aliases:
- /guide/faq-inventory.html
@@ -17,47 +17,47 @@ listing:
- ../guide/inventory/view-record-activity.qmd
- ../guide/inventory/working-with-the-inventory.qmd
- ../guide/inventory/managing-the-inventory.qmd
-categories: ["record activity", "model registration", "model inventory", "customization", "model stages", "model interdependencies", "auditing", "exports", "validmind platform"]
+categories: ["inventory", "inventory registration", "inventory customization", "inventory interdependencies", "activity", "auditing", "exports", "validmind platform"]
---
{{< include _faq-activity.qmd >}}
-## How do I register models with {{< var vm.product >}}?
+## How do I register records with {{< var vm.product >}}?
-- Register models within the {{< var validmind.platform >}} via the model inventory as the first step towards streamlining your model documentation and validation workflow.
-- To add a model to the inventory, you fill out a customizable questionnaire capturing the required registration metadata.[^1]
+- Register records (such as models) within the {{< var validmind.platform >}} via the inventory as the first step towards streamlining your documentation and validation workflow.
+- To add a record to the inventory, you fill out a customizable questionnaire capturing the required registration metadata.[^1]
-By default, the [{{< fa code >}} Developer]{.bubble} role[^2] has sufficient permissions to register models.
+By default, the [{{< fa code >}} Developer]{.bubble} role[^2] has sufficient permissions to register records.
-## Are model registration questionnaires customizable?
+## Are registration questionnaires customizable?
-- Yes, along with default fields provided by {{< var vm.product >}} as part of your basic model information, you can add additional model information and make these custom fields required when creating models.[^3]
+- Yes, along with default fields provided by {{< var vm.product >}} as part of your basic record (model) information, you can add additional record information and make these custom fields required when creating records.[^3]
- You can modify these custom fields as needed and on an ongoing basis.
-By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to manage model inventory fields.
+By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to manage inventory fields.
-## Can the {{< var vm.product >}} model inventory be customized?
+## Can the {{< var vm.product >}} inventory be customized?
-- Yes, information that is displayed on the model inventory is configurable on a per user basis.
-- You can also search, filter, and sort models to narrow down results.
-- Fields that appear on all models for all users can also be customized.
+- Yes, information that is displayed on the inventory is configurable on a per user basis.
+- You can also search, filter, and sort records (such as models) to narrow down results.
+- Fields that appear on all records for all users can also be customized.
- By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to manage model inventory fields.
+ By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to manage inventory fields.
-## Can I archive or delete models within {{< var vm.product >}}?
+## Can I archive or delete records within {{< var vm.product >}}?
-Yes, models can be archived within the {{< var validmind.platform >}} model inventory to keep your inventory accurate and up to date with your organization’s current resources.[^4]
+Yes, records (such as models) can be archived within the {{< var validmind.platform >}} inventory to keep your inventory accurate and up to date with your organization’s current resources.[^4]
-By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to archive and delete models.
+By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to archive and delete records.
-## Can I track model interdependencies within the model inventory?
+## Can I track interdependencies within the inventory?
-- Yes, the {{< var validmind.platform >}} allows you to connect two or more models together in your model inventory.[^5]
-- You can note both upstream and downstream models.
+- Yes, the {{< var validmind.platform >}} allows you to connect two or more records (models) together in your inventory.[^5]
+- You can note both upstream and downstream records.
-By default, the [{{< fa code >}} Developer]{.bubble} role has sufficient permissions to edit model interdependencies.
+By default, the [{{< fa code >}} Developer]{.bubble} role has sufficient permissions to edit record interdependencies.
-{{< include _faq-model-updates.qmd >}}
+{{< include _faq-record-updates.qmd >}}
{{< include _faq-tracking.qmd >}}
@@ -69,12 +69,12 @@ By default, the [{{< fa code >}} Developer]{.bubble} role has sufficient permiss
-[^1]: [Register records in the inventory](/guide/inventory/working-with-the-inventory.qmd)
+[^1]: [Register records in the inventory](/guide/inventory/register-records-in-inventory.qmd)
[^2]: [Manage permissions](/guide/configuration/manage-permissions.qmd)
[^3]: [Manage inventory fields](/guide/inventory/manage-inventory-fields.qmd)
-[^4]: [Archive and delete models](/guide/inventory/archive-delete-records.qmd)
+[^4]: [Archive and delete records](/guide/inventory/archive-delete-records.qmd)
-[^5]: [Configure model interdependencies](/guide/inventory/configure-record-interdependencies.qmd)
\ No newline at end of file
+[^5]: [Configure record interdependencies](/guide/inventory/configure-record-interdependencies.qmd)
\ No newline at end of file
diff --git a/site/faq/faq-organizations.qmd b/site/faq/faq-organizations.qmd
index 4a6818d07f..4709d309a5 100644
--- a/site/faq/faq-organizations.qmd
+++ b/site/faq/faq-organizations.qmd
@@ -19,19 +19,19 @@ categories: ["access", "permissions", "organizations", "user registration", "val
## How do I get access to {{< var vm.product >}}?
-#### 1. Register with ValidMind
+#### 1. Register with {{< var vm.product >}}
-- First register with our cloud-hosted {{< var validmind.platform >}},[^1] which enables you to work with model documentation or configure ValidMind for your organization.
-- With an email address or a Google, GitHub, or Microsoft account, you can gain access to ValidMind either by signing up independently, or by accepting an invite from another member of your organization.
+- First register with our cloud-hosted {{< var validmind.platform >}},[^1] which enables you to work with documentation or configure {{< var vm.product >}} for your organization.
+- With an email address or a Google, GitHub, or Microsoft account, you can gain access to {{< var vm.product >}} either by signing up independently, or by accepting an invite from another member of your organization.
-#### 2. Log in to ValidMind
+#### 2. Log in to {{< var vm.product >}}
- Once you've signed up or accepted an invite, log in to the {{< var validmind.platform >}}.[^2]
-- {{< var vm.product >}} supports logging in via both the public interent and private network endpoints.
+- {{< var vm.product >}} supports logging in via both the public internet and private network endpoints.
## What are organizations within {{< var vm.product >}}?
-Access to the {{< var validmind.platform >}} where your model inventory is hosted is associated with an organization,[^3] which encompasses all your users, groups, and business units.
+Access to the {{< var validmind.platform >}} where your inventory is hosted is associated with an organization,[^3] which encompasses all your users, groups, and business units.
- As a user,[^4] you can belong to multiple organizations.
- You will see the option to switch between organizations only if you belong to more than one organization.
@@ -46,8 +46,8 @@ By default, the [{{< fa hand >}} Customer Admin]{.bubble} role[^5] has sufficien
## How do user roles, user groups, and access permissions work?
- - Users belong to groups which determine which models they can see, and have roles with attached permissions which define the level of access they have to features.
- - Groups are segments of users with the ability to view models associated with that group. Access to granular features in the {{< var vm.platform >}} within a group’s set of models is further defined by roles and permissions.
+ - Users belong to groups which determine which records (such as models) they can see, and have roles with attached permissions which define the level of access they have to features.
+ - Groups are segments of users with the ability to view records associated with that group. Access to granular features in the {{< var vm.platform >}} within a group’s set of records is further defined by roles and permissions.
- Roles are a named set of permissions that determine your users’ access to features within the {{< var vm.platform >}} based on your organization’s structure.
- Permissions dictate user access controls within the {{< var vm.platform >}}, and are associated with specific roles.
diff --git a/site/faq/faq-privacy.qmd b/site/faq/faq-privacy.qmd
index 79644eb4e9..b2468c25e0 100644
--- a/site/faq/faq-privacy.qmd
+++ b/site/faq/faq-privacy.qmd
@@ -28,12 +28,12 @@ categories: ["data handling", "privacy", "confidentiality", "record activity", "
Access to the {{< var validmind.platform >}} is facilitated through AWS PrivateLink, which provides private connectivity between {{< var vm.product >}} and your on-premises networks without exposing your traffic to the public internet.[^2]
-## What model assets are automatically imported into {{< var vm.product >}}?
+## What assets are automatically imported into {{< var vm.product >}}?
{{< var vm.product >}} stores the following assets in documents via our {{< var validmind.api >}}:
-- Dataset and model metadata which allow generating documentation snippets programmatically (example: stored definition for "common logistic regression limitations" when a logistic regression model has been passed to the {{< var vm.product >}} test suite execution)
-- Quality and performance metrics collected from the dataset and model
+- Dataset and model (any type of record) object metadata which allow generating documentation snippets programmatically (example: stored definition for "common logistic regression limitations" when a logistic regression model has been passed to the {{< var vm.product >}} test suite execution)
+- Quality and performance metrics collected from the dataset and record
- Outputs from executed test suites
- Images, plots, and visuals generated as part of extracting metrics and running tests
@@ -55,32 +55,7 @@ Furthermore, {{< var vm.product >}}'s data retention policy complies with the SO
{{< include _faq-activity.qmd >}}
-{{< include _faq-model-updates.qmd >}}
-
-
-
-
-
-
-
-
-
-
-
-
+{{< include _faq-record-updates.qmd >}}
## Learn more
diff --git a/site/faq/faq-reporting.qmd b/site/faq/faq-reporting.qmd
index 0b9abd046a..c672652c5f 100644
--- a/site/faq/faq-reporting.qmd
+++ b/site/faq/faq-reporting.qmd
@@ -22,7 +22,7 @@ categories: ["exports", "analytics", "reports", "ongoing monitoring", "validmind
## What analytic features are offered by {{< var vm.product >}}?
-- Out-of-the-box reports within the {{< var validmind.platform >}}[^1] are broken down by data on models and data on artifacts.
+- Out-of-the-box reports within the {{< var validmind.platform >}}[^1] are broken down by data on records (such as models) and data on artifacts.
- For each of the bar charts, you can hover for numerical breakdowns or click on individual bars to get a more detailed view.[^2]
- You're also able to add custom report pages and analytic widgets to supplement the out-of-the-box reports provided.[^3]
diff --git a/site/faq/faq-testing.qmd b/site/faq/faq-testing.qmd
index 32ee6aa308..6f82ab1694 100644
--- a/site/faq/faq-testing.qmd
+++ b/site/faq/faq-testing.qmd
@@ -19,28 +19,28 @@ listing:
description: "Tests that are available as part of the {{< var validmind.developer >}}, grouped by type of validation or monitoring test."
path: ../developer/how-to/test-sandbox.qmd
- ../guide/monitoring/ongoing-monitoring.qmd
-categories: ["testing", "model documentation", "customization", "custom data", "explainability", "ongoing monitoring", "validmind library"]
+categories: ["testing", "documentation", "customization", "custom data", "explainability", "ongoing monitoring", "validmind library"]
---
## How do the out-of-the-box tests developed by {{< var vm.product >}} work?
All the default tests are developed using open-source Python and R libraries.
-The {{< var validmind.developer >}}[^1] test interface is a light wrapper that defines utility functions to agnostically interact with different dataset and model backends, and contains functions to collect and post results to the {{< var validmind.platform >}}[^2] using a generic results schema.
+The {{< var validmind.developer >}}[^1] test interface is a light wrapper that defines utility functions to agnostically interact with different dataset and record (model) backends, and contains functions to collect and post results to the {{< var validmind.platform >}}[^2] using a generic results schema.
-## When do I use tests and tests suites?
+## When do I use tests and test suites?
While you have the flexibility to decide when to use which {{< var vm.product >}} tests, here are a few typical scenarios:[^3]
- **Dataset testing** — To document and validate your dataset.
-- **Model testing** — To document and validate your model.
+- **Model testing** — To document and validate your record, such as a model.
- **End-to-end testing** — To document a binary classification model and the relevant dataset end-to-end.
## Can we configure, customize, or add our own tests?
Yes, {{< var vm.product >}} allows tests to be manipulated at several levels:
-- You can configure which tests are required to run programmatically depending on the model use case.[^4]
+- You can configure which tests are required to run programmatically depending on the record's use case.[^4]
- You can change the thresholds and parameters for default tests already available in the {{< var vm.developer >}} — for instance, changing the threshold parameter for the class imbalance flag.[^5]
- You can also connect your own custom tests with the {{< var validmind.developer >}}. These custom tests are configurable and are able to run programmatically, just like the rest of the {{< var vm.developer >}}.[^6]
- Personalize tests further for your use case by using {{< var vm.product >}}'s `RawData` feature[^7] to customize the output of tests.
@@ -51,12 +51,12 @@ In addition to custom tests, you can also add use case and test-specific context
## How do I log tests as a developer?
-You use the {{< var validmind.developer >}} to run and log tests during model development, the results of which are then inserted your model documentation within the {{< var validmind.platform >}}.[^9] The {{< var vm.developer >}} also automatically generates draft test descriptions for your test results — generations that can be modified for your custom use cases.[^10]
+You use the {{< var validmind.developer >}} to run and log tests during development, the results of which are then inserted into your documentation within the {{< var validmind.platform >}}.[^9] The {{< var vm.developer >}} also automatically generates draft test descriptions for your test results — generations that can be modified for your custom use cases.[^10]
To log tests as a developer with the {{< var validmind.developer >}}:
-- You must have the [{{< fa code >}} Developer]{.bubble} role[^11] or another role with sufficient permissions to create and own models, and to work with model documentation.
-- You must be the model owner or model developer, but not the model validator,[^12] for the model you want to log tests and update documentation for.
+- You must have the [{{< fa code >}} Developer]{.bubble} role[^11] or another role with sufficient permissions to create and own records (models), and to work with documentation.
+- You must be the record owner or record developer, but not the record validator,[^12] for the record you want to log tests and update documentation for.
::: {.callout}
## Want to learn how to use {{< var vm.product >}} as a developer?
@@ -66,12 +66,12 @@ Check out our introductory series — [**{{< var vm.product >}} for development*
## How do I log tests as a validator?
-You use the {{< var validmind.developer >}} to run and log tests during model validation, the results of which are then inserted your validation report within the {{< var validmind.platform >}}.[^13] The {{< var vm.developer >}} also automatically generates draft test descriptions for your test results — generations that can be modified for your custom use cases.[^14]
+You use the {{< var validmind.developer >}} to run and log tests during validation, the results of which are then inserted into your validation report within the {{< var validmind.platform >}}.[^13] The {{< var vm.developer >}} also automatically generates draft test descriptions for your test results — generations that can be modified for your custom use cases.[^14]
To log tests as a validator with the {{< var validmind.developer >}}:
-- You must have the [{{< fa circle-check >}} Validator]{.bubble} role[^15] or another role with sufficient permissions to access models for validation, to review model documentation, and to work with validation reports and model artifacts.
-- You must be the model validator, but not the model owner or model developer,[^16] for the model you want to log tests and update documentation for.
+- You must have the [{{< fa circle-check >}} Validator]{.bubble} role[^15] or another role with sufficient permissions to access records (models) for validation, to review documentation, and to work with validation reports and artifacts.
+- You must be the record validator, but not the record owner or record developer,[^16] for the record you want to log tests and update documentation for.
::: {.callout}
## Want to learn how to use {{< var vm.product >}} as a validator?
diff --git a/site/faq/faq-validation.qmd b/site/faq/faq-validation.qmd
index ee56299e2a..741abe5beb 100644
--- a/site/faq/faq-validation.qmd
+++ b/site/faq/faq-validation.qmd
@@ -2,10 +2,8 @@
# Copyright © 2023-2026 ValidMind Inc. All rights reserved.
# Refer to the LICENSE file in the root of this repository for details.
# SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial
-title: "Model validation and artifacts"
+title: "Validation and artifacts"
date: last-modified
-aliases:
- - /guide/faq-documentation.html
listing:
- id: faq-validation
type: grid
@@ -17,7 +15,7 @@ listing:
- ../guide/validation/manage-validation-guidelines.qmd
- ../guide/validation/preparing-validation-reports.qmd
- ../guide/validation/working-with-artifacts.qmd
-categories: ["model validation", "validation guidelines", "model artifacts", "findings", "model documentation", "templates", "compliance", "validmind platform"]
+categories: ["validation", "validation guidelines", "artifacts", "findings", "documentation", "templates", "compliance", "validmind platform"]
---
## Can I set up custom validation guidelines for use in templates?
@@ -29,9 +27,9 @@ Yes, {{< var vm.product >}} supports the implementation of custom validation gui
By default, the [{{< fa hand >}} Customer Admin]{.bubble} role[^2] has sufficient permissions to manage validation guidelines.
-## How does {{< var vm.product >}} help with assessing model compliance?
+## How does {{< var vm.product >}} help with assessing compliance?
-Use {{< var vm.product >}} to assess compliance of your models with guidelines based on analyzing evidence and artifacts (findings),[^3] providing an unbiased starting point that enables more efficient discussions between validators and developers.
+Use {{< var vm.product >}} to assess compliance of your records (such as models) with guidelines based on analyzing evidence and artifacts (findings),[^3] providing an unbiased starting point that enables more efficient discussions between validators and developers.
Without leaving the {{< var validmind.platform >}}, you're able to:
@@ -39,19 +37,19 @@ Without leaving the {{< var validmind.platform >}}, you're able to:
2. Link tracked artifacts to validation reports
3. Provide granular compliance assessments for each section of your validation report
-By default, the [{{< fa circle-check >}} Validator]{.bubble} role has sufficient permissions to assess model compliance on validation reports.
+By default, the [{{< fa circle-check >}} Validator]{.bubble} role has sufficient permissions to assess compliance on validation reports.
-## What support does {{< var vm.product >}} offer for model artifacts?
+## What support does {{< var vm.product >}} offer for artifacts?
-- Within the {{< var validmind.platform >}}, you're able to log artifacts at the model or the documentation section level.[^4]
+- Within the {{< var validmind.platform >}}, you're able to log artifacts at the record (model) or the documentation section level.[^4]
- On each artifact, you're able to outline proposed remediation plans, attach supporting documentation, track the artifact's status, attach the artifact to a risk area and/or documentation section, designate a due date, and assign a resolution owner.
-- You can also access a complete list of filterable artifacts logged across all your models, or look at only artifacts linked to a specific model.[^5]
+- You can also access a complete list of filterable artifacts logged across all your records, or look at only artifacts linked to a specific record.[^5]
-By default, the [{{< fa circle-check >}} Validator]{.bubble} role has sufficient permissions to manage model artifacts.
+By default, the [{{< fa circle-check >}} Validator]{.bubble} role has sufficient permissions to manage artifacts.
## Can I create custom artifact types?
-Yes, you can create custom artifact types to track categories of observations beyond the default types (Validation Issue, Policy Exception, Model Limitation).[^6]
+Yes, you can create custom artifact types to track categories of observations beyond the default types (Validation Issue, Policy Exception, Limitation).[^6]
Common examples include:
diff --git a/site/faq/faq-workflows.qmd b/site/faq/faq-workflows.qmd
index a11bf82fb3..5b9a1424c6 100644
--- a/site/faq/faq-workflows.qmd
+++ b/site/faq/faq-workflows.qmd
@@ -9,7 +9,7 @@ aliases:
listing:
- id: faq-workflows
type: grid
- grid-columns: 3
+ grid-columns: 2
max-description-length: 250
sort: false
fields: [title, description]
@@ -18,12 +18,12 @@ listing:
- ../guide/workflows/manage-record-stages.qmd
- ../guide/inventory/manage-inventory-fields.qmd
- ../guide/attestation/working-with-attestations.qmd
-categories: ["workflows", "model lifecycle", "lifecycle statuses", "attestations", "validmind platform", "validmind library"]
+categories: ["workflows", "lifecycle", "lifecycle statuses", "attestations", "validmind platform", "validmind library"]
---
## Can I customize workflows within {{< var vm.product >}}?
-- Yes, you can create custom workflows for the review and approval of models throughout their lifecycles with {{< var validmind.platform >}},[^1] enabling you to more easily oversee your organization's unique model risk management process.
+- Yes, you can create custom workflows for the review and approval of records (such as models) throughout their lifecycles with {{< var validmind.platform >}},[^1] enabling you to more easily oversee your organization's unique risk management process.
- For example, workflows can be configured to include any number of review stages involving different sets of stakeholders — at any point in the process.
By default, the [{{< fa hand >}} Customer Admin]{.bubble} role[^2] has sufficient permissions to manage workflows.
@@ -35,19 +35,19 @@ By default, the [{{< fa hand >}} Customer Admin]{.bubble} role[^2] has sufficien
By default, the [{{< fa hand >}} Customer Admin]{.bubble} role has sufficient permissions to manage lifecycle statuses.
-{{< include _faq-progress-model.qmd >}}
+{{< include _faq-progress-workflow.qmd >}}
## Can we work with disconnected workflows?
Yes, {{< var vm.product >}} supports disconnected workflows natively at the data-collection level since the {{< var validmind.developer >}}[^3] creates individual test runs every time a new test iteration is executed.
- This allows for running parallel/disconnected tests that individually send results to the {{< var validmind.platform >}}.
-- Visualizing the disconnected workflow in terms of model testing and documentation will depend on requirements at the use-case level.
+- Visualizing the disconnected workflow in terms of testing and documentation will depend on requirements at the use-case level.
::: {.callout}
-## You can also leverage the {{< var validmind.developer >}} once you are ready to document a specific model for review and validation.
+## You can also leverage the {{< var validmind.developer >}} once you are ready to document a specific record (model) for review and validation.
-You do not need to use the {{< var validmind.platform >}} while you are in the exploration or R&D phase of model development.
+You do not need to use the {{< var validmind.platform >}} while you are in the exploration or R&D phase of development.
:::
{{< include _faq-attestations.qmd >}}
diff --git a/site/faq/faq.qmd b/site/faq/faq.qmd
index 74bf9a5488..50a718ba8e 100644
--- a/site/faq/faq.qmd
+++ b/site/faq/faq.qmd
@@ -18,11 +18,11 @@ listing:
- path: faq-workflows.qmd
title: "Workflows"
- path: faq-inventory.qmd
- title: "Model inventory and activity"
+ title: "Inventory and activity"
- path: faq-documentation.qmd
- title: "Model documents and templates"
+ title: "Documents and templates"
- path: faq-validation.qmd
- title: "Model validation and artifacts"
+ title: "Validation and artifacts"
- path: faq-collaboration.qmd
title: "Collaboration"
- path: faq-reporting.qmd
diff --git a/site/get-started/common-steps/_register-your-first-model.qmd b/site/get-started/common-steps/_register-your-first-model.qmd
index 4e7562b6b4..332c9ca023 100644
--- a/site/get-started/common-steps/_register-your-first-model.qmd
+++ b/site/get-started/common-steps/_register-your-first-model.qmd
@@ -9,7 +9,7 @@ a. Under the [record type]{.smallcaps} drop-down, select `Model`.^[[Manage inven
a. Click **{{< fa plus >}} Register Model**.
-a. Enter in the **[model name]{.smallcaps}** and select any option for the following required fields:
+a. Enter the **[model name]{.smallcaps}** and select any option for the following required fields:
- **[business unit]{.smallcaps}** — For example: `Finance`
- **[prelimnary risk tier]{.smallcaps}** — For example: `1`
@@ -47,7 +47,7 @@ a. Under the [record type]{.smallcaps} drop-down, select `Model`.^[[Manage inven
a. Click **{{< fa plus >}} Register Model**.
-a. Enter in the **[model name]{.smallcaps}** and select any option for the following required fields:
+a. Enter the **[model name]{.smallcaps}** and select any option for the following required fields:
- **[business unit]{.smallcaps}** — For example: `Finance`
- **[prelimnary risk tier]{.smallcaps}** — For example: `1`
diff --git a/site/guide/configuration/_add-business-units.qmd b/site/guide/configuration/_add-business-units.qmd
index d9fe0f3a9e..ddc3be0ff2 100644
--- a/site/guide/configuration/_add-business-units.qmd
+++ b/site/guide/configuration/_add-business-units.qmd
@@ -7,7 +7,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
1. Click **{{< fa plus >}} Add Business Unit** under Business Units.
-1. Enter in your **[business unit name]{.smallcaps}**.
+1. Enter your **[business unit name]{.smallcaps}**.
1. Click **Add Business Unit** to save your changes.
@@ -18,7 +18,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
:::: {.content-visible unless-format="revealjs" unless-meta="includes.quickstart"}
a. Click **{{< fa plus >}} Add Business Unit** under Business Units.
-a. Enter in your **[business unit name]{.smallcaps}**.
+a. Enter your **[business unit name]{.smallcaps}**.
a. Click **Add Business Unit** to save your changes.
@@ -35,7 +35,7 @@ a. Under {{< fa building >}} Organization, select **Organization**.
a. Click **{{< fa plus >}} Add Business Unit** under Business Units.
-a. Enter in your **[business unit name]{.smallcaps}**.
+a. Enter your **[business unit name]{.smallcaps}**.
a. Click **Add Business Unit** to save your changes.
diff --git a/site/guide/documentation/_locate-document-overview.qmd b/site/guide/documentation/_locate-document-overview.qmd
index 59a5a4513d..af25cd9fec 100644
--- a/site/guide/documentation/_locate-document-overview.qmd
+++ b/site/guide/documentation/_locate-document-overview.qmd
@@ -18,7 +18,7 @@ To locate your document overview for a record:
:::: {.content-hidden unless-format="revealjs"}
1. In the left sidebar, click **{{< fa cubes >}} Inventory**.
-1. Select a record or [find your record by applying a filter or searching for it](/guide/inventory/working-with-the-inventory.qmd#search-filter-and-sort-records){target="blank"}.
+1. Select a record or [find your record by applying a filter or searching for it](/guide/inventory/working-with-the-inventory.qmd#search-filter-and-sort-records){target="_blank"}.
1. In the left sidebar that appears for your record, click **{{< fa file >}} Documents** and select **Development**.
diff --git a/site/guide/documentation/content-editing-toolbar.png b/site/guide/documentation/content-editing-toolbar.png
index 68cf696412..9421913ad7 100644
Binary files a/site/guide/documentation/content-editing-toolbar.png and b/site/guide/documentation/content-editing-toolbar.png differ
diff --git a/site/guide/documentation/content_blocks/_generate-with-ai.qmd b/site/guide/documentation/content_blocks/_generate-with-ai.qmd
index 1852a374f2..f3ed00600d 100644
--- a/site/guide/documentation/content_blocks/_generate-with-ai.qmd
+++ b/site/guide/documentation/content_blocks/_generate-with-ai.qmd
@@ -5,7 +5,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
:::: {.content-visible unless-format="revealjs"}
1. Click **{{< fa ellipsis-vertical >}}** in the content editing toolbar and select **[{{< fa diamond >}} (Generate Text with AI)]{.pink}**.
-1. Enter in a custom prompt and click **Send**, or click **Generate Content** to compose a draft for review.
+1. Enter a custom prompt and click **Send**, or click **Generate Content** to compose a draft for review.
@@ -33,7 +33,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
:::: {.content-hidden unless-format="revealjs"}
1. Click **{{< fa ellipsis-vertical >}}** in the content editing toolbar and select **[{{< fa diamond >}} (Generate Text with AI)]{.pink}**.
-1. Enter in a custom prompt and click **Send**, or click **Generate Content** to compose a draft for review.
+1. Enter a custom prompt and click **Send**, or click **Generate Content** to compose a draft for review.
:::: {.content-visible when-format="revealjs" when-meta="includes.pdf-context"}
You can also include [record attachments in `.pdf` format](/guide/inventory/edit-inventory-fields.qmd#manage-attachments){target="_blank"} as context documents:
diff --git a/site/guide/documentation/work-with-content-blocks.qmd b/site/guide/documentation/work-with-content-blocks.qmd
index 5d5e23d7b4..6ec599dbae 100644
--- a/site/guide/documentation/work-with-content-blocks.qmd
+++ b/site/guide/documentation/work-with-content-blocks.qmd
@@ -14,17 +14,17 @@ includes:
Make edits to your documents by adding or removing content blocks directly in the online editor.
-## What are content blocks?
-
-Content blocks provide you with sections that are part of a template, and are used in documents.
-
-- You can think of these sections as an empty canvas that you fill in with text and test results.
-- Multiple sections are joined to create a longer document with a table of contents that has different heading and subheading levels, such as "1.," "1.1.," and so on.
-
::: {.callout title="Static PDF documents cannot be edited."}
You can only work with content blocks in PDFs converted to editable documents,[^1] documents generated by the {{< var validmind.developer >}}, or documents created in the {{< var validmind.platform >}}.
:::
+## What are content blocks?
+
+Content blocks are modular document template components, used to populate your documents:
+
+- Content blocks are empty canvases that you fill in with text and test results.
+- Content blocks are inserted into document templates that define the structure of your documents.[^2]
+
#### Content block types
Content blocks can be new, blank blocks, or prepopulated via your library of logged test or metric results and text block templates:
@@ -43,12 +43,12 @@ The content editing toolbar is a rich text editor that enables you to:
- Undo or redo changes
- Format your text, including adding hyperlinks and code blocks
-- Reference related record and artifact field values with variables[^2]
-- Insert LaTex formulas[^3]
-- Reference other sections of the document[^4]
+- Reference related record and artifact field values with variables[^3]
+- Insert LaTeX formulas[^4]
+- Reference other sections of the document[^5]
- Attach images via upload or URL
-You can also use the toolbar to suggest changes, save named versions of content, and leave comments.[^5]
+You can also use the toolbar to suggest changes, save named versions of content, and leave comments.[^6]
::: {.callout title="Stuck on where to start?"}
Use {{< var vm.product >}} to assist you with generating content via AI!^[[Generate content drafts with AI](#generate-content)]
@@ -59,9 +59,9 @@ Use {{< var vm.product >}} to assist you with generating content via AI!^[[Gener
## Prerequisites
- [x] {{< var link.login >}}
-- [x] There are records registered in the inventory.[^6]
-- [x] Documents exist and are completed or are in progress for your record.[^7]
-- [x] You are a [{{< fa code >}} Developer]{.bubble} or [{{< fa circle-check >}} Validator]{.bubble}, or assigned another role with sufficient permissions to perform the tasks in this guide.[^8]
+- [x] There are records registered in the inventory.[^7]
+- [x] Documents exist and are completed or are in progress for your record.[^8]
+- [x] You are a [{{< fa code >}} Developer]{.bubble} or [{{< fa circle-check >}} Validator]{.bubble}, or assigned another role with sufficient permissions to perform the tasks in this guide.[^9]
:::
@@ -80,26 +80,26 @@ Use {{< var vm.product >}} to assist you with generating content via AI!^[[Gener
#### [from library]{.smallcaps}
Text Block
- : Inserts a text block from a template in your block library:[^9]
+ : Inserts a text block from a template in your block library:[^10]
a. Select the reusable blocks you want to add.
b. Click **Insert # Text Block(s) to Document**.
- Test-Driven[^10]
+ Test-Driven[^11]
: Adds a new section with logged test results.
- Metric Over Time[^11]
+ Metric Over Time[^12]
: Adds a new section with logged metric over time results.
:::
-7. After adding the block to your document, click on the text to make changes or add comments.[^12]
+7. After adding the block to your document, click on the text to make changes or add comments.[^13]
### Reference field values
While editing a simple text block within documents, you can reference values in the form of variables from:
::: {.callout}
-- To reference field values in the form of variables, your organization must not have tracked changes enabled by default.[^13]
+- To reference field values in the form of variables, your organization must not have tracked changes enabled by default.[^14]
- Note that while you are able to select fields with empty values within available record or artifact type fields, no value will be displayed in the content block until the field is populated.
:::
@@ -119,8 +119,8 @@ While editing a simple text block within documents, you can insert math equation
While editing a simple text block within documents, you can have {{< var vm.product >}} assist you with generating content drafts.
::: {.callout title="How can generate content drafts with AI?"}
-- To use the generate content drafts with AI feature, your organization must not have tracked changes enabled by default.[^14]
-- Generating content drafts works best after you've logged tests with the {{< var validmind.developer >}},[^15] as existing test descriptions and results provide more context for the {{< var vm.product >}} AI Content Builder to draw upon.
+- To use the generate content drafts with AI feature, your organization must not have tracked changes enabled by default.[^15]
+- Generating content drafts works best after you've logged tests with the {{< var validmind.developer >}},[^16] as existing test descriptions and results provide more context for the {{< var vm.product >}} AI Content Builder to draw upon.
:::
@@ -129,7 +129,7 @@ To generate content drafts:
{{< include content_blocks/_generate-with-ai.qmd >}}
-When generating content drafts with AI, accepted versions and edits are retained in your {{< fa wifi >}} Activity[^16] just like other updates to your documents.
+When generating content drafts with AI, accepted versions and edits are retained in your {{< fa wifi >}} Activity[^17] just like other updates to your documents.
@@ -177,7 +177,7 @@ While editing a simple text block within documents, you can directly reference o
:::
-Hyperlinks will also take you to the referenced section in PDF document exports.[^17]
+Hyperlinks will also take you to the referenced section in PDF document exports.[^18]
## Remove content blocks
@@ -187,11 +187,11 @@ Test-driven or metric over time blocks can be re-added later on but **text block
1. In the left sidebar, click **{{< fa cubes >}} Inventory**.
-2. Select a record or find your record by applying a filter or searching for it.[^18]
+2. Select a record or find your record by applying a filter or searching for it.[^19]
-3. In the left sidebar that appears for your record, click **{{< fa file >}} Documents** and select the **Latest** tab.[^19]
+3. In the left sidebar that appears for your record, click **{{< fa file >}} Documents** and select the **Latest** tab.[^20]
-4. Click on the document file you want to remove a block from.[^20]
+4. Click on the document file you want to remove a block from.[^21]
5. Click on a section header to expand that section and remove content.
@@ -206,40 +206,42 @@ Test-driven or metric over time blocks can be re-added later on but **text block
[^1]: [Manage documents](/guide/templates/manage-documents.qmd#add-record-documents)
-[^2]: [Reference field values](#reference-field-values)
+[^2]: [Working with templates](/guide/templates/working-with-document-templates.qmd)
-[^3]: [Insert mathematical formulas](#insert-mathematical-formulas)
+[^3]: [Reference field values](#reference-field-values)
-[^4]: [Reference document sections](#reference-document-sections)
+[^4]: [Insert mathematical formulas](#insert-mathematical-formulas)
-[^5]: [Collaborate with others](collaborate-with-others.qmd)
+[^5]: [Reference document sections](#reference-document-sections)
-[^6]: [Register records in the inventory](/guide/inventory/register-records-in-inventory.qmd)
+[^6]: [Collaborate with others](collaborate-with-others.qmd)
-[^7]: [Working with documents](/guide/templates/working-with-documents.qmd)
+[^7]: [Register records in the inventory](/guide/inventory/register-records-in-inventory.qmd)
-[^8]: [Manage permissions](/guide/configuration/manage-permissions.qmd)
+[^8]: [Working with documents](/guide/templates/working-with-documents.qmd)
-[^9]: [Manage text block library](/guide/templates/manage-text-block-library.qmd)
+[^9]: [Manage permissions](/guide/configuration/manage-permissions.qmd)
-[^10]: [Work with test results](/guide/documentation/work-with-test-results.qmd)
+[^10]: [Manage text block library](/guide/templates/manage-text-block-library.qmd)
-[^11]: [Work with metrics over time](/guide/monitoring/work-with-metrics-over-time.qmd)
+[^11]: [Work with test results](/guide/documentation/work-with-test-results.qmd)
-[^12]: [Collaborate with others](/guide/documentation/collaborate-with-others.qmd)
+[^12]: [Work with metrics over time](/guide/monitoring/work-with-metrics-over-time.qmd)
-[^13]: [Managing your organization](/guide/configuration/managing-your-organization.qmd#manage-document-defaults)
+[^13]: [Collaborate with others](/guide/documentation/collaborate-with-others.qmd)
[^14]: [Managing your organization](/guide/configuration/managing-your-organization.qmd#manage-document-defaults)
-[^15]: [Run tests and test suites](/developer/how-to/testing-overview.qmd)
+[^15]: [Managing your organization](/guide/configuration/managing-your-organization.qmd#manage-document-defaults)
+
+[^16]: [Run tests and test suites](/developer/how-to/testing-overview.qmd)
-[^16]: [View model activity](/guide/inventory/view-record-activity.qmd)
+[^17]: [View record activity](/guide/inventory/view-record-activity.qmd)
-[^17]: [Export documents](/guide/reporting/export-documents.qmd)
+[^18]: [Export documents](/guide/reporting/export-documents.qmd)
-[^18]: [Working with the model inventory](/guide/inventory/working-with-the-inventory.qmd#search-filter-and-sort-models)
+[^19]: [Working with the inventory](/guide/inventory/working-with-the-inventory.qmd#search-filter-and-sort-records)
-[^19]: [Work with document versions](/guide/documentation/work-with-document-versions.qmd)
+[^20]: [Work with document versions](/guide/documentation/work-with-document-versions.qmd)
-[^20]: [Working with documents](/guide/templates/working-with-documents.qmd)
\ No newline at end of file
+[^21]: [Working with documents](/guide/templates/working-with-documents.qmd)
\ No newline at end of file
diff --git a/site/guide/documentation/work-with-document-versions.qmd b/site/guide/documentation/work-with-document-versions.qmd
index 8c1ad1cdae..15ee59055d 100644
--- a/site/guide/documentation/work-with-document-versions.qmd
+++ b/site/guide/documentation/work-with-document-versions.qmd
@@ -33,7 +33,7 @@ Save read-only versions of your documents in the {{< var validmind.platform >}}
5. On the document overview page, click **{{< fa bookmark >}} Save Version**.
-6. Enter in your **[notes]{.smallcaps}** for the version.
+6. Enter your **[notes]{.smallcaps}** for the version.
7. Click **Save Version** to create a read-only version of that document that captures the contents in the current state.
diff --git a/site/guide/documentation/working-with-documentation.qmd b/site/guide/documentation/working-with-documentation.qmd
index 566f2e7f94..d5ada74553 100644
--- a/site/guide/documentation/working-with-documentation.qmd
+++ b/site/guide/documentation/working-with-documentation.qmd
@@ -55,26 +55,26 @@ This section describes how to work with Development type documents[^1] (for exam
## Key concepts
-
+
-{{< include /about/glossary/model_documentation/_doc-intro.qmd >}}
+{{< include /about/glossary/documentation/_doc-intro.qmd >}}
:::: {.flex .flex-wrap .justify-around}
::: {.w-50-ns}
-{{< include /about/glossary/model_documentation/_conceptual-soundness.qmd >}}
+{{< include /about/glossary/documentation/_conceptual-soundness.qmd >}}
-{{< include /about/glossary/model_documentation/_data-preparation.qmd >}}
+{{< include /about/glossary/documentation/_data-preparation.qmd >}}
:::
::: {.w-40-ns}
-{{< include /about/glossary/model_documentation/_model-development.qmd >}}
+{{< include /about/glossary/documentation/_model-development.qmd >}}
-{{< include /about/glossary/model_documentation/_monitoring-governance.qmd >}}
+{{< include /about/glossary/documentation/_monitoring-governance.qmd >}}
:::
diff --git a/site/guide/integrations/configure-connections.qmd b/site/guide/integrations/configure-connections.qmd
index 831f96e5aa..2bca5f107e 100644
--- a/site/guide/integrations/configure-connections.qmd
+++ b/site/guide/integrations/configure-connections.qmd
@@ -165,7 +165,7 @@ Required configuration details:
4. In the modal that opens, select one of the supported connections, such as MLflow or Jira.
-5. Enter in the:
+5. Enter the following:
- **[integration name]{.smallcaps}** — How other admins can identify the connection.
- **[description]{.smallcaps}** (optional) — The intended usage or additional details.
diff --git a/site/guide/inventory/_add-edit-record-types.qmd b/site/guide/inventory/_add-edit-record-types.qmd
index ff0ca938fa..21416b69e7 100644
--- a/site/guide/inventory/_add-edit-record-types.qmd
+++ b/site/guide/inventory/_add-edit-record-types.qmd
@@ -46,7 +46,7 @@ b. Make your desired changes to your record type, then click **Update**.
:::: {.content-hidden unless-format="revealjs"}
-- To add: Click **{{< fa plus >}} Add Inventory Record Type**, enter in the record type details, then click **Create**.
+- To add: Click **{{< fa plus >}} Add Inventory Record Type**, enter the record type details, then click **Create**.
- To edit: Click on an existing record type, update the record type details, then click **Update**.
#### Record type details
diff --git a/site/guide/inventory/_field-types.qmd b/site/guide/inventory/_field-types.qmd
index f0779eaf23..77fabc701e 100644
--- a/site/guide/inventory/_field-types.qmd
+++ b/site/guide/inventory/_field-types.qmd
@@ -175,21 +175,47 @@ def formula(params):
::::
+
+
::: {.panel-tabset}
#### Params dictionary
In addition to custom field keys you add from the **available fields** drop-down, formulas can read built-in keys on the `params` dictionary:
+
+
+:::: {.content-visible when-format="html" when-meta="includes.inventory"}
| Param | Applies to | Availability | Description |
|---|---|---|---|
-| `params[""]` | Inventory records and artifacts | Add the field from the **available fields** drop-down | Current value of another custom field on the same record or artifact. |
+| `params[""]` | Inventory records & artifacts | Add the field from the **available fields** drop-down | Current value of another custom field on the same record or artifact. |
| `params["model_stage"]` | Inventory records | Add **Model Stage** from the **available fields** drop-down | Current model stage name as a string (for example, `"Production"`). Returns an empty string when no stage is assigned. Compare directly: `params["model_stage"] == "Production"`. |
| `params["stakeholders"]` | Inventory records | Add a stakeholder role from the **available fields** drop-down (for example, **Stakeholders — Owners**) | Assigned users by stakeholder role. Default role keys are `owners`, `developers`, and `validators`. Custom stakeholder types use `custom_stakeholder_`. Each entry includes `name`, `email`, and `title`. |
-| `params["integrations"]` | Inventory records and artifacts | Reference `params["integrations"]` in the formula source | Linked external integration data keyed by service (for example, `params["integrations"]["mlflow"]`). Empty when integrations are not configured or not referenced. |
+| `params["integrations"]` | Inventory records & artifacts | Reference `params["integrations"]` in the formula source | Linked external integration data keyed by service (for example, `params["integrations"]["mlflow"]`). Empty when integrations are not configured or not referenced. |
+
+::::
+
+
+
+:::: {.content-visible when-format="html" unless-meta="includes.inventory"}
+| Param | Applies to | Availability | Description |
+|---|---|---|---|
+| `params[""]` | Inventory records & artifacts | Add the field from the **available fields** drop-down | Current value of another custom field on the same record or artifact. |
+| `params["integrations"]` | Inventory records & artifacts | Reference `params["integrations"]` in the formula source | Linked external integration data keyed by service (for example, `params["integrations"]["mlflow"]`). Empty when integrations are not configured or not referenced. |
| `params["finding_type"]` | Artifacts | Always available on artifact formulas | Artifact type metadata with `["tag"]` (technical identifier) and `["name"]` (display name). |
| `params["model"]` | Artifacts | Always available when the artifact is linked to an inventory record | Parent inventory record custom field values (for example, `params["model"]["criticality_level"]`). |
+::::
+
+
#### Available helpers
Reference these helpers in your formulas — they cover the date, number, and list operations the engine does not expose directly:
@@ -212,6 +238,7 @@ Reference these helpers in your formulas — they cover the date, number, and li
:::
+
Checkbox
: A `true`/`false` value set by a toggle.
@@ -283,7 +310,7 @@ Calculation
1. Select from the drop-down of **[available record fields]{.smallcaps}**, or **[available artifact fields]{.smallcaps}** and **[record fields available via]{.smallcaps} `params["model"]`** (artifact fields) to allow your formula access to the field's values.
2. Replace the demonstration formula with your own in the code box provided.
4. Click **Test Calculation {{< fa angle-down >}}** to open the testing area.
- 5. Enter in sample values in the testing area then click **{{< fa play >}} Test Calculation** to validate your formula.
+ 5. Enter sample values in the testing area then click **{{< fa play >}} Test Calculation** to validate your formula.
Checkbox
: A `true`/`false` value set by a toggle.
diff --git a/site/guide/inventory/_rename-field-keys.qmd b/site/guide/inventory/_rename-field-keys.qmd
index 487373b087..c72fd1ca25 100644
--- a/site/guide/inventory/_rename-field-keys.qmd
+++ b/site/guide/inventory/_rename-field-keys.qmd
@@ -6,7 +6,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
1. When the **{{< fa ellipsis-vertical >}}** appears, click on it and select **{{< fa pen-to-square >}} Rename Key**.
-1. Enter in the [new key]{.smallcaps} and click **Check Availability**.
+1. Enter the [new key]{.smallcaps} and click **Check Availability**.
1. If the key is not already in use, you'll be presented with a list of dependencies to review.
diff --git a/site/guide/inventory/manage-inventory-fields.qmd b/site/guide/inventory/manage-inventory-fields.qmd
index e9541ad0da..b810431c5c 100644
--- a/site/guide/inventory/manage-inventory-fields.qmd
+++ b/site/guide/inventory/manage-inventory-fields.qmd
@@ -101,7 +101,7 @@ To group inventory fields, first create an inventory field group:
2. Under {{< fa cube >}} Inventory, select **Inventory Record Fields**.
-3. Click **{{< fa folder-plus >}} Add Group** and enter in a **[name]{.smallcaps}** and a optional **[description]{.smallcaps}** for the group.
+3. Click **{{< fa folder-plus >}} Add Group** and enter a **[name]{.smallcaps}** and an optional **[description]{.smallcaps}** for the group.
4. Click **Create Group** to add the new group.
diff --git a/site/guide/reporting/_create-a-visualization.qmd b/site/guide/reporting/_create-a-visualization.qmd
index 2735588020..a485657a72 100644
--- a/site/guide/reporting/_create-a-visualization.qmd
+++ b/site/guide/reporting/_create-a-visualization.qmd
@@ -13,7 +13,7 @@ a. Click **{{< fa pencil >}} Edit Dashboard**.
a. Select **{{< fa plus >}} Add Widget** then **{{< fa plus >}} Add Visualization**.
-a. On the Add Visualization panel, enter in your **[title]{.smallcaps}**.
+a. On the Add Visualization panel, enter your **[title]{.smallcaps}**.
a. Select a **[visualization type]{.smallcaps}**:
@@ -37,7 +37,7 @@ a. When you are done configuring your dataset, click **Add Visualization** to in
:::: {.content-hidden unless-format="revealjs"}
a. Select **{{< fa plus >}} Add Widget** then **{{< fa plus >}} Add Visualization**.
-a. On the Add Visualization panel, enter in your **[title]{.smallcaps}**.
+a. On the Add Visualization panel, enter your **[title]{.smallcaps}**.
a. Select a **[visualization type]{.smallcaps}**:
diff --git a/site/guide/reporting/_create-an-analytics-page.qmd b/site/guide/reporting/_create-an-analytics-page.qmd
index 039b26e78d..5a5ee949ac 100644
--- a/site/guide/reporting/_create-an-analytics-page.qmd
+++ b/site/guide/reporting/_create-an-analytics-page.qmd
@@ -6,7 +6,7 @@ a. In the left sidebar, click **{{< fa square-poll-vertical >}} Analytics**.
a. Click **{{< fa plus >}} Add Page**.
-a. On the Add New Page module, enter in the:
+a. On the Add New Page module, enter the following:
- **[page name]{.smallcaps}**
- **[description]{.smallcaps}** (optional)
diff --git a/site/guide/shared/manage-views/_personal-views.qmd b/site/guide/shared/manage-views/_personal-views.qmd
index b4dc370bfb..3d81b810e4 100644
--- a/site/guide/shared/manage-views/_personal-views.qmd
+++ b/site/guide/shared/manage-views/_personal-views.qmd
@@ -29,7 +29,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->
3. Select **My Views (#)** and click on **{{< fa bookmark >}} Save New View** to create your saved view.
-4. Enter in the **[view name]{.smallcaps}** and **[description]{.smallcaps}** for your saved view.
+4. Enter the **[view name]{.smallcaps}** and **[description]{.smallcaps}** for your saved view.
5. Click **Add New View** to save your saved view.
diff --git a/site/guide/templates/_add-assessment-questions.qmd b/site/guide/templates/_add-assessment-questions.qmd
index 8838206a42..87d2b971c6 100644
--- a/site/guide/templates/_add-assessment-questions.qmd
+++ b/site/guide/templates/_add-assessment-questions.qmd
@@ -9,7 +9,7 @@ Manually add assessment questions, or generate questions from a PDF upload for D
a. Click **{{< fa plus >}} Add Question** to create a new question.
-a. Enter in the **[questions]{.smallcaps}**:
+a. Enter the **[questions]{.smallcaps}**:
- Each line without a break (enter) is considered one complete question.^[Empty lines will be ignored.]
- To add a separate question, press enter to start a new line.
@@ -44,7 +44,7 @@ Select the assessment you want to add questions to by clicking on it:
1. Click **{{< fa plus >}} Add Question** to create a new question.
-1. Enter in the **[questions]{.smallcaps}**:
+1. Enter the **[questions]{.smallcaps}**:
- Each line without a break (enter) is considered one complete question. Empty lines will be ignored.
- To add a separate question, press enter to start a new line.
diff --git a/site/guide/templates/_customize-document-templates.qmd b/site/guide/templates/_customize-document-templates.qmd
index e94cd2314e..1f37129c2e 100644
--- a/site/guide/templates/_customize-document-templates.qmd
+++ b/site/guide/templates/_customize-document-templates.qmd
@@ -96,7 +96,7 @@ Customize {{< var vm.product >}}'s templates for documents to fit your specific
1. Under {{< fa file >}} Documents, select **Templates**.
-1. Select one of the tabs for the [type of template you want to edit](/guide/templates/manage-document-types.qmd){target="blank"}.
+1. Select one of the tabs for the [type of template you want to edit](/guide/templates/manage-document-types.qmd){target="_blank"}.
1. Click the template to edit and on the template details page, select **{{< fa pencil >}} Edit Outline**.
diff --git a/site/guide/templates/_duplicate-template.qmd b/site/guide/templates/_duplicate-template.qmd
index 41aa0abacc..f2f3c0420f 100644
--- a/site/guide/templates/_duplicate-template.qmd
+++ b/site/guide/templates/_duplicate-template.qmd
@@ -34,7 +34,7 @@ To duplicate an existing template and start with version one of that new templat
1. Under {{< fa file >}} Documents, select **Templates**.
-1. Select one of the tabs for the [type of template you want to duplicate](/guide/templates/working-with-documents.qmd){target="blank"}.
+1. Select one of the tabs for the [type of template you want to duplicate](/guide/templates/working-with-documents.qmd){target="_blank"}.
1. Click on the template to duplicate and on the template details page, select **{{< fa copy >}} Duplicate Template**.
diff --git a/site/guide/templates/_template-schema-generated.qmd b/site/guide/templates/_template-schema-generated.qmd
index 6408b92014..3256ea27cc 100644
--- a/site/guide/templates/_template-schema-generated.qmd
+++ b/site/guide/templates/_template-schema-generated.qmd
@@ -1,6 +1,12 @@
+SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial
+
+This file is auto-generated by scripts/generate_template_schema_docs.py
+Do not edit directly. Re-run the script to update.
+
+Source: backend/src/backend/templates/documentation/model_documentation/mdd_template_schema_v5_ui.json
+-->
```{=html}
@@ -1131,7 +1137,7 @@ SPDX-License-Identifier: AGPL-3.0 AND ValidMind Commercial -->