Glossary
The names used throughout the workbench and these guides.
Work and ownership
| Term | Meaning |
|---|---|
| Project | Saved home for a product’s versions, Assessments, inputs, and results |
| Product version | Identified configuration of the components relevant to an Assessment |
| Local Project | Records and execution owned by the local service |
| Team Project | Records and execution owned by an explicit Team host |
| Organization | Membership and commercial context; Project grants remain separate |
| Vault | Project files, Datasets, Models, and API profiles in one folder tree |
Tests and evidence
| Term | Meaning |
|---|---|
| Test plan | Reusable requirements, rationale, criteria, settings, and evidence needs |
| Run | One execution of a saved Test plan against selected inputs |
| Prediction Set | Immutable obtained or imported outputs with their source bindings |
| Ground Truth | Versioned reference labels or expected outcomes |
| Evaluation | A saved scoring result using predictions, compatible Ground Truth, and settings |
| Claim | Immutable computed result with supporting provenance |
| Evidence | Source or artifact supporting a result, interpretation, or finding |
| Report | Published snapshot of scope, sources, results, reviews, and gaps |
Review and decisions
An Assessment connects Intent, Risks, Controls, Testing & Evidence, Decisions, and Confidence. A requirement states what needs to be established; an evidence review records a conclusion about its support.
A standard pack is a version of Knotest guidance for a named external standard edition. Several clauses can share a checklist item while retaining their own criteria. A Governance case covers organization-level clauses. A duty is a recurring or event-based Confidence item after approval.
Execution approval permits reviewed work to run. An Assessment decision approves, conditionally approves, or rejects a stated use.