How a resident's booking for a service, an amenity or a maintenance visit travels from the app, through Cloudflare and Postgres, into Salesforce ticketing, and back. Each map compares the code as it runs today with the target design agreed on 6 November 2026, which is still awaiting sign-off.
Sixteen steps of one booking, laid out by the system that does the work. Choose a family and a mode, then press play or pick any step.
Where each part runs, by environment. Select a node to see its bindings and how it stands in each environment.
Every connection a booking depends on, with its protocol and the kind of credential it carries. No secret values appear on this page.
| # | From | To | Protocol | Credential | Carries |
|---|
How a value that staff set in Salesforce becomes a status the resident sees. Pick a value to follow its event through the state machine.