[ PROOFECONOMY ]™GlossaryOriginSpecsSilent Drift
Silent drift is a change in a control's measured behavior, its Efficacy, False Block or Detection-Only Rate moving beyond a tolerance declared in advance, with no change in its DUT Fingerprint.
What it means
The control says nothing changed. The fingerprint says nothing changed. The results say otherwise. Something moved that nobody declared, such as a server-side model update, a vendor push or a quietly changed dependency, and continuous testing caught it.
The rules
- Silent drift is recorded as a finding, anchored to the Time Anchor and published with the result series.
- An undeclared change, a fingerprint change with no corresponding declared update, is also a finding.
- Witness drift: a decline in the Proof Witness’s accuracy beyond tolerance is recorded as a finding too. The witness is tested every run.
- Silent drift triggers a full run in Production Stream Mode.
Kinds of drift
| Drift | What changed |
|---|---|
| Control drift | The control under test (in jail mode: the Warden, cells, twins and policy engine) |
| AUT drift | The agent under test: model, version, system prompt, tool set, memory |
| Policy drift | The Declared Policy |
| Corpus drift | The material canaries are drawn from |
| Pigtail drift | The connection between the harness and the system under test |
| Harness drift | Any other testing component |
Every change starts a new segment. See DUT Fingerprint.