Verified
A defined test has been run against the stated scope and the result can be inspected.
Verify
Confidence needs
a measurement boundary.
Every material claim should answer four questions: what happened, where it happened, how it was measured and what it does not prove. Dunfaire keeps those answers beside the result.
CLAIM REGISTERScope before certainty
| Claim | Result | Scope | Method | Status |
|---|---|---|---|---|
| Queue reduction | 6,988 → 54 | One customer appliance | Measured | verified |
| Offline vendor data | 53,584 assignments | Shipped IEEE dataset | Count + checksum | verified |
| Recurrence handling | 24-hour suppression | Closed same condition | Behaviour test | implemented |
| Stale alert handling | 7-day close eligibility | Unowned + no fresh evidence | Behaviour test | implemented |
| Future connector | No production claim | Defined roadmap only | Not yet testable | development |
Illustrative public claim register based on currently documented behaviour. Production verification should be repeated against the agreed environment and test plan.
Maturity language
No connector wall.
No implied availability.
Integrations and capabilities carry an explicit maturity label. If a backend capability is unavailable, the control is disabled and the empty state explains why.
Implemented
The capability exists and has behaviour-level evidence, but is not presented as a broader field result.
In development
Work is planned or underway. It is not represented as available production capability.
Your test plan
Bring the conditions
that matter to you.
- 01Define the estate and evidence sources in scope.
- 02State the expected identity, grouping and recurrence behaviour.
- 03Measure the queue and retain raw before/after evidence.
- 04Record limits, exceptions and environmental variables.
A claim should survive your own test plan.
Challenge a claim ↗