A unit changes hands, and nobody gets keys early.
The same engine, running the transition between two tenancies. A model reads the notice and proposes what the inspector found; a person decides wear versus damage, because that decides whose money pays. The deposit clock is a deadline with legal consequences rather than a reminder, and the move-in checklist is a lock the engine cannot be talked past.
Real engine · real state · real execution semantics · external effects sandboxed
Watch a tenancy end, a unit turn, and another begin.
Thirty months of normal use. The deposit goes back.
Seeded before the run. The workflow reads it; it is not invented.
Outgoing tenancy
- Unit
- Maple Court 2A
- Resident
- Priya Raman
- Tenancy
- 30 months
- Deposit held
- $1,800
- Notice given
- 45 days
Demo policy
- Deposit window
- 21 days
- Wear vs damage
- A person decides
- Move-in gate
- All five, or no keys
Incoming resident
- Name
- Sam Adeyemi
- 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