Public proof-of-value examples
Six static examples show the same loop: trigger seen, proof missing, next action named.
Start here
Pick the workflow pain that looks familiar. These use safe demo data only and do not inspect your real workflows, call providers, or use customer data.
Observed evidence
Missing proof
Inferred risk
Exact next action
Pick a failure shape and read the proof loop.
This stays on simulated data. Choose the pain that looks familiar, then inspect the observed evidence, missing proof, and exact next action.
Simulated scenario
Lead routing failure
Form or lead source captures a new inquiry, then the automation should create a CRM record and notify Slack or email.
Observed evidence
Lead captured at the source with timestamp, source name, and expected downstream handoff.
Missing proof
No CRM record ID, Slack message, or email delivery evidence is attached to the lead handoff.
Exact next action
Open the provider run for this lead, inspect the CRM create step first, then rerun or repair the notification branch and attach the resulting record/message proof.
What breaks
The lead was captured, but CRM creation and notification proof are missing.
What FlowSentinel sees
A source event exists, the downstream CRM/notification boundary has no matching observed proof, and the workflow should not be treated as recovered yet.
Inferred risk
A sales follow-up may be delayed because the lead could be trapped before the CRM or notification step.
Recovery proof report
A client-readable report that separates verified recovery, inferred improvement, and missing proof across multiple workflows.
Lead routing failure
- What breaks
- The lead was captured, but CRM creation and notification proof are missing.
- Why it matters
- A sales follow-up may be delayed because the lead could be trapped before the CRM or notification step.
- What FlowSentinel shows
- Observed source event is available; CRM and notification proof are missing.
Client onboarding failure
- What breaks
- The customer signs up, but the downstream onboarding step remains unproven.
- Why it matters
- A new customer may be waiting without internal setup, files, or first instructions.
- What FlowSentinel shows
- Observed signup/payment evidence exists; task/folder/email proof is missing.
Support escalation failure
- What breaks
- A high-priority issue exists, but escalation proof is missing.
- Why it matters
- A time-sensitive customer issue may sit in the queue without alerting the responsible operator.
- What FlowSentinel shows
- Ticket priority is observed; routing proof and acknowledgement are missing.
Billing/CRM sync failure
- What breaks
- The payment event exists, but CRM or accounting sync is stale or missing.
- Why it matters
- Customer access, renewal follow-up, or finance reporting may be wrong because business systems disagree.
- What FlowSentinel shows
- Payment event is observed; CRM/accounting update proof is absent or older.
Daily report stale-data failure
- What breaks
- The report ran, but data freshness or delivery proof is missing.
- Why it matters
- Operators may be reading yesterday's numbers while assuming the report is current.
- What FlowSentinel shows
- Scheduler event exists; data refresh and final delivery evidence are absent.
Webhook/retry failure
- What breaks
- The webhook was received, but the transformed destination write is not verified.
- Why it matters
- The source system thinks delivery started while the destination may never receive the usable record.
- What FlowSentinel shows
- Inbound event exists; destination acknowledgement and retry proof are missing.
Technical demo workflow asset packs are tracked in repo docs at docs/demo-workflows. They are optional reference material for sample payloads and provider-style workflow specs.