Skip to content
Merulan

Run quality checks

Request a Constraint Run, retain its identity, and read the evidence before deciding whether the claim holds.

Use this guide when a rule in Quality & Measurement needs an answer now. As an operator, you request a Constraint Run and read its evidence. Success means you can trace the answer. The rule may hold, fail, or lack the data to settle its claim.

Before you start

The Constraint must have an active, enabled revision and accept the cause of this Run. Its Metric must have an active revision. Confirm the scope and any time range before requesting work. Use Constraints and alerts to understand the rule and its evidence needs.

Decide whether you need fresh checks or a combined reading. A Constraint Group assessment reads existing Runs. It does not execute its members. Request the needed Constraint Runs before assessing the group.

Read the rule

In the Console's Constraints area, inspect the exact revision you intend to run. Check its Metric, assertion, scope, and allowed causes. For a manual check, confirm that manual_request is allowed. The configuration read contract retrieves a pinned revision when you need to inspect it outside the Console. Do not use the current definition to explain an older Run without checking its revision.

Request the check

Request a Run with the exact Constraint revision, allowed cause, and a stable key for this check. The request contract owns the fields and permission. Retain the returned Run. An accepted response confirms that the attempt was kept before evaluation. A replayed response returns the same attempt. It does not mean another check ran.

The API guide and MCP guide explain access for calls outside the Console. Both reach the same Constraint Run. Choose a key for the work being checked, not a fresh key for each attempt to send the request.

Inspect the evidence

Open the Constraint Run or use Run detail. Read the state, exact Constraint and Metric revisions, trace, and evidence. A Run at accepted or waiting has not supplied a final answer. The detail also shows recent history and the Constraint's current Alert. Check whether this Run opened or last advanced that Alert before attributing it to the Run.

Checkpoints

The requested Constraint revision and cause must match the intended check. The returned Run supplies the handle for readback. After evaluation, the trace must explain the state and show the evidence used or the reason it was unavailable. For a Constraint Group, assess the pinned member revisions and state the acceptable Run age when freshness matters to your decision.

Success

The Constraint Run has settled and its trace explains the answer. A conforming result means the evidence supports the claim. A breaching result means the claim failed. An unevaluable result means the evidence could not answer it. Failed or canceled execution is not a quality verdict. Keep those distinctions when reporting the check. Admission alone cannot establish that the rule holds.

When it fails

The Constraint Run request can be refused before an attempt exists. Read the code and repair the named condition before resubmitting.

QUALITY_CONSTRAINT_RUN_CAUSE_NOT_CONFIGURED

The Constraint does not allow this cause. Choose an allowed cause, or have its author change the rule through a reviewed plan.

QUALITY_CONSTRAINT_RUN_CONSTRAINT_INACTIVE

The requested Constraint revision is retired or disabled. Inspect the configuration and select an active revision whose meaning matches the check.

QUALITY_CONSTRAINT_RUN_METRIC_REVISION_NOT_FOUND

The Constraint's Metric has no active revision in this Workspace. Restore the intended Metric configuration before requesting another Run.

Recovery

A Constraint Run with missing, stale, denied, partial, unsupported, or failed evidence needs the named evidence problem repaired. Read the trace and the access decision before changing the rule. Request a new check for corrected work with a new cause key. Replaying the same intent returns the retained attempt. If only the response was lost, recover that same request and read its Run before starting different work.

Next steps