Check whether a control reacts when it is put to the test.

Quvant introduces a controlled change in the observed path and checks whether tests, guardrails or policy detect the expected deviation.

This is an assisted, pre-commercial service. Scope is limited to the two supported operators and self-assessment evidence, agreed before work starts. It is not generally available and not a self-service purchase.

Propose a control to verify

A test for your tests, and for the controls that claim to protect you.

The current implementation uses two mutation operators on self-assessment evidence. It is not a general testing method, not externally validated, and not demonstrated on customer production systems.

How the check runs

You declare the control — expected behaviour, enforcement point, relevant test.
We introduce a controlled mutation — a bounded, reversible deviation.
We observe the reaction — the test or control detects the change, or the mutant survives.
We record the result — observation, evidence and limits flow into a record.

Example

In the demonstrated self-assessment profile, a mutation removes a required artifact or alters a policy digest in a controlled environment. Quvant observes whether the declared control detects the deviation. This is not a customer-production run.

What the customer receives

The declared control
The applied mutation
The observed behaviour
Test evidence
Verification limits
A suggested next step

Boundaries

The supported profile is two mutation operators on self-assessment evidence. External and commercial use is not tested. There is no action on customer production systems. The result is not extended beyond the observed control. A human remains in the perimeter and in the interpretation.

IN DEVELOPMENT

Control Closure

Control Validation is the current application of Control Closure. The broader capability remains marked as future development.