An inspection that books its own successor.
The same engine, and the demo where a workflow reaches the scheduler. Closing this inspection schedules the next one; a safety finding raises a maintenance work order immediately. Neither needed a new capability — a scheduler is an external system, so a workflow talks to it through an adapter exactly as it sends email through one. Entry without proper notice is not discouraged here; it is impossible.
Real engine · real state · real execution semantics · external effects sandboxed
Watch an inspection give notice, find a hazard, and schedule its own repeat.
Ordinary findings. A person decides what becomes work.
Seeded before the run. The workflow reads it; it is not invented.
This inspection
- Unit
- Maple Court 2A
- Type
- Annual
- Window
- Tuesday, 10am–noon
- Notice given
- 36 hours
Demo entry policy
- Notice required
- 24 hours
- Short notice
- Re-serve, or abandon
- Entering anyway
- Not possible
Safety items
- Smoke / CO detector
- Immediate
- Railing / structural
- Immediate
- Everything else
- A person decides
- 1UnderstandAI
- 2Structuredeterministic
- 3Deciderules + AI
- 4Approvehuman
- 5ExecuteAPIs / software
- 6Verifysystem
The same engine, the same shape
Each of these is a workflow definition, not a separate product. Maintenance, leasing, renewals, collections, turnover, vendors and inspections are the seven that exist; the rest do not.
- Owner reporting
- Invoice processing
- Compliance
- Incident management
- Utility management
- Preventive maintenance