A fictional test surface. No workflow engine, customer data or production reliability claim.
Let the rule show its work.
A customer configures when a completed inspection needs a corrective task. The run keeps the published version, reveals the decision and waits for a human where it should.
A runnable operating rule
All records below are invented for this interactive study.
Watch the event find its route.
No inspection has been run yet.
The route stays empty until you run a fictional inspection.
Set the published rule.
The configuration belongs to a sample customer. It affects the next event, not a run that is already in progress.
Changes apply to the next sample event.
Send one fictional inspection
The selected finding enters the published customer rule. It does not contact any connected system.
The run leaves a readable trace.
Every line is a local simulation. It makes the intended recovery and human gate inspectable before anyone connects a real customer account.
- Choose a sample rule and run a fictional inspection.
What the first pilot would test
$2,000 setup + $1,000/month
Two agreed customer templates inside one SaaS product, with tenant-scoped configuration and a run record. This is a proposal to test with buyers, not a quoted scope or delivery promise.
Boundaries worth keeping
Initial discussion point: 50 customer tenants, 5,000 runs/month and up to 10 executed steps/run. Actual capacity, support and delivery would follow a feasibility check with a named integration engineer.