Routine Verification Report — Live Demo

Verify whether an automated routine actually completed every step.

A success message does not prove that every automated step ran. Choose a scenario to compare the reported result with the recorded evidence.

What the bot reported

Routine: newsletter-stats-weekly
Run: run-2026-08-20-clean
Completed: 2026-08-20T03:12:00Z (as supplied)
Steps reported: 5/5
Errors surfaced: 0
The report and the evidence agree: every declared step is recorded as executed.

What the evidence shows

#StepResultReportedArtifactsFindings
1 open-dashboard Executed ok 1/1 —
2 pull-subscriber-stats Executed ok 1/1 —
3 pull-open-rates Executed ok 1/1 —
4 assemble-sponsor-report Executed ok 1/1 —
5 email-sponsor-report Executed ok 0/0 —

Findings

✓ Zero findings — every declared step is shown as executed.

Decision guidance

Accept this run Recommended

All declared steps are shown as executed, with no findings for this run.

Re-teach the routine No action

The evidence shows no step-level reason to re-teach this routine.

Retire the routine No basis

The receipt archive does not yet show a repeated finding for this routine.

receipt brr-ddc2a3932787 · routine sha256 f4085fb5d71ab9ce… · run sha256 c0b99835af220dc4…

What the bot reported

Routine: newsletter-stats-weekly
Run: run-2026-08-21-skip
Completed: 2026-08-21T03:11:00Z (as supplied)
Steps reported: 4/5
Errors surfaced: 0
The bot reported success, but step 2 is missing and the sponsor report used stale data.

What the evidence shows

#StepResultReportedArtifactsFindings
1 open-dashboard Executed ok 1/1 —
2 pull-subscriber-stats Skipped silently absent 0/1 STEP_MISSING_FROM_RUN
3 pull-open-rates Executed ok 1/1 —
4 assemble-sponsor-report Drifted ok 1/1 ASSERTION_FAILED
5 email-sponsor-report Executed ok 0/0 —

3 verified findings

1 SUMMARY_CONTRADICTS_STEPS Verified Run-level finding
Evidence: {"overall_status": "success", "steps_not_executed": ["pull-subscriber-stats", "assemble-sponsor-report"]}
Impact: The run reported overall success, but at least one declared step is not shown as executed. Reports, messages, or notifications from this run may be incomplete or based on stale data.
2 ASSERTION_FAILED Verified Step: assemble-sponsor-report
Evidence: {"expected": "fresh_exports", "field": "data_source", "op": "equals", "payload_field_value": "cache"}
Impact: A recorded check failed. The step ran, but its output does not match what the routine was taught to expect.
3 STEP_MISSING_FROM_RUN Verified Step: pull-subscriber-stats
Evidence: {"missing_step_id": "pull-subscriber-stats", "run_overall_status": "success", "run_step_ids_present": ["assemble-sponsor-report", "email-sponsor-report", "open-dashboard", "pull-open-rates"]}
Impact: This declared step has no entry in the run record, and no error was reported. Its expected output cannot be verified.

Decision guidance

Accept this run Not recommended

This run has three verified findings, including a silently skipped step.

Re-teach the routine Recommended

The evidence supports re-teaching at least one step before the next run.

Retire the routine No basis

The receipt archive does not yet show a repeated finding for this routine.

receipt brr-38437913ee7f · routine sha256 f4085fb5d71ab9ce… · run sha256 a5db7932ae93ba8f…

What the bot reported

Routine: newsletter-stats-weekly
Run: run-2026-08-22-drift
Completed: 2026-08-22T03:09:00Z (as supplied)
Steps reported: 5/5
Errors surfaced: 1
The evidence separates one quiet drift from one reported failure.

What the evidence shows

#StepResultReportedArtifactsFindings
1 open-dashboard Executed ok 1/1 —
2 pull-subscriber-stats Drifted ok 0/1 ARTIFACT_EXPECTED_MISSING, ASSERTION_FAILED
3 pull-open-rates Executed ok 1/1 —
4 assemble-sponsor-report Reported failure error 0/1 STEP_REPORTED_ERROR
5 email-sponsor-report Reported skip skipped 0/0 STEP_SKIPPED_REPORTED

4 verified findings

1 STEP_REPORTED_ERROR Verified Step: assemble-sponsor-report
Evidence: {"message": "Could not reach the report template.", "status": "error"}
Impact: The run reported a failure on this step. Its expected output was not delivered by this run.
2 STEP_SKIPPED_REPORTED Verified Step: email-sponsor-report
Evidence: {"message": "Skipped because the report failed.", "reported_status": "skipped"}
Impact: The run reported skipping this step and provided a reason. Its expected output was not delivered.
3 ARTIFACT_EXPECTED_MISSING Verified Step: pull-subscriber-stats
Evidence: {"expected_artifacts": ["subscriber-stats.csv"], "missing": ["subscriber-stats.csv"], "reported_artifacts": [], "reported_status": "ok"}
Impact: An expected artifact is missing. Downstream steps may be using stale or incomplete data.
4 ASSERTION_FAILED Verified Step: pull-subscriber-stats
Evidence: {"expected": 1, "field": "rows_exported", "op": "min_count", "payload_field_value": 0}
Impact: A recorded check failed. The step ran, but its output does not match what the routine was taught to expect.

Decision guidance

Accept this run Not recommended

This run has four verified findings, including a reported failure.

Re-teach the routine Recommended

The evidence supports re-teaching at least one step before the next run.

Retire the routine No basis

The receipt archive does not yet show a repeated finding for this routine.

receipt brr-4f5f2b51f0f8 · routine sha256 f4085fb5d71ab9ce… · run sha256 db7fd6ee2201a930…