A tenant’s message becomes a work order somebody is accountable for.
The same engine as the service-request demo, running a different business. A model reads the resident’s message and the vendor’s quote; everything that costs money or carries risk — emergency handling, vendor selection, the authorisation limit, the invoice check — is a rule you can read and change.
Real engine · real state · real execution semantics · external effects sandboxed
Watch a tenant's message become a dispatched, authorised, reconciled work order.
Ends at an approval, because the repair exceeds policy.
There is water leaking underneath my kitchen sink. I put a bowl under it but it's filling up pretty quickly.
Seeded before the run. The workflow reads it; it is not invented. The vendor roster is shared entity state — the vendor demo can change it, and dispatch re-checks it.
Property
- Unit
- 1234 Oak Street
- Resident
- Sarah Miller
- Owner
- David Chen
Vendor roster · shared entity state
- Plumbing
- Johnson Plumbing
- HVAC
- Metro HVAC
- General
- KC Handyman
- Eligible?
- re-read at dispatch
Demo owner policy
- Auto-approve up to
- $300
- Above that
- Owner approval
- Emergency
- Dispatch, then notify
- 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