Residents hit the live read.
Every resident journey that opens a residence read its stage from Salesforce, live, through one connector box. That box answers about 8 reads a second.
One event, stored once, read many times.
Salesforce changes flow left to right and are written once. Resident reads flow right to left and stop at Postgres. The grey path is the old live read, kept as a fallback.
The engine computes each holder's readiness and publishes only a changed state.
Duplicates are acknowledged and dropped. An older state never overwrites a newer one.
Before, every stage read was a live Salesforce read of about 1 s, queued behind 16 others.
Stored only while the feed is alive.
The platform serves a box's stored copy only after its backfill finished and its heartbeat is fresh. Anything else falls back to Salesforce, so a dead feed costs speed, not correctness.
| Environment · box | Sweep | Pub/Sub | Flags | Serves stage from |
|---|---|---|---|---|
| Staging · corven-ai | 15 s | on | shadow + stored | Postgres if running |
| Staging · omniyat-ai | 15 s | on | shadow + stored | Postgres if running |
| Production | none | no box config | unset | Salesforce, live |
Who promises what.
Each boundary names its producer, its consumer, the shape on the wire and what keeps the two sides in step. Two of the four have no enforced guard.
omniyat-ai SalesOrder__c on channel OMNIYAT_Invitation__chn
ready_for_viewing = Status__c is "Ready for Viewing"
envelope: event_id, correlation_id, causation_id, occurred_at, source_id, property_id, person{ref, locator}, replayed
payload: property_status, investment_status, ready_for_viewing, manager | null, holds, source_modstamp
GET /api/v1/properties/{id} → the same property
stage ∈ construction · pre_handover · handover · post_handover · living
503 connector_unavailable · Retry-After 3 · Cache-Control private, no-store
GET /session/changes (WebSocket) · /session/changes/poll (last-event-id)
Meant to tell the app to read a residence again. The mobile app has no client for either path.
The app reads stage, nothing else.
Mobile never sees readiness fields. It reads one value, stage, and routes the resident to the right part of the app from it.
What can still go wrong.
Ordered by severity. Each card states the number behind it, what it means for the business, and where the evidence lives.
From staging to 10,000 residents.
Prove the gain first, close the contract gaps second, then take it to production.