The clock does the chasing, and no legal step happens by itself.
The same engine, with time as the spine. Every rung of this ladder — due date, grace expiry, notice, escalation — is an event a scheduler delivers; here you deliver the same events yourself, because the workflow cannot tell the difference. It is also the demo with the least AI in it: one model call reads what a resident wrote, and every decision about money is a rule comparing two figures.
Real engine · real state · real execution semantics · external effects sandboxed
Watch a balance become paid, arranged, or escalated — by policy.
Settled on the first message. Nothing escalates.
Seeded before the run. The workflow reads it; it is not invented.
This month
- Unit
- Maple Court 2A
- Base rent
- $1,800
- Other charges
- Pet $50 · Parking $75
- Total due
- $1,925 on the 1st
Demo collection policy
- Grace period
- To the 5th
- Late fee
- $96
- Formal notice
- A person decides
- Referral
- A person decides
Never automatic
- Serving a notice
- Requires a person
- Referral to counsel
- Requires a person
- 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