Synthetic workspace
Every record, address, account and message on this page is invented. There is no customer here, no database is read, and this page accepts no input. The four results below were produced by running the live verification engine against fixed synthetic evidence, so they are real verdicts about fake facts.
Worked example
One workflow, four runs, four honest answers
This is what the product looks like when it is working. Two of these four runs are not a pass, and that is the point: a tool that could only show you green would not be worth connecting.
Verification rate
33%
1 run failed
33% of decided runs were verified. Failed runs are ones where the evidence contradicted a required check.
4 runs received · 3 decided
Coverage
Coverage · customer triggered
We check the enquiries your automation tells us about.
Your automation sends us an event for each enquiry, and we then verify it against the connected systems independently.
Runs
| Result | Run | Enquiry | Enquiry received | Required checks |
|---|---|---|---|---|
| Status: Verified | run_demo_verified | Enquiry from a**@example.test | 2026-03-01 12:00:00 UTC | 4/4 confirmed |
| Status: Failed | run_demo_failed | Enquiry from a**@example.test | 2026-03-01 12:00:00 UTC | 3/4 confirmed |
| Status: Pending | run_demo_pending | Enquiry from a**@example.test | 2026-03-01 12:00:00 UTC | 0/4 confirmed |
| Status: Unverified | run_demo_unverified | Enquiry from a**@example.test | 2026-03-01 12:00:00 UTC | 0/4 confirmed |
What this workflow checks
| Check | Evidence source | Field | Operator | Required |
|---|---|---|---|---|
| A CRM record was created | crm_record | record.id | exists | yes |
| The CRM record carries this enquiry reference | crm_record | record.correlation_id | equals | yes |
| The acknowledgement email reached the recipient | email_event | message.status | provider_status_in | yes |
| The acknowledgement went to the address the enquiry named | email_event | message.recipient | normalised_email_equals | yes |
Run run_demo_verified
Enquiry from a**@example.test
| Field | Reported by your workflow | What we retrieved |
|---|---|---|
|
Check: Confirmed
A CRM record was created
|
present |
crm-rec-1 |
|
Check: Confirmed
The CRM record carries this enquiry reference
|
enq_0000000000000001 |
enq_0000000000000001 |
|
Check: Confirmed
The acknowledgement email reached the recipient
|
one of: delivered |
delivered |
|
Check: Confirmed
The acknowledgement went to the address the enquiry named
|
a**@example.test |
a**@example.test |
Status: VerifiedEvery item matched.
The verdict
Verified
We independently retrieved evidence for every required check and all of it matched.
Every required check has independent supporting evidence.
Every check we made (4 required, 0 optional)
Confirmed: A CRM record was created
We retrieved this from the connected system and it matches what you asked us to check.
We expected present. We observed crm-rec-1.
reason MATCHED · observed 2026-03-01 12:00:30 UTC
Confirmed: The CRM record carries this enquiry reference
We retrieved this from the connected system and it matches what you asked us to check.
We expected enq_0000000000000001. We observed enq_0000000000000001.
reason MATCHED · observed 2026-03-01 12:00:30 UTC
Confirmed: The acknowledgement email reached the recipient
We retrieved this from the connected system and it matches what you asked us to check.
We expected one of: delivered. We observed delivered.
reason MATCHED · observed 2026-03-01 12:00:45 UTC
Confirmed: The acknowledgement went to the address the enquiry named
We retrieved this from the connected system and it matches what you asked us to check.
We expected a**@example.test. We observed a**@example.test.
reason MATCHED · observed 2026-03-01 12:00:45 UTC
Where this result came from
- Run id
- run_demo_verified
- Enquiry reference
- enq_0000000000000001
- Source type
- signed source event (customer_claim)
- Rule version
- wf_demo@v1 · schema v1
- Enquiry received
- 2026-03-01 12:00:00 UTC
- Completion window
- 10 minutes
- Deadline
- 2026-03-01 12:10:00 UTC
- Decided at
- 2026-03-01 12:02:00 UTC
- Coverage mode
- customer_triggered
Run run_demo_failed
Enquiry from a**@example.test
| Field | Reported by your workflow | What we retrieved |
|---|---|---|
|
Check: Confirmed
A CRM record was created
|
present |
crm-rec-1 |
|
Check: Confirmed
The CRM record carries this enquiry reference
|
enq_0000000000000001 |
enq_0000000000000001 |
|
Check: Not as expected
The acknowledgement email reached the recipient
|
one of: delivered |
bounced |
|
Check: Confirmed
The acknowledgement went to the address the enquiry named
|
a**@example.test |
a**@example.test |
Status: Failed1 of 4 items did not match what was reported.
The verdict
Failed
We retrieved the evidence and it contradicts at least one of your required checks.
Next step. Open the checks below to see exactly which one, what we expected and what we found.
At least one required check is contradicted by the evidence we retrieved.
Every check we made (4 required, 0 optional)
Confirmed: A CRM record was created
We retrieved this from the connected system and it matches what you asked us to check.
We expected present. We observed crm-rec-1.
reason MATCHED · observed 2026-03-01 12:00:30 UTC
Confirmed: The CRM record carries this enquiry reference
We retrieved this from the connected system and it matches what you asked us to check.
We expected enq_0000000000000001. We observed enq_0000000000000001.
reason MATCHED · observed 2026-03-01 12:00:30 UTC
Not as expected: The acknowledgement email reached the recipient
The email provider has not reported the delivery state your rule requires. Being accepted for sending, opened or clicked is not the same as being delivered.
We expected one of: delivered. We observed bounced.
Next step. If this keeps happening for one recipient domain, that domain is likely rejecting or delaying your mail.
reason STATUS_NOT_REACHED · observed 2026-03-01 12:00:45 UTC
Confirmed: The acknowledgement went to the address the enquiry named
We retrieved this from the connected system and it matches what you asked us to check.
We expected a**@example.test. We observed a**@example.test.
reason MATCHED · observed 2026-03-01 12:00:45 UTC
Where this result came from
- Run id
- run_demo_failed
- Enquiry reference
- enq_0000000000000001
- Source type
- signed source event (customer_claim)
- Rule version
- wf_demo@v1 · schema v1
- Enquiry received
- 2026-03-01 12:00:00 UTC
- Completion window
- 10 minutes
- Deadline
- 2026-03-01 12:10:00 UTC
- Decided at
- 2026-03-01 12:20:00 UTC
- Coverage mode
- customer_triggered
Run run_demo_pending
Enquiry from a**@example.test
| Field | Reported by your workflow | What we retrieved |
|---|---|---|
|
Check: Still checking
A CRM record was created
We have not received the evidence for this check yet. |
present |
not checked yet |
|
Check: Still checking
The CRM record carries this enquiry reference
We have not received the evidence for this check yet. |
enq_0000000000000001 |
not checked yet |
|
Check: Still checking
The acknowledgement email reached the recipient
We have not received the evidence for this check yet. |
one of: delivered |
not checked yet |
|
Check: Still checking
The acknowledgement went to the address the enquiry named
We have not received the evidence for this check yet. |
a**@example.test |
not checked yet |
Status: Pending4 of 4 items are still inside the completion window.
The verdict
Still checking
The agreed completion window is still open, so we are continuing to look for evidence.
The agreed completion window is still open, so we are still looking.
Every check we made (4 required, 0 optional)
Could not confirm: A CRM record was created
We have not received the evidence for this check yet.
We expected present. We did not retrieve a value.
Next step. Nothing to do yet. We will look again while the completion window is open.
reason AWAITING_EVIDENCE
Could not confirm: The CRM record carries this enquiry reference
We have not received the evidence for this check yet.
We expected enq_0000000000000001. We did not retrieve a value.
Next step. Nothing to do yet. We will look again while the completion window is open.
reason AWAITING_EVIDENCE
Could not confirm: The acknowledgement email reached the recipient
We have not received the evidence for this check yet.
We expected one of: delivered. We did not retrieve a value.
Next step. Nothing to do yet. We will look again while the completion window is open.
reason AWAITING_EVIDENCE
Could not confirm: The acknowledgement went to the address the enquiry named
We have not received the evidence for this check yet.
We expected a**@example.test. We did not retrieve a value.
Next step. Nothing to do yet. We will look again while the completion window is open.
reason AWAITING_EVIDENCE
Where this result came from
- Run id
- run_demo_pending
- Enquiry reference
- enq_0000000000000001
- Source type
- signed source event (customer_claim)
- Rule version
- wf_demo@v1 · schema v1
- Enquiry received
- 2026-03-01 12:00:00 UTC
- Completion window
- 10 minutes
- Deadline
- 2026-03-01 12:10:00 UTC
- Decided at
- 2026-03-01 12:02:00 UTC
- Coverage mode
- customer_triggered
Run run_demo_unverified
Enquiry from a**@example.test
| Field | Reported by your workflow | What we retrieved |
|---|---|---|
|
Check: Could not confirm
A CRM record was created
We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look. |
present |
no reading |
|
Check: Could not confirm
The CRM record carries this enquiry reference
We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look. |
enq_0000000000000001 |
no reading |
|
Check: Could not confirm
The acknowledgement email reached the recipient
We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look. |
one of: delivered |
no reading |
|
Check: Could not confirm
The acknowledgement went to the address the enquiry named
We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look. |
a**@example.test |
no reading |
Status: UnverifiedWe could not check 4 of 4 items.
The verdict
Unverified
We could not get enough evidence to say either way. This is not a failure: it means we could not look, or what we could see was not conclusive.
Could not check A CRM record was created, The CRM record carries this enquiry reference, The acknowledgement email reached the recipient and The acknowledgement went to the address the enquiry named: We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look.
Next step. Check the connection status for the provider named below; if it is healthy, no action is needed.
We could not retrieve the evidence needed to judge this run, so it is unverified rather than failed. The gap is on our side of the check (we could not reach or read the connected system), and it is not a fault we found in your automation.
Every check we made (4 required, 0 optional)
Could not confirm: A CRM record was created
We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look.
We expected present. We did not retrieve a value.
Next step. Reconnect the provider from the Connections page if it is showing as expired or missing permission.
reason CONNECTION_UNAVAILABLE
Could not confirm: The CRM record carries this enquiry reference
We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look.
We expected enq_0000000000000001. We did not retrieve a value.
Next step. Reconnect the provider from the Connections page if it is showing as expired or missing permission.
reason CONNECTION_UNAVAILABLE
Could not confirm: The acknowledgement email reached the recipient
We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look.
We expected one of: delivered. We did not retrieve a value.
Next step. Reconnect the provider from the Connections page if it is showing as expired or missing permission.
reason CONNECTION_UNAVAILABLE
Could not confirm: The acknowledgement went to the address the enquiry named
We could not reach the connected system, so this check is unverified rather than failed. We are not saying your automation went wrong; we are saying we could not look.
We expected a**@example.test. We did not retrieve a value.
Next step. Reconnect the provider from the Connections page if it is showing as expired or missing permission.
reason CONNECTION_UNAVAILABLE
Where this result came from
- Run id
- run_demo_unverified
- Enquiry reference
- enq_0000000000000001
- Source type
- signed source event (customer_claim)
- Rule version
- wf_demo@v1 · schema v1
- Enquiry received
- 2026-03-01 12:00:00 UTC
- Completion window
- 10 minutes
- Deadline
- 2026-03-01 12:10:00 UTC
- Decided at
- 2026-03-01 12:20:00 UTC
- Coverage mode
- customer_triggered