Quality & Measurement
Quality & Measurement checks rules with evidence and keeps results for a Workspace. Choose a service to read a rule, trace a breach, or record a measured claim.
Boundary
Quality & Measurement has two jobs: check rules and keep measured claims. A Metric supplies data for a check. A Constraint states the rule. An Objective sets a target. An Outcome keeps a chosen claim about a result. Checks within the Company Schema and Pipelines still apply. Missing or denied data cannot prove that a rule holds.
Services
Quality & Measurement keeps each rule apart from the Runs that check it. Choose the page for the claim you need to read or make.
| Service | Use it to understand |
|---|---|
| Constraints and alerts | Assertions, Constraint Groups, Run states, and breach history. |
| Metrics, objectives, and outcomes | The measure, target, and deliberate claim kept from observed evidence. |
Start here
Use Run quality checks when Quality & Measurement needs an answer now. Use Respond to breaches to trace a failed rule, repair the cause, and check the result. To keep a measured claim, read measurement before you record an Outcome.
The Console's Quality area holds the rules, Runs, Alerts, and measured claims. The configuration read contract reads an exact revision. API reference owns the fields, rights, errors, and Surfaces for each call. Use the API or MCP guide for access outside the Console.
Next steps
- Company Schema owns the data definitions Quality & Measurement can assess.
- Data Pipelines owns the input and Run evidence behind loaded Records.
- Security explains the access checks that still apply when a Metric reads evidence.